Skip to content

5.1 Coordination Principles

5.1.1 General

Coordination ensures the safe and efficient transfer of control and responsibility between controllers.

The Tower Controller shall coordinate effectively with all adjacent units at all times to prevent conflict and maintain orderly traffic flow.

5.1.2 Objectives of Coordination

The Tower Controller shall aim to:

  • Maintain safe separation between aircraft
  • Ensure smooth and timely transfer of traffic between units
  • Prevent conflicting clearances
  • Maintain efficient traffic flow

All coordination shall support safe and predictable operations.

5.1.3 Responsibility Transfer

Responsibility for an aircraft shall only transfer when:

  • Communication has been established with the receiving controller, and
  • The receiving controller has accepted control

Until transfer is complete, the transferring controller shall remain fully responsible for the aircraft.

The Tower Controller shall not assume responsibility unless positive control has been established.

5.1.4 Types of Coordination

Coordination at Tower level includes:

  • Departure release coordination with Approach
  • Arrival coordination with Approach
  • Runway usage and traffic information exchange
  • Coordination of non-standard or abnormal operations

All coordination shall be conducted in accordance with SOPs and local procedures.

5.1.5 Coordination Methods

Coordination may be achieved by:

  • Voice communication (primary method)
  • Text or coordination systems (where available)
  • Pre-defined procedures (LOAs or SOPs)

All coordination shall be:

  • Clear
  • Timely
  • Unambiguous

5.1.6 Positive Coordination

Positive coordination requires that:

  • Information is clearly transmitted
  • The receiving controller acknowledges the information
  • Both controllers have a shared understanding of the situation

The Tower Controller shall not assume coordination is complete until it has been explicitly confirmed.

5.1.7 Standardisation

Standard procedures reduce workload and minimise error.

The Tower Controller shall:

  • Follow published SOPs and LOAs
  • Use standard phraseology
  • Avoid non-standard coordination unless operationally necessary

5.1.8 Situational Awareness

The Tower Controller shall maintain awareness of:

  • Traffic transferred to and from adjacent units
  • Pending departures awaiting release
  • Arrivals under Approach control

Loss of awareness may result in coordination failure or conflicting instructions.

5.1.9 Error Prevention

To prevent coordination errors, the Tower Controller shall:

  • Confirm all critical coordination
  • Clarify any uncertainty immediately
  • Avoid assumptions regarding traffic status
  • Re-check clearances before issuing

If coordination is unclear or incomplete, the controller shall:

  • Withhold further clearances where necessary
  • Re-establish coordination
  • Maintain separation independently until confirmed

5.1.10 Key Principle

Effective coordination is based on clarity, confirmation, and standardisation.

The Tower Controller shall not act on assumed coordination.

All actions shall be based on confirmed and understood information.