Emergency Communications
Emergency Communications
Article Information
Category:
Content source:
Content control:
Last modified:
01.Apr.2025
Article UID:
Cite This Page
SKYbrary Aviation Safety. (April 1, 2025). Emergency Communications.
Retrieved June 3, 2026
from https://skybrary.aero/articles/emergency-communications
UID: 22889
Copied!
COPY
Description
When flight crew are confronted with an emergency or abnormal situation whilst in flight, they normally prioritise their immediate actions in the following order:
- Aviate;
- Navigate;
- Communicate.
Aviate
The pilot’s immediate priority is to ensure the safe flight path and condition of the aircraft. This not only includes the flying of the aircraft but also the completion of checklist drills. The safe flight path may even include the initiation of a controlled rapid descent.
For a modern two-crew flight deck, the flight crew distribute the responsibilities between the available crew members. Under normal conditions, one flight crew member (pilot flying) takes responsibility for the flight path of the aircraft while the other flight crew member (pilot not flying or pilot monitoring) deals with all radio communications and actions/reads out checklists. In order to maintain the correct balance of workload in an emergency when additional QRH checklists and AFM procedures may be required, the pilot flying will often assume responsibility for radio communications.
When there is a significant problem, the workload during the first moments is often high and the flight crew may elect to inform air traffic control immediately by the most direct means. This normally entails the use of an initial call incorporating the word “standby”.
Navigate
The flight crew will decide on whether to continue the flight to the originally intended destination, initiate an immediate en route diversion, carry out an emergency descent or just place the aircraft in a safe flying position. The decision to divert may be immediate but normally it will require coordination with air traffic control and other parties.
Communicate
Pilots believing themselves to be facing an emergency situation should declare an emergency as soon as possible and cancel it later if the situation allows.
The correct method of communicating this information to ATC is by using the prefix “MAYDAY, MAYDAY, MAYDAY” or “PAN PAN, PAN PAN, PAN PAN” as appropriate. This procedure, which is an international standard, is the single most effective means of alerting the controller to the need to give priority to the message that will follow.
In certain types of emergency (Fire in the Air, Loss of Cabin Pressurisation), the flight crew will don oxygen masks. The wearing of oxygen masks may make the voice messages more difficult to understand and increases the risk of a clearance being misunderstood and the risk of readback/hearback errors.
Controller response to emergency situation
The Operators Guide to Human Factors in Aviation Briefing Note - Pilot-Controller Communication offers the following advice:
"Controllers should recognize that, when faced with an emergency situation, the flight crew’s most important needs are:
- Time;
- Airspace; and,
- Silence."
The briefing note continues: "The controller’s response to the emergency situation could be patterned after the ASSIST memory aid...:
- Acknowledge - Ensure that the reported emergency is well-understood and acknowledged;
- Separate - Establish and maintain separation with other traffic and terrain;
- Silence - Impose silence on your control frequency, if necessary; and do not delay or disturb urgent cockpity action by unnecessary transmissions;
- Inform - Inform your supervisor and other sectors, units and airports as appropriate;
- Support - Provide maximum support to the flight crew; and,
- Time - Allow the flight crew sufficient time to manage the emergency."
EUROCONTROL has produced guidelines for controller training in handling unusual or emergency situations which contain much useful information and advice, including sample checklists for various types of emergency.
Further Reading
- ICAO Annex 10 Volume II Chapter 5 Section 5.3.2;
EUROCONTROL European Action Plan for Air-Ground Communications Safety
- AGC Briefing Note 1 - General;
- Guidelines for Controller Training in the Handling of Unusual/Emergency Situations;
UK CAA
- CAP745: Aircraft Emergencies - Considerations for Air Traffic Controllers;
- CAP 413 Radiotelephony Manual, 23rd edition, effective 17 August 2020.
What Links Here (116)
- Fuel - Company Policy
- North Atlantic Operations - Contingency
- DC10, Sioux City USA, 1989
- BA11, en route, Didcot UK, 1990
- JS41, en-route, North West of Aberdeen UK, 2008
- A346, en-route, near Amsterdam Netherlands, 2005
- A333, Hong Kong China, 2010
- A388, en-route Batam Island Indonesia, 2010
- B744, vicinity Dubai UAE, 2010
- B734, Amsterdam Netherlands, 2010 (1)
- LJ24, vicinity Bornholm Denmark, 2012
- DH8A, en-route SSE of Madang, Papua New Guinea, 2011
- A139, vicinity Sky Shuttle Heliport Hong Kong China, 2010
- SB20, vicinity Sumburgh, UK 2014
- B738, en-route, near Lugano Switzerland, 2012
- A332 MRTT, en-route, south eastern Black Sea, 2014
- B752, vicinity Keflavik Iceland, 2013
- B773, Paris CDG France, 2013
- E145, vicinity Manchester UK, 2001
- L35 / EUFI, manoeuvring, Olsberg-Elpe, Germany 2014
- A320, vicinity Abu Dhabi UAE, 2012
- A320, en route, north of Marseilles France, 2013
- A346, en route, eastern Indian Ocean, 2013
- A388, en-route, northern Afghanistan, 2014
- DH8D, en route, west-northwest of Dublin Ireland, 2015
- A332, vicinity Brisbane Australia, 2013
- AT75, en-route, north of Visby Sweden, 2014
- CRJ2, en-route, northern Sweden, 2016
- F16 / C150, vicinity Berkeley County SC USA, 2015
- A320, vicinity Dublin Ireland, 2015
- B738, Delhi India, 2014
- A320, Jaipur India, 2014
- B738, vicinity Trivandrum India, 2015
- CL60 / A388, en-route, Arabian Sea, 2017
- A320, Singapore, 2015
- SB20, en-route, Muzzano Switzerland, 2013
- RJ1H, vicinity Gothenburg Sweden, 2016
- B763, Warsaw Poland, 2011
- B773, en-route, north northwest of Adelaide Australia, 2017
- B738 / B738, Toronto Canada, 2018
- A333, en-route, southern Myanmar, 2013
- A333, vicinity Gold Coast Queensland Australia, 2017
- C130 / C27J, manoeuvring, near Mackall AAF NC USA, 2014
- B789, en-route, eastern Belgium, 2017
- A320, vicinity Perth Australia, 2015
- B773, Abu Dhabi UAE, 2016
- SF34, vicinity Sydney Australia, 2017
- E190, en-route, southwest of Turku Finland, 2017
- B764, en-route, Audincourt France, 2017
- AT76, en-route, east of Cork Ireland, 2016
- A320, en-route, east of Cork Ireland, 2017
- RJ85, en-route, near Musina South Africa, 2017
- B734, en-route, eastern England UK, 2018
- A320, en-route, west southwest of Karachi Pakistan, 2018
- A320, en-route, northeast of Granada Spain, 2017
- A319, vicinity Glasgow UK, 2018
- A320, vicinity Tallinn Estonia, 2018
- A320, Macau SAR China, 2018 (1)
- A333, en-route, southeast of Alice Springs Australia, 2016
- AT75, en-route, near Almansa Spain, 2017
- C560, vicinity Oslo Norway, 2017
- B738, en-route, near Toyama Japan, 2018
- AT75, Port Vila Vanuatu, 2018
- AT75, vicinity Nelson New Zealand, 2017
- S76, en-route, southeast of Lagos Nigeria, 2016
- A319, London Heathrow UK, 2013
- A333, vicinity Orlando FL USA, 2013
- AS3B, vicinity Den Helder Netherlands, 2006
- A333, en-route, near Bournemouth UK, 2012
- A320, en-route, north of Swansea UK, 2012
- B739, en-route, east of Denver CO USA, 2012
- Air-Ground Voice Communications
- Electrical Fires
- Wing Fire
- Engine Failure in Cruise
- In-Flight Fire: Guidance for Controllers
- In-Flight Fire: Guidance for Flight Crews
- Pressurisation Problems: Guidance for Controllers
- Pilot Workload
- Radio Silence
- Emergency Hand Signals
- Ditching: Fixed Wing Aircraft
- Engine Failure During Takeoff - Multi-Engine Transport Category Jet Aircraft
- Checklists and Procedures for Non-Alerted Fire/Smoke/Fume Events
- Engine/APU on Fire: Guidance for Controllers
- Direct Emergency Communication
- Ditching: Rotary Wing Aircraft
- Emergency Descent: Guidance for Controllers
- Emergency Landing - Guidance for Controllers
- Engine Failure: Guidance for Controllers
- ETOPS Diversion at Night (OGHFA SE)
- Fuel Dumping: Guidance for Flight Crews
- Fuel Emergencies: Guidance for Controllers
- Fuel Starvation, Stress, Fatigue and Nonstandard Phraseology (OGHFA SE)
- Hydraulic Problems: Guidance for Flight Crews
- ICAO Emergency Phases
- In-flight Pilot Incapacitation (OGHFA SE)
- Emergency Frequency (SKYclip)
- Landing Gear Failure (OGHFA SE)
- Loss of Cabin Pressurisation
- Loss of Control and In-Flight Upset After Loss of Engine Power (OGHFA SE)
- Medical Emergencies - Guidance for Flight Crew
- Pilot-Controller Communications (OGHFA BN)
- Pressurisation Problems: Guidance for Flight Crews
- Risk Assessment During Onboard Fire and Smoke (OGHFA SE)
- Unidentified Fire On Board (OGHFA SE)
- A321, vicinity London Gatwick, UK 2020
- CVLP, en-route, east of Miami Opa Locka USA, 2019
- A320, vicinity London Heathrow UK, 2019
- B738, en-route, Aegean Sea, 2019
- B738, Goa India, 2016
- A320, en-route, north of Marseilles France, 2017
- A320, en-route, northwest Greece, 2017
- C441, en-route, east southeast of Broome Australia, 2018
- B733, en-route, north of Narrandera NSW Australia, 2018
- B763, Madrid Barajas Spain, 2020






