Discussion of key phrases and communication procedures used in emergency situations along with real-life cases and analysis of responses.
In aviation, emergencies are not managed by instinct alone — they are managed by communication discipline. When systems fail, weather deteriorates, or time pressure increases, the quality of radio communication can determine whether a situation stabilizes or escalates.
In a high-stress cockpit environment, the difference between a controlled recovery and a disaster often comes down to just a few words. When things go wrong, the luxury of polite conversation disappears and is replaced by a rigid, hierarchical structure designed to save lives.
Emergency communication is designed to be:
- Standardized
- Predictable
- Concise
- Unambiguous
This article explores:
- Key ICAO emergency phrases
- Communication procedures
- Real-life cases in aviation history
- Analysis of appropriate and inappropriate responses
1. The Foundation: Standard Emergency Signals
The Distress Hierarchy: Mayday vs. Pan-Pan
The global framework for aviation emergency communication is defined by the International Civil Aviation Organization (ICAO) and distinguishes between “Life-Threatening” and “Urgent but Stable.” Using the correct prefix immediately tells Air Traffic Control (ATC) how to clear the skies for you.
There are two internationally recognized distress categories:
🔴 MAYDAY (Repeated 3 times) — indicates distress
Used when the aircraft is in grave and imminent danger and requires immediate assistance.
Examples:
- Engine failure after takeoff
- Onboard fire
- Severe structural damage
- Loss of control
Structure:
- “MAYDAY, MAYDAY, MAYDAY”
- Callsign
- Nature of emergency
- Intentions
- Position / altitude
- Assistance required
Example:
“MAYDAY MAYDAY MAYDAY, ABC123, engine failure, maintaining three thousand feet, returning to departure airport.”
🟠 PAN-PAN (Repeated 3 times) — indicates urgency
Used for urgent situations, related to the safety of an aircraft or person, but which are not immediately life-threatening.
Examples:
- Technical malfunction – a minor system failure that doesn’t affect flight characteristics
- Passenger medical emergency
- Fuel concern (not critical)
Example:
“PAN-PAN, PAN-PAN, PAN-PAN, ABC123, request priority due medical emergency on board.”
Communication Priorities in Emergencies
Procedural Hierarchy
Communication must never interfere with aircraft control. In emergency situations, communication follows three principles:
- Aviate
- Navigate
- Communicate
If you find yourself overwhelmed, remember the pilot’s fundamental priorities are:
- Flying the airplane first.
- Determining where you are going.
- Talking to the ground only after the first two are under control.
Key Phrases and Their Functions for High-Stress Moments
Clarity and brevity are essential.
Below are the primary phrases used during emergency operations:
| Phrase | Function |
| “Unable” | Refuses unsafe instruction |
| “Standby” | Delays response due to workload |
| “Request immediate vectors” | Needs urgent assistance |
| “Declaring emergency” | Escalates status formally |
| “Negative” | Corrects misunderstanding |
| “Cancel emergency” | Used once the danger has passed (e.g., an engine is successfully restarted). |
| “Souls on Board” | Total count of humans (crew + passengers). Emergency services need this number to ensure everyone is accounted for after a crash. |
| “Minimum Fuel” | A warning that any undue delay will result in an emergency. It is not an emergency yet, but it puts ATC on high alert. |
Real-Life Cases and Communication Analysis
Case 1: Ditching in the Hudson (US Airways Flight 1549)
After a bird strike, both engines failed shortly after takeoff.
Captain’s transmission: “Mayday, Mayday, Mayday… unable.”
Communication characteristics:
- Immediate MAYDAY
- Clear statement of inability
- Short, controlled exchanges
- No unnecessary details
Analysis: ATC responded calmly and offered runway options. There was no panic tone or over-explaining; the focus remained on actionable information.
Lesson: Calm brevity under pressure supports effective coordination. In an emergency, brevity is safety.
Case 2: Fuel Emergency – Phraseology Gap (Avianca Flight 52)
The crew repeatedly indicated fuel concerns but did not formally declare “fuel emergency.”
They used: “We’re running out of fuel”
instead of “Mayday — fuel emergency.”
Analysis: ATC did not recognize the urgency due to the lack of standard phraseology, which triggered misinterpretation. There was a cultural hesitation to declare an emergency and no explicit prioritization request.
Lesson: If it is critical, declare it explicitly. Never use “soft” language in a hard situation. If you need priority, you must declare an emergency.
Case 3: Runway Collision – Communication Breakdown (Tenerife Airport Disaster)
Two Boeing 747 aircraft collided on the runway in low visibility.
Communication Issues Identified:
- Non-standard phraseology
- Ambiguous wording (“We are now at takeoff”)
- Failure to clearly state “not cleared for takeoff”
- Assumptions instead of confirmations
Analysis: The crew believed they were cleared, while ATC assumed the aircraft was holding. This disaster highlighted the danger of conversational English and the necessity of explicit readbacks and hearback verification.
Lesson: Ambiguity in normal operations becomes fatal in high workload conditions or bad weather conditions.
Correct Structure of an Emergency Call –
2. The Standard Emergency Format: “MIPDOR”
To ensure you don’t forget critical data while adrenaline is pumping, pilots use the MIPDOR acronym (or similar variations) to structure the call:
- M — Mayday / Pan-Pan: (Repeat 3 times to ensure it is heard).
- I — Identification: Your aircraft callsign.
- P — Position: Where you are (e.g., “5 miles North of Kraków”).
- D — Distress Nature: What is the emergency? (e.g., “Engine fire”).
- O — Operational Intentions: What are you going to do? (e.g., “Emergency descent”).
- R — Requests: What do you need? (e.g., “Requesting immediate landing Runway 25” or additional info: Souls on board (SOB) and fuel remaining.).
Example call: “Mayday, Mayday, Mayday. SP-ABC, 5 miles North of Berlin. Engine fire, performing emergency descent. Requesting immediate landing Runway 25. Two souls on board.”
Common Communication Errors in Emergencies
In high-pressure situations, the risk of miscommunication increases significantly. The table below outlines common errors and their operational consequences.
| Error | Risk |
| Not declaring Mayday | Delayed priority |
| Talking too much | Frequency congestion |
| Vague descriptions | Misallocation of resources |
| Not stating intentions | ATC uncertainty |
| Emotional tone escalation | Cognitive overload |
CRM and Human Factors
Under stress, the human brain and speech undergo specific changes that can degrade safety:
- Speech rate increases
- Accent interference worsens
- Working memory narrows
- Information sequencing breaks down
Training in standard phraseology reduces these effects.
Appropriate Response from ATC
In emergencies, controllers must act as a stabilizing force. To support the crew, controllers should:
- Maintain calm tone
- Provide clear options
- Avoid excessive instructions
- Confirm critical data
Example:
“ABC123, roger Mayday, runway two seven available, wind calm, cleared to land.”
Final Principle
In emergencies, communication must be shorter, clearer, and stronger than confusion. Standardized emergency phraseology exists because aviation cannot rely on improvisation when time is limited.
Practice Section (Levels 4–6)
ICAO Language Proficiency Perspective
- Level 4: Can handle routine emergencies but may hesitate under pressure. Displays basic vocabulary and some imprecision.
- Level 6: Maintains clarity under stress, uses standard phraseology consistently, and structures information logically.
A. Picture Description Task (ATC Context)
Candidate Prompt: You see an aircraft stopped on the runway with emergency vehicles nearby. Describe what you see and explain:
- What may have happened
- What risks are present
- What ATC actions are required
Examiner Probing Questions:
- What information would ATC need immediately?
- What phraseology would be used?
- How would traffic be managed?
- What could be the contributing factors?
Level 4 Sample Response
“The aircraft is on the runway and something happened. There are fire trucks. Maybe it was a problem with landing. ATC must stop traffic.”
Analysis: Adequate but limited speculation control, basic vocabulary, and some imprecision.
Level 6 Sample Response
“The aircraft appears disabled on the runway, possibly due to a landing gear malfunction. Emergency services are positioned around the fuselage. ATC would need to close the runway immediately, reroute inbound traffic, and coordinate with rescue services while maintaining frequency control.”
Analysis: Clear structure. Controlled speculation. Operational awareness.
B. Emergency Role-Play (Pilot–ATC)
Situation: Engine vibration after takeoff.
- ATC Script (Examiner): “ABC123, radar contact. Confirm nature of problem.”
- Expected Strong Response (Level 6): “ABC123, experiencing engine vibration, request immediate vectors for return, maintaining four thousand feet.”
C. Confirm/Verify Trap Section (Exam Use)
Examiner says: “Confirm passing flight level one zero zero.”
- Weak response: “Yes.”
- Strong response: “Passing flight level one zero zero.”
ATC-FOCUSED SCENARIOS
Designed for ATC candidates and controllers.
Scenario 1 — Runway Incursion Risk
Situation: Aircraft vacates slowly. Another aircraft is on short final.
ATC Tasks: Issue go-around, confirm runway vacated, and maintain calm tone.
Model ATC Language:
- “ABC123, go around, I say again go around.”
- “Traffic vacating runway.”
- “Confirm runway vacated.”
Scenario 2 — Frequency Congestion During Emergency
Situation: Aircraft declares MAYDAY.
ATC Priorities:
- Clear frequency
- Confirm position
- Offer runway
- Coordinate emergency services
Model ATC Response:
- “All stations, stop transmitting. MAYDAY traffic only.”
- “ABC123, runway two seven available, wind calm, cleared to land.”
Scenario 3 — Loss of Separation
ATC must: Issue immediate instruction, avoid long explanations, and use a standard urgency tone.
Example:
- “ABC123, turn left immediately heading one eight zero.”
- Not: “I need you to turn left quickly because…”
CRM RESOURCES (Airline Focus)
Communication Under Stress Module
Key Training Objective:
Maintain clarity under high workload. Stress narrows the focus; training expands the use of standardized language to reduce cognitive load.
A. Authority Gradient Scenario
Managing communication between the Captain and First Officer.
FO notices altitude deviation.
- Weak CRM: “Is that altitude okay?” (Too ambiguous).
- Strong CRM: “Captain, we are descending below cleared altitude.” Principle: Use direct, factual, and non-accusatory language.
B. Fuel Communication Scenario
Based on historical miscommunication lessons, the crew must decide when to use specific levels of urgency and say:
- “Minimum fuel”: No delay can be accepted.
- “Fuel emergency”: Priority required.
- “Mayday, Mayday, Mayday”: Immediate landing required.
CRM Discussion Points:
- Overcoming cultural hesitation to declare an emergency.
- The danger of over-politeness in the cockpit.
- The risk of under-declaring the severity of a situation.
Final Summary of Emergency Procedures
- Aviate, Navigate, Communicate: Fly the plane first.
- Use the “Magic Words”: If you need help, say MAYDAY or PAN-PAN.
- Be Concise: Use standard phraseology to save time.
- Declare Early: It is better to cancel an emergency later than to declare it too late.
Text powered by AI.
