Minimum separation in air traffic control explained: common 1,000 ft, 3 NM and 5 NM rules, plus RVSM, wake turbulence and key exceptions.
In real-world aviation, minimum separation in air traffic control is the smallest authorised vertical, lateral or longitudinal spacing between aircraft. No single figure applies: common surveillance minima are 5 NM en route and 3 NM in some terminal airspace, while vertical separation is normally 1,000 ft below FL290 and through RVSM levels.
What counts as ATC separation?
Aircraft are separated when at least one authorised separation method is maintained, provided any additional wake-turbulence or runway requirement is also satisfied.
- Vertical separation keeps aircraft at different assigned altitudes or flight levels.
- Lateral separation uses different tracks, headings or protected route areas that do not overlap.
- Longitudinal separation keeps aircraft apart along the same or converging tracks, measured by distance or time.
Two aircraft can occupy nearly the same point on a plan-view display while remaining safely separated by 1,000 ft vertically. Conversely, aircraft at the same level may be separated by protected airspace around different routes rather than a simple radar distance.
Our wider explanation of how tower, approach and area controllers share responsibility shows where these methods are applied during a flight.
What are the common ATC separation minima?
The following figures are common standards, not universal rules; the controlling authority, airspace, surveillance system, procedure and aircraft status determine the applicable minimum.
| Situation | Common minimum | Main qualification |
|---|---|---|
| Below FL290 | 1,000 ft vertical | Local altitude and flight-level procedures still apply |
| FL290–FL410 in designated RVSM airspace | 1,000 ft vertical | RVSM status, equipment and special-handling rules matter |
| Above FL410 | Normally 2,000 ft vertical | Subject to the published regional procedure |
| En-route surveillance | Commonly 5 NM horizontal | May be larger or smaller where specifically authorised |
| Terminal surveillance | Commonly 3 NM horizontal | Requires approved coverage, equipment and procedures |
| Closely spaced final approach | As little as 2.5 NM in some systems | Only under tightly defined final-course and runway conditions |
| Wake-turbulence sequencing | Often 4–8 NM or a time interval | Depends on aircraft categories and the local wake scheme |
| Procedural or oceanic airspace | Published time, distance or lateral standard | No single worldwide figure applies |
Distances are normally expressed in nautical miles; one nautical mile is 1.852 kilometres. FL290 means flight level 290, nominally 29,000 ft using the standard pressure datum of 1013.25 hPa or 29.92 inHg.
A controller cannot reduce a minimum merely because the traffic appears stable. Reduced surveillance separation requires approval, suitable coverage and the correct procedure.
Why is minimum separation not the target spacing?
The minimum is the boundary that must not be crossed, while target spacing includes a working margin for closure, turns, wind, pilot response and runway occupancy.
A trailing aircraft flying 30 kt faster closes half a nautical mile each minute. If a controller waits until it reaches a 5 NM minimum before correcting the speed difference, separation will continue shrinking while the clearance is transmitted, read back and acted upon.
Controllers therefore sequence aircraft with extra room and monitor the trend rather than only the displayed distance. A common simulation mistake is treating 3 NM or 5 NM as the point at which action should begin.
Why can aircraft appear closer than 3 or 5 NM?
Aircraft may legally be closer than a standard surveillance minimum when another authorised form of separation is being used.
- They may have at least the required vertical separation.
- Protected tracks or parallel procedures may provide lateral separation.
- Approved visual separation may be in use under the applicable conditions.
- A reduced terminal or final-approach minimum may have been authorised.
Public tracking displays are not authoritative ATC tools. Their positions may be delayed, rounded or interpolated, and displayed altitude sources may differ. Apparent proximity on such a display does not establish that separation was lost.
Does minimum separation include wake turbulence?
Wake-turbulence spacing is an additional applicable requirement and may demand considerably more distance or time than the ordinary surveillance minimum.
The required spacing depends on the leader and follower categories, whether the aircraft are arriving or departing, and the wake system used by that authority. A controller does not normally discard the prescribed minimum because the wind appears likely to move the wake away.
Runway separation is another distinct constraint. Aircraft can satisfy radar spacing yet still be too close for landing because the preceding aircraft has not vacated the runway. Our detailed breakdown of reduced final-approach spacing, wake limits and runway occupancy covers that specific case.
Does ATC separate every aircraft?
ATC does not provide separation between every possible pair of aircraft in every class of airspace.
The service depends on flight rules, airspace classification and national regulations. IFR traffic generally receives prescribed separation in controlled airspace, but VFR pilots may receive only traffic information in some classes. Outside controlled airspace, pilots often remain responsible for collision avoidance through see-and-avoid procedures.
Receiving a transponder code, radio service or traffic advisory does not by itself mean that ATC has assumed responsibility for separation.
What happens when aircraft go below minimum separation?
A loss of separation occurs when the applicable prescribed minimum is no longer maintained and no alternative authorised form of separation has already been established.
Controllers may issue an immediate heading or altitude change, provide traffic information and co-ordinate with adjoining sectors. Predictive conflict alerts are safety nets rather than separation methods; an alert can occur before an infringement and does not by itself prove that separation was lost.
If airborne collision-avoidance equipment issues a resolution advisory, pilots follow the advisory and notify ATC as soon as workload permits. Clear transmissions and correct readbacks are critical, as explained in our guide to standard controller-pilot calls and readback discipline.
How should flight simmers apply ATC separation?
Flight simmers should select a consistent rule set, intervene before the minimum is reached and apply the most restrictive relevant requirement.
- Choose the standard. Use the rules for the simulated region or network rather than mixing convenient figures from different authorities.
- Project the closure. Watch relative speed, converging headings and altitude trends instead of relying only on present distance.
- Allow a buffer. Leave room for delayed readbacks, slow turns, wind effects, wake spacing and runway occupancy.
- Check pressure references. Use the appropriate local altimeter setting below the transition altitude and standard pressure above the transition level; a wrong setting can cause an altitude deviation despite a correct clearance.
Built-in simulator ATC and AI traffic do not always preserve realistic spacing, so a clearance should not be treated as proof that a conflict cannot occur. Simmers wanting a practical introduction can practise heading, altitude and sequencing decisions in an ATC simulator.