Separation system and vertical minima
Separation keeps controlled aircraft apart by a prescribed minimum. ATC may use a vertical difference, horizontal spacing or an authorised combination, and must establish a replacement before the existing method becomes insufficient.
Where ATC provides separation
| Airspace or operation | Flights separated |
|---|---|
| Classes A and B | All flights admitted to the class |
| Classes C, D and E | IFR from IFR |
| Class C | IFR from VFR |
| Special VFR | IFR from Special VFR, and Special VFR from Special VFR when prescribed |
Vertical, horizontal and composite separation
Vertical separation assigns different levels. Horizontal separation keeps aircraft apart laterally, longitudinally or by surveillance distance. Composite separation combines vertical and horizontal elements whose minima may each be reduced, but never below half of the individual minimum. Composite separation is used only under an applicable regional air-navigation agreement.
Vertical separation minimum
| Level band | Minimum | Condition |
|---|---|---|
| Below FL 290 | 1,000 ft | Normal vertical separation minimum |
| FL 290 through FL 410 | 1,000 ft | Both aircraft RVSM compliant and operating in designated RVSM airspace |
| At or above FL 290 outside RVSM conditions | 2,000 ft | Used when the reduced minimum is not authorised or cannot be maintained |
| Above FL 410 | 2,000 ft | Normal high-level minimum under the applicable cruising-level scheme |
Assigning a vacated level
An aircraft may normally be cleared to a level after another aircraft reports vacating it. The clearance is withheld until the first aircraft reports at or passing another level separated by the required minimum when severe turbulence exists, both aircraft are in the same holding pattern, or their performance difference could erode separation.
Own separation in VMC
At a pilot's request, with the other pilot's agreement and ATC authorisation, an IFR flight in Class D or E may climb or descend in daylight VMC while maintaining its own separation from one other aircraft. The clearance is for a specified portion at or below 10,000 ft. Essential traffic information is passed, and ATC gives an alternative instruction in case VMC cannot be maintained.
Cruise climb
Bali states that cruise climb is not permitted in Indian FIRs. A clearance must assign a level or level band permitted by the applicable procedure rather than assume an unrestricted cruise climb.
Lateral separation by position and track
Lateral separation proves that protected route areas do not overlap. The proof may come from positive position reports, divergent tracks from a common navigation aid or independently protected navigation paths.
Geographical separation
Aircraft are laterally separated when position reports positively place them over different geographical locations whose protected areas do not overlap. The locations may be determined visually or by reference to a navigation aid.
Divergence from the same facility
| Navigation basis | Minimum track divergence | Additional condition |
|---|---|---|
| VOR | 15 degrees | Both established on diverging radials and at least one aircraft 15 NM or more from the facility |
| NDB | 30 degrees | Both established on tracks to or from the NDB, at least one aircraft 15 NM or more from the facility and at least 20 degrees from the other aircraft's reference radial |
| GNSS to GNSS | 15 to 135 degrees measured at the common point | Both established with zero offset and at least one aircraft at the prescribed distance from the common point |
| VOR to GNSS | 15 to 135 degrees measured at the common point | VOR aircraft established on its radial, GNSS aircraft on a zero-offset track and the prescribed distance achieved |
GNSS distance before separation exists
For a divergence between 15 and 135 degrees, Bali uses 15 NM from the common point from FL 010 through FL 190, and 23 NM from FL 200 through FL 600. These are ground distances. When DME supplies distance, the controller accounts for slant range.
Integrity and offsets
Before applying GNSS track separation, ATC confirms that the aircraft is navigating by GNSS and is not applying an authorised strategic lateral offset. GNSS separation is not used after a reported RAIM outage. When aircraft use different aids or RNAV methods, their protected airspaces or applicable RNP containment areas must not overlap.
Track relationships and longitudinal separation
Longitudinal separation protects aircraft one behind another or approaching a common point. Before choosing a time or distance minimum, the controller classifies the angular relationship between the tracks.
Track definitions
| Relationship | Angular difference | Meaning |
|---|---|---|
| Same track | Less than 45 degrees or more than 315 degrees | Same-direction tracks, including intersecting portions, whose protection areas overlap |
| Reciprocal tracks | More than 135 degrees but less than 225 degrees | Opposite or nearly opposite tracks whose protection areas overlap |
| Crossing tracks | All other intersecting relationships | Tracks outside the same and reciprocal sectors |
Longitudinal separation is applied so that the estimated positions of the aircraft never become closer than the prescribed minimum. It may be established by assigning departure times, requiring aircraft to pass a point at stated times, holding an aircraft over a point, assigning an appropriate level change or maintaining a stated distance.
Time-based information
Time separation can use positions and estimates received by voice, CPDLC or ADS-C. Every calculation is cross-checked against the traffic geometry, because a correct subtraction applied to the wrong order of aircraft is still unsafe.
Time-based longitudinal minima
The basic procedural time interval is 15 minutes. It reduces only when position and speed can be checked more frequently, or when the leading aircraft has enough speed advantage and the geometry meets the stated conditions.
Aircraft at the same cruising level
| Situation | Minimum | Conditions |
|---|---|---|
| Same track | 15 minutes | Basic minimum |
| Same track | 10 minutes | Navigation aids permit frequent determination of position and speed |
| Same track | 5 minutes | Leader at least 20 kt faster; both departed same aerodrome, reported over same point, or departure joins the route with five minutes assured |
| Same track | 3 minutes | Same geometry as the five-minute case, but leader at least 40 kt faster |
| Crossing tracks | 15 minutes | Basic minimum at the crossing point |
| Crossing tracks | 10 minutes | Frequent position and speed determination available |
Aircraft climbing or descending
| Relationship | Minimum while vertical separation does not exist |
|---|---|
| Same track | 15 minutes, reducible to 10 minutes with frequent position and speed determination |
| Same track, common reporting point | 5 minutes when the level change starts within 10 minutes of the second aircraft's report over that point |
| Crossing tracks | 15 minutes before and after estimated crossing, reducible to 10 minutes with frequent position and speed determination |
| Crossing tracks, common point | 5 minutes when the level change starts within 10 minutes of the second aircraft's report and any indirect clearance states that restriction |
| Reciprocal tracks | Vertical separation for at least 10 minutes before and after estimated passing when lateral separation is absent |
A clearance transmitted through a third party or by CPDLC includes the restriction needed to preserve the timing condition. The controller does not assume that a level change began at the instant the clearance was issued.
DME, GNSS and surveillance separation
Distance-based separation replaces estimates with simultaneous measured distances. The measurements must refer to the same on-track DME station, the same waypoint or a collocated DME and waypoint.
Common-reference conditions
Both aircraft may use DME, both may use GNSS, or one may use each system. Direct controller-to-pilot VHF communication is maintained. Measurements are obtained simultaneously and often enough to confirm that the minimum will not be infringed. When area-navigation aircraft are involved, the controller specifically requests GNSS-derived distance.
| Geometry | Minimum | Condition |
|---|---|---|
| Same level, same track | 20 NM | Common on-track reference and frequent simultaneous readings |
| Same level, same track | 10 NM | Leader maintains at least 20 kt true-airspeed advantage |
| Same level, crossing tracks | 20 NM | Reference at crossing point, relative angle below 90 degrees and frequent checks |
| Same level, crossing tracks | 10 NM | Same conditions plus leader at least 20 kt faster |
| Climbing or descending, same track | 10 NM | One aircraft maintains a level while vertical separation does not exist |
| Reciprocal tracks | 10 NM after passing | Positive proof that the aircraft have passed each other |
When GNSS distance cannot be used
Loss of GNSS integrity, inadequate airborne equipment or loss of the GNSS input to an integrated navigation system requires another form of separation. A GNSS distance from an integrated system is acceptable only when the system provides the required integrity.
ATS surveillance minima in India
Bali states a normal horizontal surveillance minimum of 5 NM. A 3 NM minimum may be specifically authorised within suitable coverage for Delhi, Mumbai, Bengaluru, Kolkata and Shamshabad radars. When ADS-B or MLAT is combined with radar, the applicable minimum is the radar minimum. MLAT used alone follows the minimum prescribed before implementation.
Mach number and performance-based separation
Mach number technique stabilises relative speed between turbojet aircraft on the same track where surveillance is limited. Performance-based minima then connect navigation, communication and surveillance capability to a permitted spacing.
Mach number technique
Each aircraft agrees to maintain the Mach number assigned by ATC for the specified segment, normally to within Mach 0.01. No speed change is made without clearance unless an emergency requires it. Position reports are supplied at compulsory points by the available long-range communication system.
| Preceding aircraft speed advantage | Typical time interval stated by Bali |
|---|---|
| At least Mach 0.02 faster | 10 minutes |
| At least Mach 0.03 faster | 9 minutes |
| At least Mach 0.04 faster | 8 minutes |
The exact value depends on the applicable Doc 4444 and FIR procedure. On suitable designated RNAV or VOR-defined routes, an 80 NM RNAV distance minimum with Mach number technique may replace the 10-minute interval.
RNP, RCP and RSP
RNP specifies navigation containment. RCP specifies communication transaction performance, including the time for an instruction to reach the aircraft and its acknowledgement to return. RSP specifies surveillance-delivery performance from the service-provider interface to the ATS processing and display system. Performance-based communication and surveillance use these specifications with the aircraft, ground system and operating procedures as one complete chain.
| Separation | RNP | RCP | RSP | Maximum ADS-C periodic interval |
|---|---|---|---|---|
| 50 NM | 10 | 240 | 180 | 27 minutes |
| 50 NM | 4 | 240 | 180 | 32 minutes |
| 30 NM | 2 or 4 | 240 | 180 | 12 minutes |
| 5 minutes | 2, 4 or 10 | 240 | 180 | 14 minutes |
These minima apply only when every required approval, capability and reporting condition is satisfied. If a required performance element is lost, ATC establishes a different valid minimum.
Wake turbulence categories and spacing
A lifting wing sheds counter-rotating vortices from rotation until touchdown. The strongest operational hazard is produced by a heavy aircraft flying slowly, and the following aircraft is most vulnerable when it is lighter, lower and close behind.
Wake categories
| Category | Code | Maximum take-off mass basis |
|---|---|---|
| SUPER | J | An aircraft type specifically designated SUPER, currently represented operationally by the A380-800; not a general mass band |
| HEAVY | H | 136,000 kg or more, except an aircraft designated SUPER |
| MEDIUM | M | More than 7,000 kg but less than 136,000 kg |
| LIGHT | L | 7,000 kg or less |
Procedural time spacing
| Operation | Following relationship | Minimum |
|---|---|---|
| Timed approach | Medium behind Heavy | 2 minutes |
| Timed approach | Light behind Heavy or Medium | 3 minutes |
| Departure from same runway or related parallel or crossing geometry | Light or Medium behind Heavy, or Light behind Medium | 2 minutes |
| Departure from an intermediate point | Light or Medium behind Heavy, or Light behind Medium | 3 minutes |
| Displaced-threshold or opposite-direction conflict described in the procedure | Lighter aircraft exposed to the heavier aircraft's path | 2 minutes |
For a SUPER aircraft, the current AIP and controller procedure provides the applicable time minimum. The category word SUPER or HEAVY is included with the call sign on initial contact where required.
Surveillance wake spacing on approach and departure
| Leading | Following | Minimum |
|---|---|---|
| SUPER | HEAVY | 6 NM |
| SUPER | MEDIUM | 7 NM |
| SUPER | LIGHT | 8 NM |
| HEAVY | HEAVY | 4 NM |
| HEAVY | MEDIUM | 5 NM |
| HEAVY | LIGHT | 6 NM |
| MEDIUM | LIGHT | 5 NM |
Maintaining, changing and restoring separation
A separation minimum is a live condition, not a one-time calculation. The controller monitors the geometry, predicts where the current method will cease to work and establishes the next valid method before that point.
Loss or change of the current method
If the navigation aid, communication, surveillance source, aircraft performance or route geometry needed for a minimum is lost, ATC acts before the minimum is infringed. It may stop a level change, issue vectors, assign another level, change speed, increase longitudinal spacing or revert to a larger procedural minimum.
Transfer and pilot-maintained separation
Transfer of control between ATS units does not create a gap in separation responsibility. The agreed transfer condition specifies the aircraft position, level, clearance and any restriction still in force. Responsibility changes only at the coordinated point or time. A pilot accepts responsibility for separation from one named aircraft only under an authorised visual-separation procedure and after reporting the traffic in sight or agreeing to the stated VMC condition.
Essential traffic information
Essential traffic is controlled traffic to which separation applies but which is not, or will not be, separated from another controlled flight by the required minimum. ATC gives both flights the information needed to understand the conflict, normally including direction, aircraft type and wake category when relevant, level and the estimated position or time of closest approach. Information does not by itself establish separation.
Operational sequence
| Step | Controller logic |
|---|---|
| 1. Identify obligation | Confirm which flights must be separated under the airspace class and operation. |
| 2. Select method | Choose vertical, lateral, longitudinal, surveillance or authorised composite separation. |
| 3. Verify prerequisites | Check navigation source, common reference, communication, performance approval, track geometry and wake category. |
| 4. Apply the minimum | Issue a clearance early enough for the aircraft to achieve and maintain the required value. |
| 5. Monitor | Cross-check reports or surveillance and predict closure, level crossing and geometry change. |
| 6. Replace before failure | Establish another valid method before the current separation becomes insufficient. |
Common exam traps
- Do not use 1,000 ft above FL 290 unless RVSM conditions are satisfied.
- Do not reduce a time minimum unless every speed, reporting and common-point condition is met.
- Do not mix distances from unrelated DME stations.
- Do not confuse traffic information with ATC separation.
- Do not apply a smaller surveillance minimum when wake turbulence requires more.
- Do not authorise cruise climb in an Indian FIR.