Skip to content

2.1 Runway Operations

2.1.1 General

Runway operations are the primary responsibility of the Tower Controller.

The controller shall ensure that the runway is:

  • Safe
  • Protected
  • Free from conflict

No clearance shall be issued that would result in a loss of separation or unsafe runway occupancy.

2.1.2 Runway Occupancy

A runway shall be considered occupied when:

  • An aircraft is taking off or landing
  • An aircraft is lined up and waiting
  • An aircraft or vehicle is crossing or positioned on the runway
  • A landing aircraft has not fully vacated the runway
  • A departing aircraft has not become airborne and passed the departure end

A runway shall not be considered clear until all traffic has vacated and no conflict exists.

2.1.3 Runway Protection

The Tower Controller shall protect the runway at all times.

This includes ensuring:

  • No conflicting aircraft are on final approach
  • No aircraft or vehicles are occupying the runway
  • Adequate separation exists between successive movements
  • Instructions issued will not create a conflict

Where doubt exists, the controller shall withhold clearance until safety can be assured.

Failure to adequately protect the runway may result in a runway incursion or loss of separation.

2.1.4 Issuing Runway Clearances

Before issuing any runway-related clearance, the Tower Controller shall:

  • Verify the runway is clear of traffic
  • Confirm no conflicting aircraft are on approach
  • Assess spacing between arriving and departing aircraft
  • Ensure wake turbulence requirements are met
  • Maintain awareness of all aircraft at holding points

Clearances shall only be issued when positive separation is assured.

The controller shall not issue a clearance if any uncertainty exists regarding runway status or traffic position.

2.1.5 Line Up and Wait (LUAW)

Line Up and Wait may be used to improve traffic efficiency.

The Tower Controller shall only issue a LUAW clearance when:

  • The runway is clear and safe to enter
  • No aircraft is on short final or within unsafe proximity
  • The controller can maintain continuous situational awareness
  • There is no risk of runway conflict

The controller shall continuously monitor the aircraft after issuing LUAW.

LUAW shall not be used where traffic complexity or workload may reduce situational awareness.

2.1.6 Line Up Behind (LUB)

Line Up Behind may be used to position an aircraft on the runway behind preceding traffic.

The Tower Controller shall only issue a Line Up Behind clearance when:

  • The preceding aircraft is clearly visible to both the controller and the pilot
  • The instruction explicitly references the preceding traffic
  • No conflict will occur with landing or departing aircraft
  • Adequate spacing will exist for subsequent departure

The controller shall ensure that:

  • The pilot correctly identifies the referenced aircraft
  • No ambiguity exists in the instruction
  • Continuous monitoring is maintained

Line Up Behind shall not be used when:

  • Visibility is insufficient for traffic identification
  • Traffic complexity increases the risk of confusion
  • There is any doubt regarding pilot understanding

Example Phraseology: 

GFA123, behind landing traffic, line up runway 27 behind.
GFA123, behind departing A320, line up runway 27 behind.

2.1.7 Take-Off Clearance

Take-off clearance shall only be issued when:

  • The runway is confirmed clear
  • Required separation exists from preceding traffic
  • No landing aircraft conflict exists

The controller shall ensure that the departure can be conducted safely without risk of conflict.

A take-off clearance shall not be issued if:

  • A conflicting aircraft is on final approach
  • Runway occupancy cannot be assured
  • Wake turbulence separation cannot be achieved

2.1.8 Conditional Clearances

Conditional clearances may be issued for runway entry or crossing, subject to a specified condition.

The Tower Controller shall only issue a conditional clearance when:

  • The condition relates to a clearly identifiable aircraft or movement
  • The condition is stated first in the instruction
  • The controller is certain the condition can be safely met
  • There is no risk of misunderstanding

Conditional clearances shall not be used for:

  • Take-off clearance
  • Landing clearance

The pilot shall not act on the clearance until the condition has been met.

The controller shall monitor compliance and be prepared to intervene if required.

Example Phraseology: 

GFA123, after landing traffic, line up runway 27.
GFA456, after departing traffic, cross runway 27.

2.1.9 Landing Clearance

Landing clearance shall only be issued when:

  • The runway is clear or will be clear in sufficient time
  • No departing or crossing aircraft will create a conflict
  • Safe spacing from preceding traffic is assured

Where runway occupancy is uncertain, landing clearance shall be delayed.

A landing clearance shall not be issued if:

  • Runway availability is uncertain
  • A departing aircraft will not vacate in time
  • Separation cannot be guaranteed

2.1.10 Phraseology

Standard ICAO phraseology shall be used at all times.

Examples: 

GFA123, line up and wait runway 27.
GFA123, hold short runway 27.
GFA123, wind 270 degrees 8 knots, runway 27, cleared for takeoff.
GFA456, runway 27, cleared to land.

2.1.10 Phraseology

Standard ICAO phraseology shall be used at all times.

Examples:

GFA123, line up and wait runway 27.
GFA123, hold short runway 27.
GFA123, wind 270 degrees 8 knots, runway 27, cleared for takeoff.
GFA456, runway 27, cleared to land.

2.1.11 Key Principle

Runway safety is the highest priority in Aerodrome Control.

If there is any doubt regarding:

  • Runway occupancy
  • Aircraft position
  • Separation

The controller shall not issue a clearance until the situation is fully resolved.