ATS Surveillance Services

General Procedures

Aircraft identification

For aircraft to be provided ATS surveillance services, aircraft identification must be established, and the pilot informed. Identification should then be maintained until the termination of ATS surveillance.

Identification on a secondary surveillance radar system (SSR) is established by one of the following methods:

Once radar identification has been established the pilot shall be informed. If at any time identification is lost or ATS surveillance service terminated, this pilot shall also be informed.

Position information

Where identification has been performed the aircraft should be informed of its position except in the following cases:

Position information shall be passed in the following forms:

Wherever practical, position information shall be made with reference to positions or routes relevant to the aircraft concerned.

Radar vectoring

Vectoring is achieved by assigning aircraft specific headings which will enable the aircraft to maintain the desired track.

When vectoring an aircraft, controllers should comply with the following:

When vectoring an IFR flight and when giving an IFR flight a direct routing which takes the aircraft off an ATS route, the controller should ensure that the minimum obstacle clearance exists at all times until the aircraft reaches a point where it is able to resume its own navigation.

When radar vectors are terminated, the controller shall issue an appropriate instruction to the aircraft to return it to its pre-planned route, and the aircraft should be instructed to resume own navigation.

Application of separation

Separation shall only be applied with reference to ATS surveillance systems if there is reasonable assurance that identification of aircraft will be obtained and maintained.

When the control of an identified aircraft will be transferred to a sector that applies procedural separation, or a higher separation minima, this separation must be applied before the aircraft enters the next sector, or the sector of airspace where the higher separation minima applies.

Under no circumstances should the symbols on the radar screen touch or overlap unless vertical separation is assured.

Separation minima based on ATS surveillance

SSR/ADS-B/MLAT based separation minima

When aircraft are under ATS surveillance either from SSR, ADS-B or MLAT, the minimum horizontal separation is 5.0 NM.

This may be reduced to 3.0 NM when radar and/or ADS-B and MLAT systems capabilities at a given location permit.

Separation minima on final approach

A minimum separation of 2.5 NM may be applied between aircraft under ATS surveillance when established on the final approach course within 10 NM of the runway threshold provided:

Separation from adjacent airspace

Except where transfer of control to be made, aircraft shall not be vectored closer than 2.5 NM to the boundary of the airspace that a controller is responsible for unless there has been prior coordination with the controller of the adjacent sector. This ensures that minimum horizontal separation will always exist between aircraft in different sectors.

Distance-based wake turbulence separation minima

The following distance-based wake turbulence separation minima shall by applied when aircraft are under ATS surveillance during the approach and departure phases of flight.

These minima shall be applied under the following circumstances:

Preceding Aircraft Category Succeeding Aircraft Category Separation Minima Succeeding Aircraft Category Separation Minima
SUPER
HEAVY 6 NM
MEDIUM 7 NM
LIGHT 8 NM
HEAVY
HEAVY 4 NM
MEDIUM 5 NM
LIGHT 6 NM
MEDIUM LIGHT 5 NM
Aircraft operating directly behind:
icao_aircraft_directly_behind.png
Aircraft crossing behind:

icao_aircraft_crossing_behind.png

Separation from aircraft that are holding

Where vertical separation does not exist between aircraft established in a holding pattern and aircraft not holding, a minimum of 5.0 NM of horizontal separation must exist.

Separation of aircraft on reciprocal tracks

Where confirmation has been obtained from radar derived that aircraft on reciprocal tracks have passed, there is no requirement to ensure that minimum radar separation exists before reducing the minimum vertical separation provided:

Verification of Mode C altitude readout

Verification of pressure-altitude-derived level information Mode C displayed to the controller shall be affected by simultaneous comparison (reported and observed at least once on initial contact by the first controller providing a surveillance service), when an aircraft enters civil controlled airspace after departure from an aerodrome.

Following successful verification, the Mode C information may be considered to remain verified provided it is associated with a Mode A SSR Code that has been previously validated by another controller and that the observed Mode C information has an error of 200ft or less at all levels.

Determination of level occupancy

Maintaining a level

An aircraft may be considered to be maintaining a level when the observed altitude readout is within the tolerances, of the assigned level.

Vacating a level

An aircraft can be considered to have vacated a level during a climb or descent when the observed altitude readout is more than 200ft from the previously occupied level, in the anticipated direction.

Passing a level

An aircraft may be considered to have crossed a level during a climb or descent when the observed altitude readout has passed the level by more than 200ft in the required direction.

Reaching a level

An aircraft may be considered to have reached a level to which it had been cleared when whichever is the greater of 3 sensor or display updates, or 15 seconds has passed since the level information has indicated that it is within the appropriate tolerance.

Departing a runway

Aircraft may be considered to have departed a runway when the surveillance display indicates a positive rate of climb from the aerodrome elevation. However, Mode C information shall not be used when the display varies by more than 200ft from the aerodrome elevation during the take-off roll.


Revision #4
Created 11 October 2024 01:57:29 by Ali
Updated 16 March 2025 19:06:18 by Ali