RTR(A) phraseology

Learn the radio before you spend a practice attempt

This free library shows the standard shape of each call, then a complete two-voice example. Read a phase before you practise it. Learn what must be read back, what to write down, and when to ask ATC to say it again.

The templates use braces for information that changes with your flight. Do not transmit a bracket. Replace every slot with your own callsign, runway, route, level or frequency.

These examples are teaching models, not permission to replace local procedures. In India, follow the current AIP, DGCA guidance and the instruction you actually receive. When a call is unclear, request repetition rather than inventing one.

Core RT rules

Numbers and callsign conventions

For every transmission containing callsigns, levels, headings, runways, frequencies or altimeter settings.

Pilot

{RECIPIENT}, {CALLSIGN}, {MESSAGE_WITH_NUMBERS}.

ATC

{CALLSIGN}, {MESSAGE_WITH_NUMBERS}.

Pilot

Delhi Ground, Skyline 345, request taxi, information Charlie, QNH one zero zero nine.

ATC

Skyline 345, taxi via Alpha to holding point runway two niner left, QNH one zero zero nine.

Pilot

Taxi via Alpha to holding point runway two niner left, QNH one zero zero nine, Skyline 345.

Transmit most numbers digit by digit: runway two seven, heading zero eight zero, squawk four two one three.
Say DECIMAL in a frequency, for example one two one decimal seven five zero.
Keep your aircraft callsign at the end of a readback and at a point where identification matters.
Use your assigned radiotelephony callsign every time. A registration may be used only where that is the assigned callsign.

Reference: ICAO Doc 9432, Chapter 2

What you must read back

After every safety-related clearance or instruction.

Pilot

{CALLSIGN} readback of {ROUTE_OR_INSTRUCTION}, followed by your callsign.

ATC

{CALLSIGN}, {CORRECTION_OR_READBACK_CHECK}.

ATC

Skyline 345, climb flight level two zero zero.

Pilot

Climb flight level two zero zero, Skyline 345.

ATC

Skyline 345, correction, climb flight level two five zero.

Pilot

Climb flight level two five zero, Skyline 345.

Always read back route clearances, runway entry, landing, take-off, backtrack, cross and hold-short instructions.
Also read back runway in use, altimeter settings, transponder codes, level, heading, speed and transition-level instructions.
Acknowledge other instructions so the controller knows you understood and will comply.
If any part is unclear, say SAY AGAIN or CONFIRM. Never guess a number.

Reference: ICAO Doc 9432, 2.8.3

Clearance

Reading back a route clearance

When ATC issues an IFR route clearance before or during taxi.

Pilot

{CALLSIGN}, request clearance to {DESTINATION}.

ATC

{CALLSIGN}, cleared to {DESTINATION} via {ROUTE}, initial climb {LEVEL}, squawk {CODE}.

Pilot

Kolkata Ground, Skyline 345, information Alpha, request clearance to Delhi.

ATC

Skyline 345, cleared to Delhi via filed route, initial climb four thousand feet, squawk two one zero seven.

Pilot

Cleared to Delhi via filed route, initial climb four thousand feet, squawk two one zero seven, Skyline 345.

ATC

Skyline 345, readback correct.

Write the clearance while it is passed slowly, then read back destination, route, initial level and transponder code.
A route clearance is not permission to start, push, taxi, enter a runway or take off.
Wait for the controller to confirm the readback before treating the clearance as accepted.

Reference: ICAO Doc 9432, 2.8.3

Requesting start-up

Before starting engines after receiving departure information.

Pilot

{UNIT}, {CALLSIGN}, {STAND}, request start up, information {ATIS}.

ATC

{CALLSIGN}, start up approved, QNH {QNH}.

Pilot

Bengaluru Ground, Skyline 345, stand three four, request start up, information Bravo.

ATC

Skyline 345, start up approved, QNH one zero one zero.

Pilot

Start up approved, QNH one zero one zero, Skyline 345.

State your location or stand and acknowledge the current ATIS information letter.
ATC may approve immediately or give a start-up time. Write down the exact time if one is given.
A start-up approval does not authorize push-back, taxi or runway movement unless those are separately given.

Reference: ICAO Doc 9432, 4.2

Taxi and surface

Holding short and crossing a runway

At every active runway holding point and whenever instructed to hold short or cross.

Pilot

{CALLSIGN}, holding short runway {RUNWAY}. Request cross runway {RUNWAY}.

ATC

{CALLSIGN}, cross runway {RUNWAY}, report vacated.

Pilot

Chennai Tower, Skyline 345, holding short runway three zero, request cross.

ATC

Skyline 345, cross runway three zero, report vacated.

Pilot

Cross runway three zero, will report vacated, Skyline 345.

Pilot

Skyline 345, runway vacated.

ROGER and WILCO are not sufficient acknowledgements for HOLD, HOLD POSITION or HOLD SHORT.
Say HOLDING SHORT RUNWAY followed by the runway number so the controller hears the exact limit.
Cross only after hearing your callsign with CROSS RUNWAY. Report vacated when the entire aircraft is beyond the holding position.

Reference: ICAO Doc 9432, 4.4

Surface taxi instructions

After start-up or push-back, when moving to the holding point.

Pilot

{UNIT}, {CALLSIGN}, request taxi, information {ATIS}.

ATC

{CALLSIGN}, taxi via {TAXIWAY_ROUTE} to holding point runway {RUNWAY}, QNH {QNH}.

Pilot

Hyderabad Ground, Skyline 345, request taxi, information Delta.

ATC

Skyline 345, taxi via Alpha and Charlie to holding point runway two seven right, QNH one zero zero six.

Pilot

Taxi via Alpha and Charlie to holding point runway two seven right, QNH one zero zero six, Skyline 345.

Every taxi instruction has a limit. Normally this is the holding point for the departure runway.
Do not cross a runway unless the instruction explicitly says CROSS RUNWAY.
Report obstacles or uncertainty early. Taxiing onto the wrong taxiway is easier to correct before the runway.

Reference: ICAO Doc 9432, 4.4

Departure

Initial climb and frequency handover

Immediately after becoming airborne, when ATC passes a climb or transfer instruction.

Pilot

{CALLSIGN}, airborne at {TIME}, maintaining {LEVEL}.

ATC

{CALLSIGN}, contact {NEXT_UNIT} on {FREQUENCY}.

Pilot

Delhi Tower, Skyline 345, airborne at three five.

ATC

Skyline 345, contact Delhi Departure, one two five decimal seven.

Pilot

Contact Delhi Departure, one two five decimal seven, Skyline 345.

ATC

Skyline 345, readback correct.

Pilot

Delhi Departure, Skyline 345, passing two thousand feet, climbing four thousand feet.

Read back the unit name and complete frequency, using DECIMAL, before changing frequency.
Do not switch immediately after your readback. Wait for the controller to confirm it is correct.
On the new frequency, make an initial call with callsign, passing level and cleared level.

Reference: ICAO Doc 9432, 2.8.2

Line up and take-off clearance

When approaching the holding point and entering the departure runway.

Pilot

{UNIT}, {CALLSIGN}, holding short runway {RUNWAY}, ready for departure.

ATC

{CALLSIGN}, runway {RUNWAY}, {LINE_UP_OR_CLEARED_FOR_TAKE_OFF}{CONDITIONAL_INSTRUCTION}.

Pilot

Delhi Tower, Skyline 345, holding short runway two niner left, ready for departure.

ATC

Skyline 345, line up runway two niner left and wait.

Pilot

Line up runway two niner left and wait, Skyline 345.

ATC

Skyline 345, runway two niner left, cleared for take-off.

Pilot

Runway two niner left, cleared for take-off, Skyline 345.

The words TAKE OFF are used only in a take-off clearance or its cancellation.
LINE UP AND WAIT is not a take-off clearance. Stay on the runway and wait.
Read back the runway, conditional instruction and CLEARED FOR TAKE-OFF exactly.

Reference: ICAO Doc 9432, 4.5

En-route

Climbing, descending and maintaining levels

When ATC issues or confirms a climb, descent or cruise level.

Pilot

{CALLSIGN}, leaving {PRESENT_LEVEL}, climbing or descending to {CLEARED_LEVEL}.

ATC

{CALLSIGN}, climb or descend to {CLEARED_LEVEL}.

ATC

Skyline 345, descend to flight level one five zero.

Pilot

Descend to flight level one five zero, Skyline 345.

ATC

Skyline 345, report passing flight level one eight zero.

Pilot

Wilco, Skyline 345.

Pilot

Skyline 345, passing flight level one eight zero, descending flight level one five zero.

Always read back the complete level instruction. If ATC changes any part, expect the whole level clearance to be restated.
Report leaving, passing and reaching levels when asked, or when standard practice requires it.
Distinguish altitude, height and flight level. Flight level is based on the standard pressure setting.

Reference: ICAO Doc 9432, 3.3

Compulsory position report

At compulsory reporting points where radar coverage or procedure does not exempt the flight.

Pilot

{CALLSIGN}, {POSITION} at {TIME}, {LEVEL}, next {NEXT_POSITION} at {NEXT_TIME}, {ENSUING_POINT} next.

ATC

{CALLSIGN}, roger, {REPORT_OR_INFORMATION}.

Pilot

Kolkata Control, Skyline 345, Buban at four seven, flight level two zero zero, next Daman at zero two, Bodeli next.

ATC

Skyline 345, Kolkata Control, roger, report Daman.

Pilot

Report Daman, Skyline 345.

A full report contains aircraft identification, position, time over or at, level, next position and estimated time, and the ensuing significant point.
Include passing and cleared levels if you are changing level and are not yet maintaining the cleared level.
Use UTC for times and speak each digit separately.

Reference: ICAO Doc 9432, 3.4

En-route frequency change

Whenever ATC transfers you from one controlled airspace frequency to another.

Pilot

{CALLSIGN}, monitoring {CURRENT_FREQUENCY}. Contact {NEXT_UNIT} on {FREQUENCY}.

ATC

{CALLSIGN}, contact {NEXT_UNIT} on {FREQUENCY}.

ATC

Skyline 345, contact Chennai Control, one two seven decimal niner.

Pilot

Contact Chennai Control, one two seven decimal niner, Skyline 345.

ATC

Skyline 345, readback correct.

Pilot

Chennai Control, Skyline 345, flight level two four zero.

ATC

Skyline 345, Chennai Control, radar contact.

If told MONITOR a frequency, listen there without making a routine initial call unless required.
If told STAND BY, wait. It is neither an approval nor a refusal.
If no advice to change frequency is received, notify the controlling station before making the change.

Reference: ICAO Doc 9432, 2.8.2

Arrival

Approach vectors and approach clearance

During radar vectoring and receipt of the instrument approach clearance.

Pilot

{UNIT}, {CALLSIGN}, {POSITION_OR_ESTABLISHED_REPORT}, {LEVEL}.

ATC

{CALLSIGN}, turn {DIRECTION} heading {HEADING}, descend {ALTITUDE}, cleared {APPROACH_TYPE} approach runway {RUNWAY}.

Pilot

Mumbai Approach, Skyline 345, passing six thousand feet, descending four thousand feet.

ATC

Skyline 345, turn right heading one two zero, descend three thousand feet, cleared ILS approach runway two seven.

Pilot

Right heading one two zero, descend three thousand feet, cleared ILS approach runway two seven, Skyline 345.

Pilot

Skyline 345, established localiser runway two seven.

ATC

Skyline 345, continue approach.

Read back heading, altitude, approach type and runway before flying the clearance.
An approach clearance authorizes the named approach. It does not itself authorize landing.
Report established on the localiser or final approach course when instructed.

Reference: ICAO Doc 9432, 4.6 to 4.7

Final call, landing clearance and vacating

On long final or final, after landing, and when clearing the runway.

Pilot

{CALLSIGN}, final runway {RUNWAY}.

ATC

{CALLSIGN}, runway {RUNWAY}, cleared to land{WIND}. {INSTRUCTION_AFTER_LANDING}.

Pilot

Goa Tower, Skyline 345, final runway two six.

ATC

Skyline 345, runway two six, cleared to land, wind two seven zero degrees one zero knots.

Pilot

Runway two six, cleared to land, Skyline 345.

ATC

Skyline 345, vacate right, contact Ground one two one decimal seven.

Pilot

Vacate right, contact Ground one two one decimal seven, Skyline 345.

Make a LONG FINAL report about eight nautical miles out on a straight-in approach, otherwise FINAL within about four nautical miles.
Do not land without an explicit CLEARED TO LAND instruction for the runway in use.
The runway is vacated only when the entire aircraft is beyond the relevant holding position. Report RUNWAY VACATED when asked or when local procedure requires it.

Reference: ICAO Doc 9432, 4.7

Emergency

MAYDAY versus PAN PAN

MAYDAY for distress requiring immediate assistance. PAN PAN for urgency concerning safety when immediate assistance is not required.

Pilot

MAYDAY MAYDAY MAYDAY, {UNIT}, {CALLSIGN}, {PROBLEM}, {INTENTIONS}, {POSITION_LEVEL_HEADING}. PAN PAN PAN follows the same order for urgency.

ATC

{CALLSIGN}, MAYDAY received, {ASSISTANCE_AND_INSTRUCTIONS}.

Pilot

MAYDAY MAYDAY MAYDAY, Mumbai Control, Skyline 345, engine failure, diverting to Mumbai, two zero miles north, flight level one eight zero, heading one eight zero.

ATC

Skyline 345, Mumbai Control, MAYDAY received, runway two seven available, descend and maintain one two thousand feet, report heading.

Say the signal three times at the start of the first distress or urgency transmission.
Give the unit addressed if possible, then aircraft identification, nature of the problem, intentions, position, level and heading.
Declare early. You may cancel the state later if the situation improves.
Distress traffic has absolute priority. Urgency traffic has priority over all communications except distress traffic.

Reference: ICAO Doc 9432, 9.2 to 9.3