How to Read Back an IFR Clearance

CRAFT is the standard memory aid for IFR clearance components: Clearance limit, Route, Altitude, Frequency (departure), Transponder (squawk code). Every IFR clearance contains these elements, and your readback should too — in the same order they were given.

Clearance limit is almost always your destination airport, but occasionally — when ATC cannot issue a full-route clearance — it may be a fix or navaid near the departure airport. In that case you'd proceed to that fix and hold until ATC can issue the rest of your route. Route includes your departure procedure (SID), airways, and any amendments. Altitude means your initial assigned altitude and any crossing restrictions. Frequency is the departure control frequency. Squawk is the four-digit transponder code.

FAA regulations (14 CFR 91.123) and ATC orders require pilots to read back any ATC instruction that contains an altitude assignment, a heading, or a clearance to enter a runway. For IFR clearances, that means the altitude, the route, and the squawk code at minimum.

In practice, experienced pilots read back the entire clearance. Controllers use your readback to verify you got it right. If you read back something incorrectly, the controller will catch it and correct it before you depart. That's the whole point.

Start your readback with your callsign, then work through CRAFT in order. Don't editorialize or add filler. "November 4-5-3 Tango Foxtrot, cleared to Denver International via the KORDA2 departure, then as filed, climb and maintain 5,000, expect flight level 2-3-0 one-zero minutes after departure, departure frequency 1-2-4-point-4, squawk 4-5-1-7" is a complete, professional readback.

Two common habits that identify inexperienced pilots: reading back in a rush and dropping words, and adding "uh" or "roger" before starting. Start with your callsign. Speak at a pace the controller can follow. Read it back in order.

If the clearance came in faster than you could write it down, say so: "November 4-5-3 Tango Foxtrot, unable to copy, say again." Controllers expect this from time to time — it's much better than reading back something wrong.

If you got most of it but missed the squawk: "November 4-5-3 Tango Foxtrot, ready to copy squawk code only." Controllers will give you just that element. Never guess at a squawk code.

The controller will say "Negative" or "Correction" and re-issue the element you got wrong. This is not a problem. Read-back errors happen to everyone and catching them is exactly why the readback system exists.

What controllers notice more than a read-back error is a pilot who reads back confidently wrong and doesn't respond to the correction. Pay attention after your readback — if the controller comes back, something didn't match.