ICAO Request Phrases – Radiotelephony Clearances, Tactical Deviations & Priority Handling

ICAO Request Phrases

The ability to initiate clear, precise operational requests is a vital communication skill evaluated under the ICAO Language Proficiency Assessment (Doc 9835, Annex 10, and Doc 4444). Aviation examiners assess whether flight crews can state tactical requirements unambiguously, specify quantifiable parameters (such as headings, altitudes, or time constraints), provide logical operational justifications, and negotiate alternative solutions when air traffic or airspace restrictions prevent immediate compliance.

To achieve ICAO Level 4 (Operational), Level 5 (Extended), or Level 6 (Expert), candidates must move beyond hesitant or informal phrases like "can we go higher?" or "we want to turn left." This guide organizes essential request language across five key operational domains: Level Changes & Direct Routings, Weather Deviations & Turbulence Management, Speed Adjustments & Approach Configurations, Priority Ground Services & Medical Support, and Practical Role-Play Drills.

ICAO Request Lexicon Overview

  • differentiate standardized radiotelephony request callouts: REQUEST CLIMB/DESCENT, REQUEST DIRECT TO, and REQUEST DEVIATION
  • structure tactical requests with precise operational parameters: specific headings, nautical mile offsets, and flight levels
  • provide concise operational justifications: turbulence, convective activity, aircraft gross weight, or medical emergencies
  • apply standard request phraseology for approach alternatives: visual approaches, straight-in approaches, and circuit extensions
  • request ground-based aerodrome emergency support: medical triage, aircraft towing, and fire rescue intervention
  • practice model spoken exchanges for ICAO Speaking Part 3 problem-solving role-plays and interactive examinations

Step 1: En-Route Level Changes & Navigational Clearances

Flight crews initiate vertical and lateral navigation requests to optimize flight path efficiency, manage fuel burn, and avoid rough air. Use standard ICAO formats:

Operational Request Standard ICAO Phraseology Format Model Example Transmission
Climb / Descent Request REQUEST CLIMB / DESCENT TO [LEVEL] (DUE TO [REASON]) "Bordeaux Control, Lufthansa 412, REQUEST CLIMB TO FLIGHT LEVEL THREE SIX ZERO due to wind optimization."
Direct Routing Request REQUEST DIRECT TO [WAYPOINT] "Zurich Radar, Swiss 884, REQUEST DIRECT TO WAYPOINT ELMEM."
Block Altitude Request REQUEST BLOCK [LEVEL] TO [LEVEL] "Shanwick Radio, Speedbird 114, REQUEST BLOCK FLIGHT LEVEL THREE THREE ZERO TO THREE FIVE ZERO due to moderate turbulence."
Speed Change Request REQUEST [MACH / SPEED IN KNOTS] "Maastricht Radar, Air France 206, REQUEST MACH DECIMAL EIGHT TWO for schedule recovery."
Heading Offset Request REQUEST [NUMBER] DEGREES [LEFT/RIGHT] HEADING "Control, Scandinavian 901, REQUEST TEN DEGREES LEFT HEADING due to navigation system cross-check."

Step 2: Weather Deviations & Severe Atmospheric Hazards

When encountering thunderstorms, severe icing, or mountain waves, requests must convey urgency, direction, and lateral displacement:

Meteorological Hazard Tactical Request Structure Aviation Context
Cumulonimbus (CB) Avoidance "Request heading deviation [number] degrees [left/right] of track for [distance] miles to avoid weather." "Munich Radar, Lufthansa 204, request heading deviation thirty degrees right of track for twenty miles to avoid active cumulonimbus cell."
Severe Turbulence Level Change "Request immediate descent to [level] due to severe clear air turbulence." "Control, Speedbird 672, request immediate descent to flight level two eight zero due to severe clear air turbulence."
Holding for Weather Improvement "Request holding at [waypoint] to monitor aerodrome weather conditions." "Tower, Air France 450, request holding at waypoint TANGO due to low visibility on final approach."
Runway Change Due to Crosswind "Request runway [designator] due to crosswind limits exceeded." "Approach, KLM 812, request runway zero six right due to crosswind limits exceeded on runway zero six left."

Step 3: Approach, Landing & Terminal Area Requests

During the descent and approach phase, pilots make specific requests to establish stabilized approach profiles or adapt to technical constraints:

  • Visual Approach: REQUEST VISUAL APPROACH RUNWAY [DESIGNATOR] → Used when flight crews maintain continuous visual contact with the runway environment and terrain (e.g., "Speedbird 312, runway in sight, request visual approach runway two eight left").
  • Straight-In Approach: REQUEST STRAIGHT-IN [ILS / RNAV] APPROACH → Minimizes vectoring distance and fuel consumption when arriving aligned with the final approach course.
  • Track Miles / Distance to Touchdown: REQUEST TRACK MILES TO RUNWAY → Enables flight crews to calculate descent profiles and target energy states accurately.
  • Circuit Extension / Orbit: REQUEST ONE THREE-SIXTY RIGHT FOR SPACING → Allows aircraft to absorb delay or bleed off excess altitude prior to joining the final approach path.
  • Flapless / High-Speed Approach: REQUEST EXTENDED FINAL APPROACH TRACK DUE TO TECHNICAL PROBLEM → Informs ATC that non-normal configurations require higher approach speeds and larger turn radiuses.

Standard Radiotelephony: Visual Approach Request

"Frankfurt Approach, Lufthansa 114, field in sight, REQUEST VISUAL APPROACH RUNWAY ZERO SEVEN RIGHT, cancel IFR flight plan."

Step 4: Priority Handling, Medical Support & Emergency Ground Services

Emergency conditions require structured requests specifying the precise medical, technical, or security assistance required upon landing:

Emergency Condition Required Assistance Standard Request Phraseology
Medical Incident Paramedic ambulance and doctor at gate. "Request mobile intensive care ambulance with physician to meet the aircraft at gate Bravo four."
Hot Brakes / Gear Malfunction Airport Rescue and Firefighting (ARFF). "Request emergency firefighting vehicles standing by along the runway and follow-me vehicle after rollout."
Hydraulic Depletion / No Steering Aircraft tow truck on active runway. "Request aircraft tug and tow bar to meet us on runway two six; unable to steer off runway under our own power."
Unruly Passenger / Security Threat Airport security police at parking stand. "Request local law enforcement officers at stand Delta two immediately upon block arrival."
Fuel Dumping Block Clearance Dedicated airspace block and altitude reservation. "Request airspace block flight level one zero zero to one two zero over the sea to conduct fuel jettison."

Step 5: Practical Spoken Application & Model Exam Drills

Examine how structured operational requests are delivered during ICAO oral examinations:

Drill 1: Requesting Emergency Diversion with Medical Priority (Part 3 Role-Play)

Examiner (as ATC): "Scandinavian 418, be advised our radar shows heavy traffic congestion in your destination terminal area. Expect holding at fix ALBA."
Candidate (as Pilot): "Bregenz Radar, Scandinavian 418, unable to accept holding. We have declared a PAN-PAN due to a passenger suffering acute cardiac arrest. We request immediate priority radar vectors for a straight-in approach to runway two-eight, expedited descent to four thousand feet, and an ambulance standing by at the gate upon touchdown."

Drill 2: Requesting Heading Deviation Around Storms (Part 3 Interactive Scenario)

Candidate (as Pilot): "Marseille Radar, Speedbird 882, we have a continuous line of towering cumulonimbus clouds directly ahead across our flight path with active lightning. We request heading deviation twenty-five degrees left of track for thirty nautical miles, maintain flight level three fow-er zero."
Examiner (as ATC): "Speedbird 882, deviation twenty-five degrees left of track approved, report clear of weather."

Drill 3: The Importance of Clear Request Justifications (Part 4 Discussion)

"In high-density airspace, air traffic controllers manage multiple conflicting aircraft profiles simultaneously. When a flight crew submits an operational request, providing a clear and concise justification—such as 'due to gross weight limits' or 'due to severe convective activity'—enables the controller to understand the operational necessity immediately and prioritize clearances safely."