ICAO Non-Standard Communication

While standard radiotelephony phraseology covers approximately 80% of routine flight operations, non-routine, abnormal, and emergency events inevitably require pilots and air traffic controllers to transition into plain English. Under ICAO Annex 1 and Doc 9835, language proficiency assessments specifically evaluate whether a candidate can deliver clear, concise, and unambiguous plain language when standard phraseology does not exist or proves insufficient to describe a developing crisis.

This page explores the interface between standard phraseology and plain English, breaks down the rules for non-standard communication, analyzes common causes of miscommunication, and provides practical operational scripts across complex flight deck scenarios.

Step 1: Phraseology vs. Plain English – The Operational Boundary

ICAO Doc 9835 establishes clear regulatory guidelines governing when standardized phraseology must give way to descriptive plain English:

• Standard Phraseology: Mandatory for all routine operations (e.g., pushback, taxi, takeoff, level changes, approach clearances). Its formulaic nature minimizes transmission time and eliminates linguistic ambiguity across international airspace.
• Plain English: Mandatory whenever an unusual, abnormal, or emergency scenario occurs for which no standardized phraseology exists, or when standard terms fail to fully convey the nuance, urgency, or technical status of an aircraft.
• The Hybrid Approach: Professional radiotelephony blends standard callouts (e.g., "MAYDAY", "PAN-PAN", "REQUEST IMMEDIATE DESCENT") with targeted plain English descriptors (e.g., "dense acrid smoke emanating from the forward avionics bay").
• Aviation Phraseology vs Plain English
• ATC Communication English
• ICAO Language Proficiency Requirements
• ICAO Interaction

Step 2: The 4 Core Principles of Aeronautical Plain English

When stepping outside standardized phraseology, flight crews must adhere to four strict linguistic principles to protect situational awareness:

1. Clarity Over Complexity

• avoid convoluted idioms, literary metaphors, and overly casual conversational structures
• use simple subject-verb-object constructions that are easily processed by non-native speakers under high cockpit workload
• ICAO Grammar Structures
• ICAO Fluency

2. Conciseness & Information Density

• state the critical problem, operational impact, and immediate request in the first sentence
• eliminate conversational fluff (e.g., replace "Well, we were just wondering if maybe we could..." with "Request heading 240 to avoid weather")
• ICAO Speaking Sample Answers
• Level 4 Speaking Examples

3. Lexical Precision

• use accurate aeronautical and mechanical terminology rather than vague words like "broken" or "bad"
• differentiate precisely between states (e.g., "asymmetric flap extension", "uncontained engine failure", "depressurization")
• ICAO Aviation Vocabulary
• ICAO Technical Problem Vocabulary

4. Active Closed-Loop Confirmation

• never assume an ambiguous transmission has been understood; always verify using explicit readback and clarification formulas
• explicitly confirm non-routine parameters: fuel endurance remaining, souls on board, and emergency vehicle staging
• ICAO Clarification Phrases
• ICAO Negotiation Phrases

Step 3: Common Non-Standard Communication Traps

Language examiners listen carefully for dangerous communicative slips that degrade operational safety:

• Colloquialisms & Cultural Slang: Using regional expressions (e.g., saying "we're in the soup" for IMC, or "we're burning daylight" for time-critical fuel) creates severe confusion for non-native controllers.
• Ambiguous Conditional Phrasing: Saying "We could land on runway 27 if needed" instead of the definitive command "We require runway 27 for landing due to crosswind limitations."
• Negative Prefix Confusion: Misusing prefixes over noisy frequencies (e.g., saying "unable" is standard, whereas saying "we cannot not comply" causes fatal misunderstandings).
• Unclear Numbers & Homophones: Confusing "to / two / too" or "for / four" when negotiating tactical altitudes or headings.
• ATC Communication Discussion
• ICAO Communication Scenarios
• Accent Listening Practice

Step 4: Operational Scenarios & Model Plain English Scripts

Review how professional pilots blend standard phraseology with descriptive plain English across diverse operational contingencies:

Scenario 1: In-Flight Medical Emergency & Urgent Diversion

Context: A passenger has collapsed with symptoms of an acute myocardial infarction. The crew must divert immediately.

• Pilot: "Frankfurt Radar, Lufthansa 442, PAN-PAN, PAN-PAN, PAN-PAN. We have a suspected cardiac arrest in the passenger cabin. We request an immediate diversion to Nuremberg, vectors for the active runway, and paramedic emergency services to meet the aircraft upon arrival at the stand."
• ATC: "Lufthansa 442, roger PAN-PAN, turn left heading 140, descend to flight level 090, cleared direct to Nuremberg. Medical services are being notified."
• ICAO Passenger Scenarios
• ICAO Passenger Vocabulary

Scenario 2: Abnormal Gear Indication & Low Flypast Request

Context: The nose landing gear unsafe light remains illuminated after gravity extension. The crew requests visual inspection by the tower.

• Pilot: "Tower, Air France 819, we have an unsafe nose gear indication following alternate manual extension. We request a low visual flypast along runway 26 at 500 feet to allow the tower to visually inspect the landing gear position before we commit to landing."
• ATC: "Air France 819, cleared low approach runway 26, maintain not below 500 feet, surface wind 240 degrees 12 knots. Tower will report landing gear status."
• Technical Failure Scenarios
• Airport Picture Description

Scenario 3: Volcanic Ash Encounter at Night

Context: Cruising at FL360, the crew detects a strong sulfur odor, electrostatic St. Elmo's fire on the windshield, and fluctuating engine parameters.

• Pilot: "Control, Speedbird 114, MAYDAY MAYDAY MAYDAY. We have inadvertently entered a volcanic ash cloud. Experiencing sulfur fumes in the cockpit, engine parameter fluctuations, and severe windshield static. Request an immediate 180-degree turn left and descent to flight level 240 to exit the cloud."
• ATC: "Speedbird 114, turn left heading 180 immediately, descend and maintain flight level 240, QNH 1012."
• Weather Safety Discussion
• Emergency Procedures Discussion
• ICAO Emergency Scenarios

Step 5: Exam-Day Strategies for Part 3 Role-Plays

In Part 3 of the ICAO speaking assessment, you will be placed into simulated non-routine scenarios. Apply these techniques to secure a high Interaction and Vocabulary score:

• Declare the Status Early: Clearly state whether the situation is a routine request, an operational urgency (PAN-PAN), or a life-threatening emergency (MAYDAY).
• Use the "Problem → Consequence → Request" Formula: State what is broken, explain how it affects flight performance (e.g., speed, fuel, flaps), and state exactly what clearance or ground assistance you require.
• Paraphrase Without Hesitation: If you forget a specific mechanical term, describe its function, shape, or symptom immediately in descriptive plain English.
• Maintain Professional Tone & Tempo: Avoid rushing. Speak with clear articulation, deliberate pauses, and measured pacing to project command authority.
• ICAO Speaking Part 3 Problem Solving
• ICAO Problem Solving
• ICAO Speaking Practice
• ICAO Mock Speaking Test