Skip to content

5.3 Arrival Coordination

5.3.1 General

Arrival coordination ensures the safe and efficient integration of inbound aircraft into the aerodrome environment.

The Tower Controller shall coordinate with Approach Control to maintain safe separation, establish an orderly landing sequence, and ensure efficient runway utilisation.

5.3.2 Principles of Arrival Coordination

Arrival coordination shall ensure:

  • Safe separation between aircraft
  • An orderly and predictable landing sequence
  • Efficient use of the runway
  • Minimal delay and disruption

The Tower Controller shall maintain continuous awareness of all inbound traffic and expected sequencing.

5.3.3 When Coordination is Required

Coordination shall be conducted when:

  • An Approach or Radar controller is online
  • Aircraft are transferred on final approach
  • Special handling is required (e.g. priority or emergency)
  • Sequencing adjustments are necessary

Where no higher unit is online, the Tower Controller shall assume responsibility for sequencing and separation beyond the aerodrome, as defined by local procedures.

5.3.4 Transfer from Approach

Aircraft shall normally be transferred from Approach:

  • Established on final approach
  • At a defined distance from touchdown
  • With sequencing already assigned

Upon transfer, the Tower Controller shall:

  • Acknowledge the aircraft
  • Confirm runway and continue approach instruction
  • Monitor spacing and runway occupancy

Example:

APP → TWR: GFA456, established ILS runway 27.  
TWR: GFA456, continue approach runway 27.

5.3.5 Sequencing Arrivals

The Tower Controller shall ensure:

  • Adequate spacing between successive arrivals
  • Wake turbulence separation is applied
  • Runway occupancy allows safe landing

The Tower Controller shall not alter the sequence without coordination with Approach unless required for safety.

Sequencing adjustments may include:

  • Requesting spacing from Approach
  • Adjusting circuit traffic
  • Instructing a go-around where required

5.3.6 Landing Order Management

Landing order shall be:

  • Established as early as possible
  • Communicated to pilots where necessary
  • Adjusted only when safe and operationally required

The Tower Controller shall:

  • Avoid last-minute sequence changes
  • Prevent compression of spacing
  • Anticipate potential conflicts

Example:

GFA456, number two, follow traffic on short final.

5.3.7 Runway Occupancy Considerations

Before issuing landing clearance, the Tower Controller shall ensure:

  • The runway is clear or will be clear in sufficient time
  • The preceding aircraft has vacated or is vacating
  • No conflicting runway movements are authorised

The Tower Controller shall monitor:

  • Exit taxiways
  • Aircraft vacating performance
  • Potential delays affecting runway availability

A landing clearance shall not be issued if runway availability is uncertain.

5.3.8 Missed Approach / Go-Around Coordination

If an arrival cannot land safely, the Tower Controller shall:

  • Issue a go-around immediately
  • Inform Approach Control where required
  • Re-sequence the aircraft

The Tower Controller shall:

  • Protect the missed approach path
  • Ensure separation from other traffic
  • Update the traffic sequence accordingly

Example:

GFA456, go around, I say again go around.

5.3.9 Coordination with Approach

The Tower Controller shall coordinate with Approach when:

  • Changing the landing sequence significantly
  • Multiple go-arounds occur
  • The runway becomes unavailable
  • Traffic demand exceeds capacity

Effective coordination ensures safe, predictable, and efficient operations.

5.3.10 Key Principle

Arrival coordination shall be proactive and continuous.

The Tower Controller shall:

  • Prioritise safety over efficiency
  • Plan sequencing early
  • Maintain continuous situational awareness
  • Act early to prevent conflicts

Failure in arrival coordination may result in:

  • Loss of separation
  • Go-arounds
  • Runway incursions
  • Increased workload and reduced safety margins