Skip to content

02 6.2 Identification of Emergencies

6.2 Identification of Emergencies

Early identification of an emergency or abnormal situation is critical to ensuring timely and effective assistance.

The Tower Controller shall remain vigilant for both declared and undeclared emergencies at all times.

6.2.1 Methods of Identification

Emergencies may be identified through:

  • Pilot declaration
  • Radio communication abnormalities
  • Observed aircraft behaviour
  • Transponder (SSR) codes
  • Reports from other aircraft, ATC units, or airport authorities

The Tower Controller shall treat any indication of abnormality as a potential emergency.

6.2.2 Pilot-Declared Emergencies

Pilots may declare an emergency using standard ICAO phrases:

  • MAYDAY (Distress – serious and/or imminent danger)
  • PAN PAN (Urgency – safety concern requiring priority)

Upon declaration, the Tower Controller shall:

  • Acknowledge immediately
  • Provide priority handling
  • Avoid unnecessary questioning
  • Offer assistance as required

Example:

GFA123, MAYDAY MAYDAY MAYDAY, engine failure, request immediate landing.  
GFA123, roger MAYDAY, runway 27 cleared to land, wind 270 degrees 8 knots.

6.2.3 Non-Declared Emergencies

Not all emergencies are declared. The Tower Controller shall identify abnormal situations such as:

  • Loss of communication (R/T failure)
  • Erratic or unusual aircraft behaviour
  • Abnormal speed, altitude, or track deviations
  • Repeated or incorrect readbacks
  • Indications of pilot confusion or distress

In such cases, the Tower Controller shall:

  • Attempt to clarify the situation
  • Provide simple and clear instructions
  • Prepare for escalation to full emergency handling

6.2.4 Transponder Codes

Certain SSR codes indicate emergency conditions:

  • 7700 – General emergency
  • 7600 – Radio failure
  • 7500 – Unlawful interference

Upon observing these codes, the Tower Controller shall:

  • Treat the situation as an emergency
  • Avoid requesting unnecessary confirmation
  • Apply appropriate emergency procedures immediately

6.2.5 Indicators of Abnormal Situations

The Tower Controller shall remain alert to indicators including:

  • Requests for priority without formal declaration
  • Reports of technical issues (e.g. hydraulic, navigation, pressurisation)
  • Weather avoidance requests outside normal operations
  • Unstable or extended approaches
  • Repeated go-arounds due to performance or control issues

Such situations may escalate and shall be managed proactively.

6.2.6 Controller Actions on Identification

Upon identification of an emergency or abnormal situation, the Tower Controller shall:

  • Acknowledge immediately
  • Establish the nature of the problem if not already clear
  • Prioritise the aircraft over all other traffic
  • Ensure runway and airspace availability
  • Coordinate with relevant units without delay

The Tower Controller shall not delay action in order to obtain complete information where safety is affected.

6.2.7 Example

GFA456, we have a technical issue, request priority landing.  
GFA456, roger, runway 27 cleared to land, wind 270 degrees 10 knots.

6.2.8 Key Principle

Any uncertainty shall be treated as a potential emergency.

The Tower Controller shall:

  • Act early
  • Prioritise immediately
  • Maintain continuous monitoring
  • Be prepared to escalate the situation at any time

Failure to recognise an emergency in a timely manner may result in loss of separation or unsafe outcomes.