Hold-Short Readback: The One You Cannot Get Wrong
This is the one readback you can never skip — it is a direct runway-safety issue. Here is exactly what to say, why it exists, and the traps that catch new pilots. · 7 min read
On the radio, there are two kinds of instructions: the ones you simply acknowledge with your callsign, and the short, specific list you must read back word-for-word. At the very top of that must-read-back list is the hold-short instruction — and its close cousin, the runway-crossing clearance. If you learn to do nothing else perfectly as a student pilot, learn these, because they sit directly on top of one of aviation’s most serious risks: putting an aircraft on a runway where it should not be. Getting the hold-short readback right, every single time, is the single highest-value habit you can build on the ground.
What must be read back verbatim
Per AIM 4-3-18, you are required to read back — with your callsign attached — any instruction to do the following. Notice these all share a theme: they are all points where being at the wrong place or wrong number could put you in conflict with another aircraft.
- Hold short of a runway — stop before the marked line and do not cross
- Cross a runway — you may proceed across a specific runway
- Line up and wait — taxi onto the runway and hold (not a takeoff clearance)
- Any assigned runway (for takeoff or landing)
- Any assigned altitude or heading (vector)
- Any assigned transponder (squawk) code
The hold-short readback
When Ground gives you a taxi route with a hold-short, your readback must contain the runway number AND the words "hold short," plus your callsign. Do not shorten it to "roger" or "will do" — the controller specifically needs to hear you say the runway and the hold-short back:
When you reach that hold-short line, you stop — even if the runway looks empty, even if you are in a hurry, even if you are pretty sure it is fine. You do not cross until you are explicitly cleared to. "Pretty sure" is exactly the state of mind that causes runway incursions.
The runway-crossing readback
If your taxi route needs to cross a runway, Ground issues a separate, explicit clearance to cross — and it gets the same word-for-word readback. A crossing clearance is never implied by your taxi instructions; you must actually hear "cross Runway XX":
A key rule change to know: controllers must issue a separate crossing clearance for each runway you cross, and can no longer clear you to "cross" multiple runways at once. So expect to be told to hold short of, then individually cleared across, each runway on a complex taxi route. Read each one back.
The line-up-and-wait trap
"Line up and wait" belongs on this list because it puts you ON the runway — but it is NOT a takeoff clearance. It means taxi into position and hold there while Tower waits for spacing. Read it back, then hold on the centerline and do nothing until you hear the actual words "cleared for takeoff":
Why it matters this much
A runway incursion — any incorrect presence of an aircraft, vehicle, or person on a runway — is one of aviation’s most serious ground risks, and the vast majority involve a breakdown in communication or expectation. The verbatim readback is the safeguard that catches those breakdowns before they turn into a collision: it lets the controller hear, in your own words, that you copied a safety-critical instruction correctly. If you read back the wrong runway, or you were never actually cleared to cross, the controller hears it in your readback and stops you. A missing or wrong readback removes that safety net at the exact moment it matters most.
So build one unbreakable habit: when in doubt, read it back and HOLD. You can never be faulted for holding short of a runway. You can be violated — and worse — for crossing one without a clearance. If you are ever unsure whether you are cleared to cross, stop and ask: "Ground, verify Five-Two-Kilo cleared to cross Runway 31?" That question is always the right call.
Phraseology sourced from the FAA Aeronautical Information Manual (Change 3, effective 9 July 2026) and the Pilot/Controller Glossary. Check the AIM · Last reviewed 13 August 2026.