In aviation, communication is a closed-loop system. The Readback/Hearback process is the primary defense against “expectation bias” and linguistic errors. If a pilot hears what they expect to hear rather than what was actually said, the readback is the only moment the controller can catch the mistake.
1. Purpose of Readback
Readback is not a repetition for politeness. It is a primary safety barrier designed to:
- Confirm correct reception of instructions.
- Expose misunderstandings immediately.
- Prevent silent errors.
- Support shared situational awareness.
In aviation, what is not read back is not confirmed.
2. ICAO Closed-Loop Communication Model
Correct readback is part of a four-step loop:
- Instruction issued (ATC).
- Readback (Pilot).
- Hearback (ATC checks accuracy).
- Correction (if required).
Skipping any step weakens the safety net.
In the previous posts you could read a lot of examples of correct read backs. Below you can find key points of hot to structure them.
Mock Transcript
First, let’s have a look at a mock transcript of a Complex Departure Clearance. This scenario simulates a busy environment where the pilot receives a lot of data at once, often called a “CRAFT” clearance.
The Scenario:
- Aircraft: SP-DRE (a twin-engine aircraft).
- Location: Kraków Tower (EPKK).
- Condition: Instrument Flight Rules (IFR) to Warsaw (EPWA).
The Exchange:
- ATC: “SP-DRE, Kraków Delivery, cleared to Warsaw via the EVINA 5Q departure, squawk 4521. After departure, climb via the SID to Flight Level 80. Contact Departure on 121.075.”.
- Pilot (correct readback): “Cleared to Warsaw, EVINA 5Q departure, squawk 4521. Climb via SID to Flight Level 80, and frequency 121.075 on the departure. SP-DRE.”.
- ATC: “SP-DRE, readback correct. Contact Ground on 118.1 for taxi.”.
Breakdown of Required Readback Items
In this single transmission, the pilot had to catch and repeat five critical pieces of information. If any of these were missed, the controller would have to correct them.
| Item | What was said | Why it’s mandatory |
| Clearance Limit | “Cleared to Warsaw” | Confirms the destination is correct in the system. |
| SID (Route) | “EVINA 5Q departure” | Ensures the pilot follows the correct noise/terrain path. |
| Transponder | “Squawk 4521” | Critical for the radar to “see” who you are. |
| Altitude | “Flight Level 80” | Prevents mid-air collisions with arriving traffic. |
| Frequency | “121.075” | Ensures the pilot doesn’t disappear from the radio. |
The Structure of a Correct Readback
Here is an analysis of the procedures and the high-stakes logic behind them.
According to ICAO and operational practice, certain instructions are so critical that they require a verbatim, that is a word-for-word readback.
A proper readback follows a specific hierarchy: the information followed by the caller ID. This ensures that the controller hears the confirmation of the data first, and the caller ID ensures the readback comes from the right aircraft.
Core Elements of a Correct Readback
A correct readback contains three core elements:
1. Use Action Verbs
Inform what the aircraft is doing:
- Climbing
- Descending
- Maintaining
- Turning
- Holding
2. Repeat Instructions
If any values are provided, they mustn’t be omitted:
- Taxiing instructions: specifically “Hold Short” instructions, runway numbers, and crossings.
- Takeoff and landing clearances: always include the runway designator.
- Altitudes and levels: every change in height must be confirmed.
- Headings and speeds: assigned vectors or speed restrictions.
- Transponder codes (Squawk): to ensure radar identification.
- Altimeter settings (QNH/QFE): critical for vertical separation.
- Frequency changes: to ensure you don’t “go lost” on the wrong channel.
3. State Your Callsign
End the transmission with your aircraft identification (e.g., „SP-ABC”) to confirm which aircraft is acting.
Examples of Correct vs. Incorrect
- ATC: “SP-ABC, climb and maintain Flight Level 100.”
- Correct readback: “Climb and maintain Flight Level 100, SP-ABC.”
- Incorrect readback: “Roger, going to 100, SP-ABC” (Avoid using “Roger” as a substitute for repeating data).
✅ Correct example:
- “Climbing to flight level two four zero, ABC123.”
❌ Incorrect examples:
- “Roger.”
- “Okay.”
- “Yes, we’re doing that.”
Note: These do not confirm the instruction and fail to close the communication loop.
3. Readback vs Acknowledgement
Acknowledgement alone is not sufficient. Even “Wilco” does not replace a required readback.
| Phrase | Function | Safety value |
| Roger | Message received | Low |
| Wilco | Will comply | Medium |
| Full readback | Confirms understanding | High |
4. Accuracy Requirements
Numbers
- Must be spoken digit by digit.
- Use standard ICAO pronunciation.
- ❌ “Two forty” instead of ✅ “Two four zero”
Units
- Include flight level or feet.
- Avoid assumptions.
- ❌ “Descending to three thousand” instead of ✅ “Descending to three thousand feet”
5. Partial Readback: a common failure
Example Scenario:
- ATC: “Descend to flight level one eight zero, reduce speed to two one zero knots.”
- ❌ Pilot (partial): “Descending to flight level one eight zero.”
- Result: Speed instruction lost.
- ✅ Correct: “Descending to flight level one eight zero, reducing speed to two one zero knots.”.
6. ATC Hearback Responsibility
The procedure is only 50% complete once the pilot finishes speaking. The Hearback is the controller’s job:
- The controller must listen to the pilot’s readback actively.
- If the readback is correct, the controller remains silent (or continues with the next instruction).
- If incorrect values are detected, the controller must immediately use the word “NEGATIVE” or “CORRECTION” and repeat the entire instruction.
7. Readback in Non-Standard Situations
During:
- weather deviations
- technical problems
- emergencies
readback may be
- shorter
- focused on critical actions
Example: “Turning left ten degrees for weather avoidance.”
Clarity remains more important than brevity.
8. Common Pitfalls and Best Practices
The “Blocked” Transmission: If two pilots speak at the same time, the controller hears a high-pitched squeal. If you hear this, do not assume your readback was heard.
Fix: Wait for the frequency to clear and say, “Confirm you copied readback for SP-ABC?”.
Stringing Instructions: Controllers sometimes give “strings”, e.g., “Turn left heading 240, climb FL80, contact approach on 119.1”.
Fix: If you cannot remember all three, do not guess. Say, “Say again all after heading 240, SP-ABC.”
Common Errors and Associated Risks
| No readback | Unnoticed misunderstanding | |
| Yes/affirm only | Wrong action | |
| Missing callsign | Wrong aircraft acts | |
| Informal language | Ambiguity | |
| Incorrect number | Loss of separation |
Common Errors to Watch Out For
The “Roger” Trap: If the pilot had simply said “Roger, SP-DRE,” the controller would be required to say “SP-DRE, negative, read back clearance”.
Transposing Numbers: A common mistake is saying “Squawk 4251” instead of 4521. This creates a “ghost” aircraft on the controller’s screen.
Missing the Call Sign: Even if the readback is perfect, it is invalid without the call sign at the end. There controller needs to know who just agreed to those instructions.
9. CRM and Safety Culture Link
Correct readback procedures:
- support a challenge-and-response culture
- reduce authority gradient effects
- prevent assumption-based actions
Requesting clarification is expected behaviour, not a weakness.
10. Confirm / Verify / Check = SAY THE VALUE OR ACTION
Quick Training Drill: Confirm / Verify / Check
Instructor says:
“Confirm…”
Student must respond:
verb + value
Example:
“Maintaining…”, “Turning…”, “Passing…”, “Established…”.
When ATC says: “CONFIRM”, “VERIFY”, or “CHECK”, they require an explicit response. Never answer with simple words like “yes/no”, “affirm/negative”, or “roger” .
Drill scenarios
A. “Confirm able direct LIMA.”
- ❌ Wrong response: “Yes.”
- ✅ Correct response: “Able direct LIMA” or “Unable direct LIMA.”
- 🧠 Trap: ATC needs a capability statement, not politeness .
B. “Verify runway vacated.”
- ❌ Wrong response: “Affirm.”
- ✅ Correct response: “Runway vacated” or “Vacating runway.”
- 🧠 Trap: Runway status is safety-critical – ambiguity can cause a runway incursion .
C. “Confirm cleared to land runway two seven.”
- ❌ Wrong response: “Affirm.”
- ✅ Correct response: “Cleared to land runway two seven.”
- 🧠 Trap: ATC is checking that you believe you are cleared — your readback must prove it .
D. “Confirm you are established on the localizer.”
- ❌ Wrong response: “Yes, established.”
- ✅ Correct response: “Established on the localizer” or “Not yet established.”
- 🧠 Trap: ATC needs status, not agreement .
E. “Check altitude.” (open-ended)
- ❌ Wrong response: “Checked.”
- ✅ Correct response: “Altitude four thousand feet” or “Maintaining four thousand feet.”
- 🧠 Trap: Open-ended checks demand explicit data .
🔑 Universal ICAO Rule to Memorize
Final Safety Principle:
Aviation safety depends on saying it out loud — correctly, completely, and immediately .
Let’s Level Up: ICAO Level 6 Perspective
At ICAO Level 6, candidates demonstrate superior communication skills by :
- reading back proactively and precisely
- self-correcting immediately
- clarifying before acting if unsure
Level 6 Example: “Confirm cleared to descend to flight level one eight zero.” This response demonstrates awareness, professionalism, and effective risk management .
Text powered by AI.
