Understanding the Basics
Intersecting runway operations should never be taken lightly. The easiest way to go would be to integrate everyone onto one runway, but that’s not what I am showing you today. I will be showing you how to let multiple aircraft fly patterns on two runways that intersect. This is quite difficult, but once you get the hang of it it’s one of the best things to do, my former local trainees can definitely attest to that.
Tutorial
Visual Aid
I will be using the visual aids below to explain the mechanics of intersecting runways. The different colours are there for me to help explain, please pay attention to them. The arrows represent aircraft flying in the pattern.
The Three Rules
I will explain the 3 most important rules for intersecting runways below. These 3 rules must always be applied when controlling aircraft that are flying patterns on runways that intersect.
1. Traffic Direction
With intersecting runways it is vital that everyone flies in the same traffic direction. If you have aircraft making left and right traffic on each respective runway, you will have aircraft flying head on in the pattern. This can be avoided by using only one pattern direction for both runways.
If you look at the purple and grey colours in Visual Aid 1.1 you will see that they are both making right traffic. Everyone is flying in the same direction, by doing this you will prevent a head on collision.
Looking at the red and grey colours in Visual Aid 1.2 on the other hand, you will see they are not flying in the same pattern direction. With red making left traffic on runway 35 there is a big risk of a head on collision in the pattern.
2. Upwind Separation
With intersecting runways you have to be careful when clearing aircraft for take off on the different runways. They will be flying over the departure path of another runway, this requires caution. There are two scenarios which must be kept in mind when clearing aircraft for take off.
If you cleared an aircraft for take off on runway 35, making right traffic, he will be flying over the departure path of runway 08. So now, you can’t clear someone for take off on runway 08, otherwise they will crash into each other on upwind. You have to wait until the aircraft that is making right traffic on runway 35 is clear of the departure path of runway 08. So the best course of action would be to send the “Line up and Wait” command to the departure on runway 08.
OR
Sometimes it may not be possible to have an aircraft line up and wait due to traffic that is on final to the runway. In such a scenario you do the following:
Take a look at the green and pink colours in Visual Aid 2.1. You will depart aircraft simultaneously on both runway 35 and 08. Remember we said that the departure on runway 08 can’t wait due to traffic on short final, we need to get him out as soon as possible. Once the departure on runway 35 is airborne, send him the “Extend upwind, I’ll call your crosswind” command. By doing this you ensure that the departure on runway 35 does not immediately turn crosswind and fly over the departure path of runway 08, resulting in a conflict with the departure on runway 08 on upwind. When there is appropriate separation, send the departure on runway 35 the “Turn Crosswind” command. Now he will fall in behind the traffic on runway 08 that is on right crosswind, without conflicting.
3. Downwind Separation
Lastly we will be looking at orange in Visual Aid 3.1. You have to be familiar with the separation rules of Infinite Flight. You must be thinking: “Wow, how on earth will I prevent aircraft from colliding on the runways? It must be so difficult!” Nope, it’s not! The “Extend downwind, I’ll call your base” command is your most important tool that you will use to ensure separation between aircraft on the different runways.This command is your key to success. Here’s how to use it:
Let’s say you have 4 aircraft flying in the pattern. You have 2 aircraft making right traffic on runway 08 and two aircraft making right traffic on runway 35.
Step 1:
• Choose the leading runway. The aircraft on this runway will land before the aircraft on the other runway. For this scenario our leading runway will be runway 35
Step 2:
• Send the “Extend downwind, I’ll call your base” command to the aircraft that is number 1 on runway 08. This number 1 is now following number 2 (the last aircraft) on runway 35.
Step 3:
• Wait until there is appropriate separation between the aircraft that is number 1 on runway 08 and the aircraft that is number 2 on runway 35, then send the “Turn Base” command to number 1 on runway 08 so he can fall in behind number 2 on runway 35. This will ensure that the aircraft on runway 08 doesn’t have to go around due to the traffic on runway 35.
Step 4:
• Chances are that number 1 on runway 35 will already be on right downwind for a second touch and go while number 2 on runway 08 is still on final for his first touch and go. Now runway 08 is your leading runway and you have to send “Extend downwind, I’ll call your base” to number 1 on runway 35 so he can fall in behind number 2 on runway 08.
Step 5:
• Repeat these steps with each pattern! You will notice that this pattern stays the same, you are just switching between the two runways the entire time.
Always take aircraft performance into account. If you have a TBM on final to one runway and an A318 on the other runway, you have to give more spacing between them because the A318 will catch up to the TBM pretty fast, and vice versa. If the TBM is following the A318 you can send the “Turn Base” command earlier than normal because a TBM has a much slower approach speed. Remember that pattern entries and sequencing apply as normal with intersecting runway operations.
Practical Example
I organised a session where I controlled intersecting runways at KPNE, afterwards I sent advice and tips about the session through text so the trainee can look at the replay and my notes simultaneously. I found this method of practically showing the trainee really helped him/her to understand exactly what I mean. I uploaded the replay to YouTube below for easy access and I will attach the link to the replay file of the session here, download it to your device and watch the session along with my feedback below.
Feedback
20:03:12z:
• The first pattern integration is very important. Always try to evenly spread out your traffic on both runways.
20:05:50z:
• Here I used the “Line up and wait” command to ensure seperation on upwind between F-FAXX and S5-MTA. (Rule 2)
20:11:11z:
• The pattern integration came together very nicely here with D-NICO on final for runway 24 falling in behind G-KYSW on final for runway 33. No intervention from the controller was needed here.
20:13:07z:
• I sent the “Extend downwind, I’ll call your base” command to S5-MTA so he can fall in behind N1DL on right downwind for runway 24. (Rule 3 - Step 2)
20:16:20z:
• I sent the “Turn base” command to S5-MTA because there is now satisfactory separation between him and N1DL so he can safely make a touch and go without having to go around. (Rule 3 - Step 3)
20:16:38z:
• I sent the “Extend downwind, I’ll call your base” command to D-NICO so he can fall in behind G-KYSW on right downwind for runway 33. (Rule 3 - Step 2)
20:18:34z:
• Remember, there is no need to send the “Extend downwind, I’ll call your base” command to F-FAXX, because he is sequenced he will follow D-NICO so separation is ensured.
20:19:25z:
• I encourage you to use the opposite downwind when an aircraft requests a runway change. This will expedite your pattern. Be aware that D-NICO will now be behind N1DL who is on left downwind for 33. It is easier to always let “runway follow runway”, otherwise the sequencing can get very confusing.
20:20:49z:
• Here I sent the “Turn base” command to D-NICO too late. There is now too much spacing between him and N1DL who is on left base for runway 33. (Rule 3 - Step 3)
20:22:49z:
• I decided that I will try and correct this huge gap between D-NICO and N1DL by slotting in S5-MTA in front of D-NICO. This worked out very well, by doing this I didn’t waste spacing and prevented S5-MTA from flying an unnecessary long pattern.
20:23:25z:
• Remember to always be on the lookout for possible go arounds. G-KYSW has not fully vacated the runway, resulting in N1DL having to go around.
• Regarding the go around of N1DL on runway 33. With this method of intersecting runways, the only type of go around you want to see is between aircraft landing on the same runway. You don’t want to see a go around between aircraft on different runways. (In this case runway 24 and 33) Because you are using base calls. Separation is your responsibility as the controller, so make sure you give enough spacing between the aircraft. But there is a fine line, don’t give too much spacing otherwise it will cause unnecessary delays and make the pattern very large.
20:25:33z:
• I sent the “Extend Downwind, I’ll call your base” command to N1DL to ensure separation between him and F-FAXX who is on full stop for runway 24. (Rule 3 - Step 2)
Credits
• Firstly a big thank you to @NJ24, my former trainee who has now climbed through the ranks of IFATC and made me very proud, who was always there when I needed him no matter what it was for in the process of making this tutorial. Couldn’t have done it without you!
• Thank you to @lucaviness, @sqeezelemon and @Gliding_Central for all their time and hard work they put into helping me with the design of this tutorial.
• Thank you @Tyler_Shelton , @RAH and @JoshFly8 for your guidance in the final stages.
• Thank you to the wonderful pilots who helped me with the KPNE Practical Example:
@NJ24 (D-NICO)
@DannyHL (N1DL)
@DimitriB (F-FAXX)
@Matevz_Treven (S5-MTA)
@Kyle (G-KYSW)