The Runway Assignment Readback, the Hearback Failure That Keeps Showing Up in Runway Incursion Reports, and the Specific Words You Are Required to Say Back Every Single Time

Under AIM section 4-4-7, pilots are required to read back - verbatim and with their call sign - a specific list of ATC instructions that includes runway assignments, hold short clearances, takeoff and landing clearances, altimeter settings, transponder codes, and frequency changes. “Roger” is never a substitute: it confirms only receipt of a transmission, not what was heard. Readback failures are a documented contributing factor in FAA runway incursion incidents, and the safety loop that protects against them only closes when the pilot gives the controller something specific to verify.

What Does the AIM Require You to Read Back?

Aeronautical Information Manual section 4-4-7 defines the required readback list. These items are not optional acknowledgments - each requires the pilot to repeat the specific content back to the controller, verbatim, followed by their call sign.

The required items are:

• Runway assignments
• Hold short instructions
• Runway crossing clearances
• Altimeter settings
• Transponder codes
• Frequency changes
• Departure and destination airports (when copying an IFR clearance)
• Cleared for takeoff
• Cleared to land

Runway operations dominate that list. That is not a coincidence. The FAA has identified readback failures as a contributing factor in a significant number of runway incursion incidents.

Why Is “Roger” Never Enough?

“Roger” has exactly one meaning: I received your transmission. The AIM states this explicitly. It does not mean “I understand.” It does not mean “I will comply.” When a pilot says “roger” to a runway assignment, the controller has no way to know what runway the pilot thinks they heard.

A Cessna 172 holding short at a busy regional airport is cleared to cross runway 27 and hold short of runway 32. The student pilot, overwhelmed by frequency traffic, keys the mic and says “roger.” The controller moves on. Thirty seconds later, the Cessna is sitting on runway 32 when a regional jet on short final has to go around. Nobody got hurt - but this scenario appears in runway incursion reports year after year.

“Wilco” is not a substitute either. It means “I have received your message and I will comply,” which is appropriate for some instructions. But saying “wilco, four-five-six uniform” to a runway crossing clearance still tells the controller nothing about which runway you heard.

The controller needs to hear the instruction itself - not your interpretation of it, not your intention to comply with it.

What Does a Correct Readback Sound Like?

Format matters. When the controller issues a takeoff clearance:

Controller: “Cessna four-five-six uniform, runway two-seven, cleared for takeoff.”

Correct readback: “Runway two-seven, cleared for takeoff, Cessna four-five-six uniform.”

The runway number goes first - before the clearance, before the call sign. That structure lets the controller immediately verify the most critical piece of information before confirming the transmission belongs to the right aircraft.

A common shortcut: “Cleared for takeoff, four-five-six uniform.” That drops the runway number - the one piece of information the hearback loop exists to verify. If the controller issued runway 27 and you heard runway 25, your “cleared for takeoff” readback tells them nothing about whether a mix-up occurred. Build the habit now: runway number first, every single time.

What Is the Hearback, and Why Does It Matter?

Most pilots understand the readback as their responsibility. The hearback is the controller’s half of the loop - listening to what the pilot reads back and correcting it if it does not match the original instruction.

Here is how the complete loop works:

1. Controller issues an instruction
2. Pilot reads it back verbatim with call sign
3. Controller listens
4. If the readback is correct, the controller acknowledges
5. If the readback is wrong, the controller corrects it before the pilot moves

When a pilot says “roger,” steps 3 through 5 cannot occur. The hearback requires the pilot to provide specific content - a runway number, an altimeter setting, a frequency. A one-word acknowledgment breaks the loop entirely, and there is no mechanism left to catch a misheard instruction before the pilot acts on it.

Why Are Hold Short Instructions the Most Critical Readback?

Hold short instructions have the shortest accident chain in general aviation. If you misunderstand one and act on it, you may enter an active runway. There is almost no margin.

Controller: “Cessna four-five-six uniform, hold short of runway one-niner.” Correct readback: “Hold short runway one-niner, Cessna four-five-six uniform.”

Saying “roger, six uniform” tells the controller nothing about which runway you heard. If you misheard runway 9 as runway 19, nothing in that communication loop will catch the error - because you never gave the controller anything to verify.

Hold short instructions may be the single most important readback in general aviation. The consequence of getting them wrong is immediate.

How Do Busy Frequencies and Blocked Transmissions Affect Readbacks?

Busy frequencies create a specific cognitive trap. With a lot of traffic, when the controller calls your aircraft, the temptation is to give the shortest possible response and get off the frequency. “Roger” comes out fast. That is exactly the wrong instinct.

The busier the frequency, the more important the full readback becomes. More aircraft moving means more opportunity for blocked transmissions, more chance of a misheard instruction, and less margin for any miscommunication.

A blocked transmission occurs when two aircraft key up simultaneously. The signals interfere, and sometimes the frequency sounds completely normal while neither message made it through. A pilot who “read back” a takeoff clearance during a blocked transmission may believe they are cleared when the controller is not certain what happened.

The correct response to any unclear transmission:

• If you heard your call sign but could not make out the rest, say “say again”
• If you are not certain a transmission was for your aircraft, say “say again”
• If there is any ambiguity, ask before proceeding

The AIM requires you to confirm before acting on any clearance you are uncertain about. This matters especially at airports where multiple aircraft from the same flight school have similar-sounding call signs.

Do Readbacks Protect Against Controller Error?

They do. Controllers are human. They work busy frequencies with multiple aircraft updating constantly, and occasionally an instruction goes to the wrong aircraft.

When you read back a clearance with your call sign, the controller can catch that error before you act on it. Without the readback, you may be operating on an instruction that was never meant for your aircraft - and there is no mechanism in the loop to catch it.

How Do You Read Back Altimeter Settings, Transponder Codes, and Frequency Changes?

These are frequently shortchanged in training. Each has a specific failure mode if the readback is dropped.

Altimeter settings: Read back the specific value. “Two-niner-niner-two, Cessna four-five-six uniform.” A misheard altimeter setting introduces an altitude error that compounds as you climb. The readback catches it before you leave the ground.

Transponder codes: Read back the specific code, then verify your transponder is actually showing that code before confirming. “Squawking four-three-two-one, Cessna four-five-six uniform.” Say it back, then check it.

Frequency changes: Read back the specific frequency. “One-two-four-point-five, four-five-six uniform.” If you misheard the frequency and switch to the wrong one, you will transmit into silence. The controller will not know you are gone until they try to reach you and hear nothing. The readback is the only chance to catch a misheard frequency before you disappear.

What Do the Airman Certification Standards Require?

The ACS for the private pilot certificate addresses communications explicitly. The examiner observes whether you use proper phraseology, conduct communication procedures correctly, and comply with ATC instructions. Proper phraseology includes readbacks - as a task element in the standard, not a suggestion.

On checkride day, the examiner is specifically watching for readbacks on runway assignments, hold short instructions, cleared for takeoff, and cleared to land. These are the items students most often shortchange under pressure, which is exactly why they appear in the standard.

Acknowledging a runway assignment with “roger” is noted. Doing it again on a hold short instruction is a potential unsatisfactory on the communication task.

Key Takeaways

• “Roger” and “wilco” are never substitutes for a required readback - they tell the controller nothing about what you heard
• The runway number goes first in every takeoff, landing, and crossing readback; it is the piece of information the hearback is specifically designed to verify
• Hold short readbacks are the most critical clearance in general aviation - the accident chain from a misunderstood hold short is immediate
• Busy frequencies demand more precision, not less - more traffic means more blocked transmissions and greater consequence from any miscommunication
• The readback closes both sides of the safety loop - without specific content, the controller cannot complete the hearback, and a one-word acknowledgment is no safety check at all