What is readback
The readback is the exact repetition by the pilot of ATC instructions received. It's a two-way verification:
- The controller has confirmation you received correctly.
- The controller can correct you immediately if you misunderstood.
- You have an active reminder of values to set.
Without readback, an ATC clearance isn't considered "closed". If you misread a readback (e.g. repeat "QNH 1008" when the controller said "1018") and the controller doesn't catch the error, legally what you repeated is what counts. That's why it's also called "hearback": the controller must listen to your readback and correct if needed.
What must always be repeated (mandatory)
ICAO Annex 10 lists instructions that mandatorily require readback. They're all direct operational instructions:
- ATC clearance (clearances for IFR and special VFR)
- Taxi instructions (taxi instructions, holding points)
- Runway authorizations (cleared for take-off, cleared to land, line up and wait)
- Altimeter settings (QNH and Standard)
- Altitudes, flight levels, headings, speeds assigned
- Transponder squawk codes
- Frequency changes assigned
- Approach type assigned
- Runway in use
- Restrictions (e.g. "report passing 3000 feet")
If the instruction contains a number or operational value, it must be repeated. If it's just information (weather, traffic, NOTAM), full readback isn't needed — a simple "Roger" or "Copied" suffices.
What does NOT need to be repeated
Some things don't require readback, and repeating them only wastes radio time:
- Weather information ("Wind 220 degrees 5 knots") — just acknowledgement
- Traffic information ("Traffic 12 o'clock 3 miles") — "Traffic in sight" or "Looking out"
- NOTAM or informational messages
- Action confirmation ("Confirm you copied?") — just "Affirm" or "Negative"
HB-PMRTaxi to holding point runway 19 via Alpha, QNH 1018, HB-PMR. ✅
HB-PMRLooking for traffic, HB-PMR. ✅
(NOT: "Traffic 11 o'clock 3 miles Cessna 4000 feet HB-PMR" ❌)
Correct readback structure
Readback has three golden rules:
1. Same order
Repeat elements in the same order the controller said them. Don't reorganize, don't summarize.
2. End with your callsign
The callsign always closes the readback. It tells the controller who confirmed.
3. Literal, not paraphrased
Quantities are said with the same words. If the controller says "climb to flight level one two zero", you repeat "climb to flight level one two zero" — not "FL120" or "climbing twelve thousand".
HB-PMRDescend 4000 feet, QNH 1019, heading 270, speed 130 knots, HB-PMR. ✅
What happens if you mess up the readback
The controller must correct you immediately. Standard phraseology:
"NEGATIVE, [callsign], I say again..." followed by the correct instruction. You then make a new correct readback.
If you notice the error yourself (you realize a second after releasing PTT), correct immediately:
"Correction, HB-PMR, descend 4000 feet QNH 1018."
Abbreviated readback. On busy frequencies some pilots only say "Cleared HB-PMR" or "Roger 1018" instead of full readback. It's non-standard and not legally sufficient. The controller may ask you to redo the full readback.
Readback and controller corrections
When the controller corrects you, your new readback must include the explicit correction:
HB-PMRClimb 5000 feet QNH 1018, HB-PMR. (error: 5000 instead of 4000)
TWRHB-PMR, NEGATIVE, climb 4000 feet, I say again four thousand feet, QNH 1018.
HB-PMRClimb 4000 feet, QNH 1018, HB-PMR. ✅
Readback in different languages
Readback is done in the same language as the instruction. If the controller speaks Italian, you reply in Italian. If they speak English, reply in English. Mixing languages is incorrect and creates ambiguity.
In Switzerland Skyguide adapts to the pilot: if you feel safer in English, start in English. If you start in Italian, continue in Italian. Linguistic consistency is almost as important as phraseology.
Summary — to remember
- Readback = operational confirmation, not politeness.
- Mandatory for clearances, taxi, take-off/landing, QNH, altitudes, headings, speeds, squawk, frequencies.
- Not mandatory for weather, traffic, NOTAM, general info.
- Same order, literal, callsign at the end.
- "Roger" isn't enough for operational instructions.
- Consistent language throughout the conversation.
Sources
- ICAO Annex 10 — Aeronautical Telecommunications, Volume II, Chapter 5
- ICAO Doc 9432 — Manual of Radiotelephony, Chapter 4
- ICAO Doc 4444 — PANS-ATM, Chapter 12 (Phraseologies)
- Aero Locarno · Subject 090 — VFR Communications (EASA syllabus)
The wiki gives you the parts. The course teaches you to assemble them.
VFR Essentials is the video phraseology course for people who really fly — with real Swiss airfield scenarios, real ATC audio, and the perspective of someone on the other side of the microphone.
Discover VFR Essentials