Practice taxi and hold short readbacks

This is practice for the taxi readback, said out loud to a simulated controller. The call names the runway you were given, and it names the hold short.

14 CFR 91.129(i) says that at an airport with an operating control tower, you do not operate an aircraft on a runway or a taxiway, and you do not take off or land, unless you have an appropriate clearance from ATC. AIM 4-3-18 says approval is required before you move onto the movement area while the tower is open, and a clearance is required before you taxi on a runway, take off, or land. A clearance is also required before you cross any runway. ATC issues an explicit clearance for every runway crossing.

What the taxi clearance sounds like

When you are assigned a takeoff runway, AIM 4-3-18 says ATC first specifies the runway, then issues the taxi instructions, then states any hold short or runway crossing clearance if the route crosses a runway. That transmission does not authorize you to enter or cross the assigned departure runway. The word cleared is not used for the taxi. FAA Order JO 7110.65, paragraph 3-7-1, says the same thing on the controller side: do not use cleared to authorize an aircraft to taxi. Use taxi, proceed, or hold.

State your position when you call for taxi. The AIM example is the whole exchange. The pilot says the facility, the call sign, the place on the airport, ready to taxi, and IFR or the destination. The controller answers with the runway, the taxiways, and hold short of a named runway. The pilot reads back the call sign, the runway, and hold short of that runway. A second example, after landing, is hold short of the parallel runway, read back as hold short of that runway. Nothing in those examples is a bare roger.

JO 7110.65 paragraph 3-7-2 says the taxi route has to include the specific route. When the clearance is to a runway, the controller confirms you have the correct runway assignment. A readback of the taxi instructions that includes the runway assignment can be that confirmation. If you will hold short of a runway, the route is issued up to the hold short point, and a crossing clearance says where to cross. If you will hold short of some other point, you get the route up to that point, or the whole route and then the hold short. The absence of holding instructions authorizes you to cross taxiways that intersect the route. It does not authorize a runway.

The readback the controller must hear

AIM 4-3-18 says that when taxi instructions come from the controller, pilots should always read back three things. The runway assignment. Any clearance to enter a specific runway. Any instruction to hold short of a specific runway, or to line up and wait. A note in the same paragraph says ATC is required to obtain a readback of all runway hold short instructions. Another note says controllers request that readback when the pilot or vehicle does not give it.

JO 7110.65 paragraph 3-7-2, item 8, is the controller version. Request a readback of runway hold short instructions when it is not received. The phrase is read back hold instructions. The examples are a taxi with a hold short, a pilot who answers only roger, and the controller coming back for the readback. The same thing happens at the hold short line for departure, and for a vehicle. A note says the controller may also demand a readback for any point on the movement area when the readback is needed. Your job on the first transmission is to make that second call unnecessary. Call sign, runway, hold short of the named runway.

AIM 4-4-7 fits the same transmission. The initial readback of a taxi clearance should include the runway assignment, including left, right, or center if it applies. Aircraft identification goes in every readback. If you are unsure, 14 CFR 91.123(a) says you immediately request clarification. AIM 4-3-18 quotes the pilot in command rule and says to get clarification of any taxi clearance you do not understand.

Line up and wait is not a takeoff, and AIM 4-3-18 tells you to read it back. AIM 5-2-5 says it puts you on the assigned runway, aligned for departure, waiting. It is not a takeoff clearance. Pilots have read it back correctly and then departed anyway. If the takeoff clearance does not come in a reasonable time, call. The AIM points at cases where two minutes or more passed between line up and wait and the later event, when no delay had been announced. If a similar call sign is on the frequency, ask before you move.

Runway incursion habits that are in the book

AIM 4-3-18 says you can ask for progressive taxi if you are unfamiliar or confused, and the controller can issue step-by-step routing for traffic or a closed taxiway. JO 7110.65 paragraph 3-7-2 also calls for progressive instructions in reduced visibility when the tower cannot see the route.

After landing, AIM 4-3-21 says exit without delay at the first available taxiway, or the one ATC named. Do not turn onto another runway unless ATC authorized it, and do not stop or reverse on the runway without approval. You are clear when every part of the airplane is past the runway edge and the holding position markings. Then you hold unless further instructions were already issued. Stay on tower until you are sent to ground. The taxi clearance to parking does not let you enter or cross a runway.

Practice it out loud

WilcoAI is the simulated controller. You hear the taxi clearance, hold push-to-talk, and read back the runway and the hold short. The score is correctness, clarity, and speed. The debrief shows what you got right, what you missed, what to watch out for, and the transcript. One Daily Challenge attempt a day is free, about 60 to 90 seconds, with a streak and badges. No account. Set a callsign and aircraft once. iPhone and iPad, iOS 26 or later. The session needs internet. In Phase Block and Full Flight the controller says negative or correction on a miss. The number words are on the phraseology page. The first solo ground call is on the student pilot page.

Training aid only. Not for flight use. Never act on simulated clearances.