Skip to content

03 6.3 Types of Emergencies

6.3 Types of Emergencies

Aircraft emergencies may arise from technical, operational, or medical causes.

The Tower Controller shall identify the nature of the emergency and apply appropriate handling to ensure safety.

6.3.1 Engine Failure

Engine failures are most critical during take-off and initial climb.

The Tower Controller shall:

  • Prioritise the aircraft immediately
  • Ensure the runway is available
  • Stop departures where required
  • Provide wind and runway information without delay

Example:

GFA123, MAYDAY MAYDAY MAYDAY, engine failure after departure.  
GFA123, roger MAYDAY, runway 27 cleared to land, wind 270 degrees 8 knots.

6.3.2 Radio Communication Failure (R/T Failure)

Loss of communication may be indicated by:

  • No response to calls
  • Incorrect or incomplete readbacks
  • SSR code 7600

The Tower Controller shall:

  • Continue transmitting instructions assuming the aircraft can receive
  • Observe the aircraft for compliance
  • Apply standard radio failure procedures
  • Ensure separation from other traffic

The Tower Controller shall not assume the aircraft is unable to receive transmissions.

Example:

GFA456, if you read, squawk IDENT.

6.3.3 Medical Emergencies

Medical situations may require priority handling.

The Tower Controller shall:

  • Provide priority handling
  • Minimise delay
  • Coordinate with emergency services where required

Example:

GFA789, PAN PAN, medical emergency onboard, request priority landing.  
GFA789, roger PAN PAN, runway 27 cleared to land.

6.3.4 Aircraft Systems Failure

Failures may include:

  • Hydraulic failure
  • Electrical failure
  • Navigation system failure
  • Pressurisation issues

The Tower Controller shall:

  • Provide priority handling as required
  • Allow extended or modified approaches
  • Avoid complex or non-essential instructions

6.3.5 Unlawful Interference (Hijack)

Unlawful interference may be indicated by SSR code 7500 or pilot report.

The Tower Controller shall:

  • Acknowledge discreetly
  • Avoid actions that may increase risk
  • Continue normal service unless otherwise required
  • Follow local security procedures

The Tower Controller shall not request confirmation of unlawful interference unless necessary.

6.3.6 Fuel Emergencies

Aircraft may report:

  • Minimum fuel (advisory)
  • Fuel MAYDAY (emergency)

The Tower Controller shall:

  • Monitor aircraft reporting minimum fuel closely
  • Provide priority when a fuel emergency is declared
  • Avoid delays

Example:

GFA321, MAYDAY MAYDAY MAYDAY, fuel emergency.  
GFA321, roger MAYDAY, runway 27 cleared to land.

6.3.7 Unstable Approach

Indicators may include:

  • Excessive speed or descent rate
  • Incorrect configuration
  • Poor alignment

The Tower Controller shall:

  • Monitor the approach closely
  • Be prepared to issue a go-around
  • Maintain separation from other traffic

6.3.8 Runway Incidents

Runway incidents may include:

  • Aircraft unable to vacate the runway
  • Vehicles or obstructions on the runway
  • Disabled aircraft

The Tower Controller shall:

  • Stop all arrivals and departures
  • Issue go-arounds where required
  • Coordinate with ground and emergency services

6.3.9 Bird Strike and Environmental Hazards

Hazards may include:

  • Bird activity or bird strike
  • Severe weather
  • Foreign Object Debris (FOD)

The Tower Controller shall:

  • Provide relevant information to affected aircraft
  • Allow flexibility in routing or approach
  • Monitor affected aircraft closely

6.3.10 Key Principle

The Tower Controller shall prioritise the nature and severity of the emergency.

The controller shall:

  • Provide clear and concise instructions
  • Avoid overloading the pilot with information
  • Continuously reassess the situation
  • Adapt control actions as required

All emergency handling shall be focused on maintaining safety and control of the traffic situation.