When there is no controller online, pilots use advisory frequencies to coordinate with each other. It is not a chat channel, and it is not for pretending to be ATC. Its purpose is to keep traffic safe, predictable, and cooperative.
Most problems happen when pilots talk about irrelevant topics, don’t report key actions, or don’t pay attention to what others are doing. Another big challenge is sequencing safely without a controller.
In today’s S.O.A.R article, we will explore some rules and suggestions to flying in an uncontrolled airspace.
Listen First, Speak Second
Before transmitting, listen to what others are doing and notice which runway other pilots are using. Read (or listen to) recent position reports and build a mental picture of the traffic flow.
Speak when what you say will help others understand where you are, what you’re doing, or what you intend to do and feel free to ask short, relevant questions when needed to coordinate safely.
Report Key Actions
Report movements that affect others, especially near the runway:
- Joining or leaving the pattern
- Turning base or final
- Entering the runway
- Departing
- Vacating the runway
- Crossing a runway others may use
Avoid narrating every tiny correction and remember: if in doubt, it’s better to make one useful call too many than one too few. Keep transmissions short, clear, and relevant.
Self-Sequencing: Principles First
When there’s no ATC, pilots must sequence themselves. Start with what is actually regulatory:
ICAO right-of-way (simplified)
- Aircraft on final generally have priority over those on the ground intending to depart.
- The lower aircraft on approach usually has right of way (without cutting in).
- Overtaking aircraft must keep clear.
- Never force another aircraft to deviate suddenly.
These are rules, not suggestions, and they should guide every decision.
Practical Spacing Tips (Rules of Thumb)
These are guidelines, not mandatory procedures. Use judgment, communicate, and always prioritize safety.
1) Keep Comfortable Distance
For pattern and approach work, aim to give the aircraft ahead enough space that you could safely land (or go around) without rushing. For many jets, a simple rule of thumb works:
- ~7 NM behind another jet works well in most approach situations, or usually a 2 minutes trail. This distance corresponds to a light aircraft behind a super. In other cases, this distance can be lowered
For slower GA traffic, spacing is often easier to judge using time instead of miles:
- Think in terms of 2–3 minutes between aircraft on final, adjusted for speed.
2) Speed-Based Jet Spacing (optional)
These guidelines mainly make sense for jets:
- Maintain 180 kt until ~6 DME
- Maintain 160 kt until ~4 DME
Use them only when they help sequencing, not if they make your approach unstable.
3) When in Doubt: Ask
If you don’t know how fast the aircraft ahead is flying or what they intend to do, ask politely and adjust accordingly.
Pattern and Runway Coordination
- One aircraft on the runway at a time — wait if unsure.
- Join behind established traffic — don’t cut in. Extend downwind/base if needed.
- Departures respect arrivals — if someone is 2–3 miles on final, wait.
- Go-around if spacing collapses — announce clearly and re-sequence.
Format calls clearly:
“Copenhagen traffic, SAS744, 7 miles final runway 22L, full stop.”
En-Route Spacing (Big Picture)
In cruise, controllers normally use larger buffers than pattern spacing. As a rough mental model:
- Expect 10 NM or more between aircraft,
- or roughly 2/3 minutes in trail at typical jet speeds to adjust for ground speed differences.
- Worst case, you can always climb or descend to avoid conflict. Just make sure to report it so the other traffic doesnt do the same.
Again, this is not a fixed rule, just awareness to avoid flying on top of each other.
Conclusion
Advisory frequencies work when pilots act professionally:
- Listen first
- Communicate clearly (but not endlessly)
- Follow right-of-way rules
- Use simple spacing techniques
- Go around when something doesn’t look safe