The Required Readback, the Hold-Short Instruction That Must Come Back Word for Word, and the Runway Incursion Trap Hidden in a Single Syllable
Learn what the FAA mandates for required readbacks, why 'Roger' isn't enough for hold-short instructions, and how proper readbacks prevent runway incursions.
When a controller issues a hold-short instruction, “Roger” is not an acceptable response - and it’s not a matter of etiquette. FAA regulations require pilots to read back runway holding instructions verbatim, including the specific runway number. This requirement exists because the readback is the primary mechanism that catches misheard instructions before they result in a runway incursion.
Why Isn’t “Roger” Good Enough for Hold-Short Instructions?
“Roger” has a precise meaning in radio procedure: received. The word traces to early military phonetics, where “R” stood for “Roger” - the code for “received.” That is all it has ever meant. Not “I agree.” Not “I will comply.” Not “I understood the specific details of your instruction.”
“Roger” tells the controller your transmission reached your ears. It does not tell them which runway you understood them to say.
When a controller issues “Hold short of runway three-six, Piper seven-seven Uniform” and the pilot responds “Roger, seven-seven Uniform,” the controller faces genuine uncertainty. Did the pilot correctly hear “runway three-six”? Did they catch only the tail end of the transmission and key up on instinct? On a runway with landing traffic, that uncertainty matters.
What Do FAA Regulations Actually Require for Readbacks?
AIM Section 4-3-18 addresses the readback and hearback problem directly. It states that pilots are expected to read back parts of ATC clearances and instructions containing altitude assignments, vectors, or runway assignments as a means of mutual verification, and specifically flags runway holding instructions.
FAA Order 7110.65 - the Air Traffic Control handbook that controllers work from - places the obligation on both sides of the radio. Controllers are required to obtain a readback of runway crossing and runway holding instructions. If a pilot responds to a hold-short instruction with only “Roger,” the controller is supposed to request a proper readback.
Controllers are managing multiple aircraft on multiple frequencies, and they miss it sometimes. The gap between what the controller intended and what the pilot understood is precisely where runway incursions live.
What Does a Correct Readback Look Like?
The format is straightforward. Lead with the instruction, close with your call sign.
Controller: “Cessna two-seven-three Sierra, hold short of runway one-zero left, traffic on a two-mile final.”
Correct readback: “Hold short of runway one-zero left, Cessna two-seven-three Sierra.”
The runway number comes back. The call sign goes at the end. The controller can locate your aircraft, confirm your position, and verify that the runway designation they issued matches the one you repeated. If you had misheard “one-zero right” instead of “one-zero left,” the incorrect readback would surface that error before you moved.
Placing the call sign at the end rather than the beginning is the preferred format. Controllers are listening specifically for the repeated instruction to verify accuracy - leading with your call sign makes them wait longer to reach the critical information. Instruction first is cleaner and consistent with AIM guidance.
Which Instructions Require a Specific Readback?
Not every transmission needs a verbatim readback, but several categories always do:
- Runway holding instructions - the specific runway number must come back every time
- Runway crossing instructions - “Cross runway two-seven” gets “Crossing runway two-seven” plus your call sign, not just “Roger, crossing”
- Altitude assignments on departure when the controller wants confirmation
- Squawk codes when assigned by approach or departure control
- Altimeter settings when specifically requested
These categories carry elevated consequences if the message was garbled or misunderstood, which is exactly why they require readbacks.
What’s the Difference Between “Roger,” “Wilco,” and a Real Readback?
“Wilco” - short for “will comply” - is a step beyond “Roger.” It tells the controller you received the transmission and intend to do what was asked. But it is still not a readback.
If a controller issues a hold-short instruction and you respond “Wilco,” they still don’t know which runway you heard. You might be willing to comply with a hold-short at the wrong runway because you misheard the number.
“Roger” closes neither the compliance loop nor the accuracy loop. “Wilco” closes the compliance loop. Only repeating the specific information closes the accuracy loop.
What Happens When Readbacks Break Down?
There are two distinct failure modes. A readback error is when the pilot reads back incorrect information. A hearback error is when the controller listens to a readback and fails to catch that it’s wrong. Both have been documented contributing factors in actual runway incursions. The system is designed to catch errors at both points - when either point fails, the margin collapses.
The Aviation Safety Reporting System (ASRS) - the NASA program that allows pilots to voluntarily report safety incidents without FAA certificate action - contains numerous readback failure reports. Pilots who taxied to the wrong runway because they misheard the assignment. Pilots who crossed active surfaces because no readback was requested. Controllers who issued clearances to the wrong aircraft because two similar-sounding call signs were on frequency simultaneously and the readback confirmed the wrong one.
The most extreme example of communication ambiguity in aviation history is the Tenerife disaster of 1977 - still the deadliest accident in aviation history at 583 fatalities. Among multiple contributing factors, the KLM Boeing 747 crew used language that led them to believe they had a takeoff clearance when they did not, while the tower responded with imprecise language on a foggy runway with no visibility. The procedural changes that followed are part of why standardized phraseology exists today. The principle scales directly down to a single-engine trainer at a small Delta airport: when the readback doesn’t close the loop, the system is open.
How Do Readbacks Affect Your Checkride?
The Airman Certification Standards (ACS) for the private pilot certificate address radio communications throughout the practical test. Examiners watch readbacks specifically - not just whether the applicant said something on the radio, but whether runway instructions came back with the runway number included. Responding with “Roger” to a hold-short instruction during the practical test is a demonstration failure for that task.
If you make a readback error during the checkride and the controller requests a proper readback and you provide one cleanly, that actually demonstrates the system working as designed. Examiners evaluate overall patterns of behavior. What draws scrutiny is a consistent habit of substituting “Roger” for required readbacks without awareness that a full readback was needed.
How Do These Rules Apply at Non-Towered Airports?
The readback requirement applies at every towered airport, regardless of size. At a Class Delta airport without surface detection equipment, the controller works from what they can see out the tower window and what they hear on the frequency. The readback is their primary confirmation that the pilot understood the instruction - there is no technology to backstop the communication gap the way there might be at a larger facility.
At non-towered airports, there is no controller to read back to - but the underlying principle carries through. Position and intention calls on the Common Traffic Advisory Frequency (CTAF) serve the same function: giving other traffic the information they need to build an accurate picture. The communication obligation doesn’t disappear without a controller. It shifts to pilot-to-pilot situational awareness.
How Can You Build Better Readback Habits?
Before taxiing, apply one rule: any hold-short instruction comes with a runway number, and that runway number goes back to the controller every single time.
Ask your flight instructor to evaluate your readbacks specifically. The question is not whether you said something when the controller spoke - it’s whether the runway number came back every time one was assigned. Many pilots are surprised how often the reflex to reach for “Roger” emerges under workload.
The formula for every readback is the same:
- What did the controller tell you to do?
- Say that back - including the specific runway number, altitude, or squawk code.
- Add your call sign at the end.
That is the complete loop. When it closes every time, the system works the way it was designed to.
Key Takeaways
- “Roger” means received - not understood and not will comply. It is never a substitute for a required readback.
- AIM Section 4-3-18 and FAA Order 7110.65 both mandate readbacks for runway holding and crossing instructions; the obligation applies to the pilot and the controller.
- A correct hold-short readback repeats the runway number and ends with your call sign - instruction first, call sign last.
- Readback errors and hearback errors are both documented contributing factors in runway incursions; the system requires both parties to perform their part.
- The reflex to say “Roger” under workload is common even among experienced pilots. Practicing correct readback format on every flight builds the habit before it matters.
Radio Hangar. Aviation talk, built by pilots. Listen live | More articles