Skip to content

1.4 Separation Standards

1.4.1 General

Separation standards are applied to ensure that aircraft remain at a safe distance from each other.

The Approach Controller shall apply approved separation minima at all times.

Separation shall only be applied between aircraft that are positively identified.

1.4.2 Lateral Separation

Radar lateral separation is based on distance between aircraft.

Minimum Separation

  • 3 NM – Training / simulation standard
  • 5 NM – Real-world standard (unless otherwise authorised)

The applicable separation standard shall be applied consistently.

1.4.3 Application of Lateral Separation

The Approach Controller shall ensure that:

  • Both aircraft are identified
  • Surveillance information is reliable
  • Distance between aircraft does not reduce below the prescribed minimum

The controller shall apply separation proactively to prevent conflicts.

1.4.4 Vertical Separation

Vertical separation is achieved by assigning different altitudes.

Minimum Separation

  • 1000 ft

1.4.5 Mode C Verification

The Approach Controller shall verify Mode C altitude prior to using it for separation.

The controller shall:

  • Compare pilot-reported altitude with Mode C readout
  • Ensure the difference is within acceptable limits

If Mode C is not verified or unreliable, vertical separation shall not be applied using radar-derived altitude.

1.4.6 Maintaining Separation

The Approach Controller shall:

  • Monitor aircraft continuously
  • Anticipate conflicts before they develop
  • Issue timely control instructions
  • Ensure separation is maintained at all times

Separation shall not be allowed to reduce below the minimum.

1.4.7 Loss of Separation

A loss of separation occurs when the prescribed minimum is infringed.

If separation is lost or at risk, the Approach Controller shall:

  • Take immediate corrective action
  • Issue clear and decisive instructions
  • Restore separation as quickly as possible

1.4.8 Transfer of Separation Responsibility

Separation responsibility remains with the Approach Controller until:

  • Responsibility is transferred to another controller, or
  • Alternative separation methods are applied

1.4.9 Key Principle

Separation is the primary responsibility of the Approach Controller.

The controller shall:

  • Apply separation proactively
  • Monitor continuously
  • Act immediately to prevent or resolve conflicts

Separation shall never be compromised for efficiency.