<\/p>\n\n\n\n
In aviation, communication is a closed-loop system<\/strong><\/sup>. The Readback\/Hearback process<\/strong> is the primary defense against “expectation bias” and linguistic errors<\/sup>. 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<\/sup>.<\/p>\n\n\n\n Readback is not a repetition for politeness. It is a primary safety barrier<\/strong> designed to:<\/p>\n\n\n\n In aviation, what is not read back is not confirmed<\/strong><\/sup>.<\/p>\n\n\n\n Correct readback is part of a four-step loop<\/strong>:<\/p>\n\n\n\n Skipping any step weakens the safety net.<\/strong><\/p>\n\n\n\n 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.<\/p>\n\n\n\n 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<\/strong>.<\/p>\n\n\n\n The Scenario:<\/strong><\/p>\n\n\n\n The Exchange:<\/strong><\/p>\n\n\n\n Breakdown of Required Readback Items <\/sup><\/p>\n\n\n\n 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.<\/p>\n\n\n\n <\/p>\n\n\n\n Here is an analysis of the procedures and the high-stakes logic behind them. <\/p>\n\n\n\n According to ICAO and operational practice, certain instructions are so critical that they require a verbatim, that is a word-for-word readback.<\/p>\n\n\n\n A proper readback follows a specific hierarchy: the information followed by the caller ID<\/sup>. This ensures that the controller hears the confirmation of the data first, and the caller ID ensures the readback comes from the right aircraft<\/sup>.<\/p>\n\n\n\n A correct readback contains three core elements<\/sup>:<\/p>\n\n\n\n Inform what the aircraft is doing<\/sup>:<\/p>\n\n\n\n If any values are provided, they mustn\u2019t be omitted<\/sup>:<\/p>\n\n\n\n End the transmission with your aircraft identification (e.g., \u201eSP-ABC”) to confirm which aircraft is acting<\/sup>.<\/p>\n\n\n\n <\/p>\n\n\n\n \u2705 Correct example:<\/strong><\/p>\n\n\n\n \u274c Incorrect examples:<\/strong><\/p>\n\n\n\n Note:<\/strong> These do not confirm the instruction and fail to close the communication loop<\/sup>.<\/p>\n\n\n\n <\/p>\n\n\n\n Acknowledgement alone is not sufficient<\/sup>. Even “Wilco” does not replace a required readback<\/sup>.<\/p>\n\n\n\n Numbers <\/sup><\/p>\n\n\n\n Units <\/sup><\/p>\n\n\n\n Example Scenario:<\/strong><\/p>\n\n\n\n <\/p>\n\n\n\n The procedure is only 50% complete once the pilot finishes speaking<\/sup>. The Hearback<\/strong> is the controller’s job<\/sup>:<\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n During: <\/p>\n\n\n\n readback may be<\/p>\n\n\n\n Example: “Turning left ten degrees for weather avoidance.”<\/em><\/p>\n\n\n\n Clarity<\/strong> remains more important than brevity<\/strong>.<\/p>\n\n\n\n <\/p>\n\n\n\n The “Blocked” Transmission:<\/strong> 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. <\/p>\n\n\n\n Fix:<\/strong> Wait for the frequency to clear and say, “Confirm you copied readback for SP-ABC?”<\/em>.<\/p>\n\n\n\n Stringing Instructions:<\/strong> Controllers sometimes give “strings”, e.g., “Turn left heading 240, climb FL80, contact approach on 119.1”.<\/p>\n\n\n\n Fix:<\/strong> If you cannot remember all three, do not guess. Say, “Say again all after heading 240, SP-ABC.”<\/em><\/p>\n\n\n\n <\/p>\n\n\n\n Common Errors and Associated Risks<\/strong><\/p>\n\n\n\n Common Errors to Watch Out For<\/strong><\/p>\n\n\n\n The “Roger” Trap:<\/strong> If the pilot had simply said “Roger, SP-DRE,” <\/em>the controller would be required to say “SP-DRE, negative, read back clearance”.<\/em><\/p>\n\n\n\n Transposing Numbers:<\/strong> A common mistake is saying “Squawk 4251”<\/em> instead of 4521. This creates a “ghost” aircraft on the controller’s screen.<\/p>\n\n\n\n Missing the Call Sign:<\/strong> Even if the readback is perfect, it is invalid without the call sign at the end. There controller needs to know who<\/em> just agreed to those instructions.<\/p>\n\n\n\n <\/p>\n\n\n\n Correct readback procedures:<\/p>\n\n\n\n Requesting clarification is expected behaviour, not a weakness<\/strong>.<\/p>\n\n\n\n1. Purpose of Readback<\/h2>\n\n\n\n
\n
2. ICAO Closed-Loop Communication Model<\/h2>\n\n\n\n
\n
\n\n\n\nMock Transcript<\/h2>\n\n\n\n
\n
\n
Item<\/strong><\/td> What was said<\/strong><\/td> Why it’s mandatory<\/strong><\/td><\/tr><\/thead> Clearance Limit<\/strong><\/td> “Cleared to Warsaw”<\/td> Confirms the destination is correct in the system.<\/td><\/tr> SID (Route)<\/strong><\/td> “EVINA 5Q departure”<\/td> Ensures the pilot follows the correct noise\/terrain path.<\/td><\/tr> Transponder<\/strong><\/td> “Squawk 4521”<\/td> Critical for the radar to “see” who you are.<\/td><\/tr> Altitude<\/strong><\/td> “Flight Level 80”<\/td> Prevents mid-air collisions with arriving traffic.<\/td><\/tr> Frequency<\/strong><\/td> “121.075”<\/td> Ensures the pilot doesn’t disappear from the radio.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
\n\n\n\nThe Structure of a Correct Readback<\/h2>\n\n\n\n
Core Elements of a Correct Readback<\/h3>\n\n\n\n
1. Use Action Verbs<\/h4>\n\n\n\n
\n
2. Repeat Instructions<\/h4>\n\n\n\n
\n
3. State Your Callsign<\/h4>\n\n\n\n
\n\n\n\nExamples of Correct vs. Incorrect<\/h2>\n\n\n\n
\n
<\/h3>\n\n\n\n
\n
\n
3. Readback vs Acknowledgement<\/h2>\n\n\n\n
Phrase<\/strong><\/td> Function<\/strong><\/td> Safety value<\/strong><\/td><\/tr><\/thead> Roger<\/strong><\/td> Message received<\/td> Low<\/td><\/tr> Wilco<\/strong><\/td> Will comply<\/td> Medium<\/td><\/tr> Full readback<\/strong><\/td> Confirms understanding<\/td> High<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n 4. Accuracy Requirements<\/h2>\n\n\n\n
\n
\n
5. Partial Readback: a common failure<\/h2>\n\n\n\n
\n
6. ATC Hearback Responsibility<\/h2>\n\n\n\n
\n
7. Readback in Non-Standard Situations<\/h2>\n\n\n\n
\n
\n
\n
\n
\n
8. Common Pitfalls and Best Practices<\/h2>\n\n\n\n
No readback<\/td> Unnoticed misunderstanding<\/td> <\/td><\/tr> Yes\/affirm only<\/td> Wrong action<\/td> <\/td><\/tr> Missing callsign<\/td> Wrong aircraft acts <\/td> <\/td><\/tr> Informal language<\/td> Ambiguity<\/td> <\/td><\/tr> Incorrect number<\/td> Loss of separation<\/td> <\/td><\/tr><\/tbody><\/table>\n<\/div>\n<\/div>\n\n\n\n 9. CRM and Safety Culture Link<\/h2>\n\n\n\n
\n