The Readback, the Three AIM Items Every Pilot Must Read Back Verbatim, and the Wrong Runway at Lexington Blue Grass That Put Phraseology at the Center of the FAA's Runway Safety Push

On August 27, 2006, a Bombardier Canadair Regional Jet crew at Lexington Blue Grass Airport was cleared for Runway 22, acknowledged the instruction, and lined up on Runway 26. 49 people died that morning. One crew member survived. The NTSB’s investigation into Comair Flight 5191 pointed to crew resource management failures and confusing taxiway geometry - but the FAA’s response circled back to something foundational: what pilots say before they move, and whether both sides of that conversation are actually working.

That conversation is the readback. Done correctly, it is one of the most effective safety tools in aviation. Done carelessly, it creates a false sense of confirmation where none exists.

What Is the Readback-Hearback Loop?

The readback-hearback loop is the formal name for the exchange that occurs when ATC issues a clearance and a pilot confirms it. ATC transmits an instruction, the pilot processes and reads it back, and the controller compares the readback to what was issued. A match closes the loop. A discrepancy triggers a correction before anything moves.

The mechanism works because repeating information forces a second cognitive pass. Hearing a clearance and then encoding it as speech exposes errors that passive listening misses. If your readback comes out wrong, there’s a moment where the mismatch surfaces - either in your own processing or in the controller’s comparison.

The failure mode is called a hearback error: the controller listens to your readback and hears what they expected, rather than what you actually said. The human brain completes patterns under cognitive load. A readback that sounds close enough to the issued clearance can pass unnoticed by an experienced, attentive controller. This is a documented limitation of auditory processing - not negligence - and the FAA’s runway safety program materials address it explicitly.

The readback is not a guarantee. It is, however, one of the best tools available, and on the items that carry the highest consequence, the FAA has made it a requirement.

What Are the Three Items the AIM Requires Pilots to Read Back Verbatim?

AIM Chapter 4, Section 4 identifies three categories that require a verbatim readback:

1. Runway assignments
2. Hold short instructions
3. Clearances into Class Bravo airspace

These are the non-negotiables. Every other readback practice builds on this foundation.

How Do I Read Back a Runway Assignment?

Whenever ATC assigns a runway - for landing, takeoff, or crossing - read back the runway number. Not “roger.” Not “wilco.” The number.

Runway designations that sound similar are more common than expected. Runway 22 and Runway 26 share significant sonic overlap, especially on a congested frequency or with fatigue in the mix. Parallel runways add a left/right suffix that can drop in a hurried transmission. When you say the number back, you confirm you heard it correctly. The controller confirms you’re going to the right piece of pavement.

The Comair accident illustrates something important: the crew records indicate a readback of the Runway 22 clearance occurred. The positioning onto Runway 26 happened during the taxi phase, in darkness, on a layout that didn’t make the error obvious until it was too late. The readback alone couldn’t prevent what followed - which is precisely why the FAA hardened the entire runway safety framework after 2006. Better signage, better lighting, stronger phraseology requirements. The readback for runway assignments is one layer of a defense-in-depth system. It is not optional.

Say the runway number back. Every time. Including at your home airport.

How Do I Read Back a Hold Short Instruction Correctly?

A correct hold short readback includes the runway designation and your aircraft identifier:

“Hold short Runway 28, N734PT.”

FAA Air Traffic Organization Order 7110.65, which governs controller procedures, specifically references readback of hold short instructions as a critical safety behavior. Controllers are trained to listen for it and reissue the instruction if not confirmed correctly. That’s the loop functioning as designed - but the pilot has to hold up their end.

The most common shortcut is responding “holding short” without the runway number. That’s better than silence, but it tells the controller only that you intend to stop - not that you stopped at the right line on the right runway. Two extra words confirm you heard the right instruction.

Runway incursions remain one of the FAA’s top sustained safety priorities. The readback is the simplest tool available to prevent them.

When Do I Need to Read Back a Class Bravo Clearance?

Entry into Class Bravo airspace requires an explicit clearance - not a vague affirmative, not a “standby.” And when that clearance is issued, you read it back.

The legal dimension matters here. Unauthorized entry into Class Bravo is a violation of 14 CFR Part 91. If you enter believing you had a clearance that wasn’t actually issued, the consequences fall on you. Your readback is your on-frequency record that you understood you were cleared and know where you’re authorized to go.

A correct readback sounds like:

“Cleared into the Bravo, maintain 4,500, N734PT.”

This trips up pilots transitioning from smaller, uncontrolled fields. The Bravo shelf may extend lower than expected. The clearance may come quickly in a high-workload environment. Confirm it back every time.

What Else Should I Read Back Every Time?

The AIM’s three required items are the floor. Experienced pilots treat several other clearance types the same way:

Altimeter settings. Particularly critical in IMC or at any surface where vertical separation depends on every aircraft referencing the same pressure. “Two-niner-niner-four, N734PT.”

Transponder codes. A misread squawk causes radar identification problems and can corrupt the traffic picture the controller uses to sequence you. “Squawk 0532, N734PT.”

Altitude assignments in the IFR environment. In actual instrument conditions, vertical separation is the only separation that exists. There is no visual backup. “Descend and maintain four thousand, N734PT.”

Frequency changes. Saying the frequency aloud before reaching for the dial reinforces that you have the right digits. Ending up on the wrong frequency during a critical phase of flight is recoverable - and avoidable.

How Should I Structure a Readback?

The preferred structure: repeat the clearance item, then give your aircraft identifier. If ATC called you by name first, lead with your identifier instead.

• “Cleared to land Runway 28, N734PT.”
• “Hold short Runway 33, N734PT.”
• “Descend and maintain four thousand, N734PT.”

The identifier at the end tells the controller which aircraft confirmed. On a frequency with several aircraft in similar phases of flight, voice recognition alone is not reliable. The identifier closes the loop unambiguously.

“Roger” tells the controller you heard something - not what you understood. “Wilco” means you’ll comply, but with what, exactly? On routine communications, those responses are fine. On the required items, they don’t close the loop.

What Happens If My Readback Is Wrong and the Controller Doesn’t Catch It?

A controller failing to catch an incorrect readback does not transfer legal or safety responsibility. If you taxi across a runway you were supposed to hold short of, the absence of a correction is not a defense. The responsibility to understand your clearance remains yours.

If you’re ever unsure, ask.

“Verify Runway 22?”

“Say again altimeter?”

Both are complete, professional transmissions. Controllers would rather answer a clarifying question in two seconds than work a runway incursion or an airspace deviation.

When Should I Say “Unable”?

“Unable” is a complete, appropriate response to any ATC instruction you cannot safely comply with.

ATC issues instructions based on their radar picture. They don’t know what you see out the window. They don’t know your aircraft’s climb performance or equipment limitations. If an assigned altitude would put you into icing conditions, say “unable, request different altitude.” If a direct routing takes you through weather, say “unable direct, requesting deviation.”

Student pilots are often reluctant to use this word. It can feel confrontational. It isn’t. “Unable” is the bridge between the controller’s picture and your reality. Use it without hesitation.

How Do I Use Aircraft Identifiers Correctly in Readbacks?

Without established radar contact: use your full registration in every transmission. N734PT in full, every time.

After ATC abbreviates your callsign: once radar contact is confirmed and the controller shortens your identifier, use the abbreviated version they established. If they call you “four-papa-tango,” you respond as “four-papa-tango.” You do not abbreviate first - you wait for ATC to set the short form.

On a checkride, use the full identifier until ATC abbreviates it. The examiner is listening for this.

Use standard NATO phonetic alphabet throughout: Alpha, Bravo, Charlie, Delta, Echo, Foxtrot, Golf, Hotel, India, Juliet, Kilo, Lima, Mike, November, Oscar, Papa, Quebec, Romeo, Sierra, Tango, Uniform, Victor, Whiskey, X-Ray, Yankee, Zulu. On a busy frequency with multiple aircraft sharing similar identifiers, non-standard phonetics add unnecessary ambiguity. The standard is the standard for a reason.

Key Takeaways

• The AIM requires verbatim readbacks for three items: runway assignments, hold short instructions, and Class Bravo clearances. These are non-negotiable.
• A correct hold short readback includes the runway number and your aircraft identifier - “holding short” alone is not sufficient.
• If a controller fails to catch your incorrect readback, the legal and safety responsibility remains yours. Never guess and rely on the loop to catch you.
• Build the habit of reading back altimeter settings, transponder codes, altitude assignments, and frequency changes even when not strictly required.
• “Unable” is a professional, complete response to any instruction you cannot safely comply with. Use it without hesitation.