C
R-A-F-T
Verbatim
Why Readbacks Matter
A readback is not just a formality. It is the error-detection layer built into the ATC system. When you read back a clearance, the controller compares what you say against what they issued. If there is a mismatch — wrong altitude, wrong squawk, wrong route — the controller can catch it before it becomes a problem.
FAA Order 7110.65 (the ATC handbook) requires controllers to listen to pilot readbacks and correct any errors. That system only works if pilots read back the right elements, word for word. When pilots paraphrase, abbreviate, or skip elements entirely, the safety check fails silently.
For instrument students, getting readbacks right builds the communication habits that carry forward into every phase of IFR flight — from the initial clearance to the missed approach. For rated pilots looking to sharpen their skills, clean readbacks are one of the clearest signals of professionalism on the frequency.
The CRAFT Acronym
CRAFT stands for the five standard elements of an IFR clearance, listed in the order ATC typically issues them. Knowing the order helps you copy the clearance faster because you know what comes next.
Each element serves a distinct purpose. The clearance limit tells you where your clearance is valid to — usually your destination, but sometimes a fix if ATC cannot issue a full-route clearance. The route is what you'll fly from departure to the limit. Altitude gives you your initial assigned level and, when applicable, an altitude to expect at a later time (important for lost-comms planning). The departure frequency is what you'll switch to after takeoff. The transponder code identifies your flight in the radar system.
When ATC issues a clearance, they do not always announce each element by name. A typical delivery sounds like: “Cleared to Kennedy Airport via the Canarsie One departure, then as filed. Climb and maintain three thousand, expect eight thousand ten minutes after departure. Departure frequency one-two-four-point-four-five. Squawk four-three-two-one.” You have to recognize which part of the clearance each phrase belongs to as it arrives, which is why practicing the structure matters.
Readback Technique
The mechanics of a good readback break down into three habits: write it down first, read back in order, and know what to do when you miss something.
Never read back from memory alone. Copy the clearance as it comes in, then read from what you wrote. This prevents transposition errors — a common mistake where pilots accidentally swap digits in a squawk code or altitude because they are recalling from short-term memory rather than reading.
Use shorthand that you can decode under pressure. A typical approach: write the destination, abbreviate the route with waypoint identifiers, write the initial altitude and expect altitude numerically, jot the frequency, and write the squawk in full. If you have a scratch pad on an EFB like ForeFlight, the clearance scratch field mirrors the CRAFT structure and can help organize your notes as you copy.
The act of writing also buys you a moment to process. Clearance delivery speaks at a steady pace. If you are writing, you can ask for a pause or repeat without losing your place.
Read back in the same order the clearance was issued. This makes it easy for the controller to follow along and spot any discrepancy. A readback that jumps from squawk to route to altitude forces the controller to mentally reorder what you said, which increases the chance that an error slips through.
Start with your callsign, then work through C-R-A-F-T:
- “[Callsign], cleared to Kennedy...”
- “...via the Canarsie One departure, then as filed...”
- “...climb and maintain three thousand, expect eight thousand ten minutes after departure...”
- “...departure one-two-four-point-four-five...”
- “...squawk four-three-two-one.”
The altitude readback must be verbatim — say the full number as issued. “Three thousand” not “thirty” or “three.” The squawk code must be all four digits, spoken individually: “four-three-two-one,” not “forty-three twenty-one.”
If you miss an element, do not guess. Ask for a specific repeat using the element name so the controller knows exactly what to re-issue. Say: “Say again altitude” or “Say again squawk.” Do not say “say again all after” unless you genuinely missed everything from that point — controllers are busy, and a targeted request is faster for everyone.
If the frequency is too congested to ask immediately, copy what you have, issue the readback for the elements you are confident about, and flag the missing piece: “[Callsign] ready to copy, did not copy altitude.” The controller will fill in the gap.
Never fill in a blank with what you expect the clearance to say. Expected altitudes, routes, and squawk codes do not always match what is actually issued. If you did not hear it, you do not have it.
Common Mistakes
Most readback errors fall into a small number of patterns. Recognizing them helps you catch them in your own technique before they become habits.
| Element | Wrong Readback | Correct Readback |
|---|---|---|
| Altitude | “Three for altitude” or “climbing to three” | “Climb and maintain three thousand” |
| Squawk code | “Squawking forty-three twenty-one” | “Squawk four-three-two-one” |
| Departure frequency | No readback — pilot skips it entirely | “Departure one-two-four-point-four-five” |
| Runway assignment | “Roger” or no response | “Runway two-two left, [callsign]” |
Skipping the departure frequency readback is one of the most common omissions because it feels like low-stakes information — you can always ask for the frequency again after takeoff. But the frequency readback is part of the mandatory readback sequence, and omitting it is an incomplete readback regardless of intent.
Acknowledging a runway assignment with “roger” is another common mistake that many pilots do not realize is incorrect. Runway assignments require an explicit readback of the runway number and, where applicable, the letter designator (left, right, center). This applies both at towered airports and when receiving taxi instructions.
Building Proficiency
Clearance readback is a motor skill as much as a knowledge skill. Knowing the rules does not automatically produce clean, fast readbacks under pressure. The only way to build that proficiency is repetition in realistic conditions.
Simulator training is particularly effective for this because the environment can be paused, replayed, and adjusted in ways a real aircraft cannot. An instructor can issue a clearance, evaluate your readback, and immediately debrief on what you missed — then do it again. After several iterations, the CRAFT structure becomes automatic and the cognitive load of copying drops significantly, freeing up capacity for everything else happening in the cockpit at departure time.
Between sessions, listen to LiveATC.net feeds from busy clearance delivery frequencies. Practice copying clearances in real time without pausing. You will quickly identify which elements you consistently miss or mis-transcribe, and you can focus your simulator work on those gaps.
As you progress toward professional operations, the goal shifts from using CRAFT as a written checklist to internalizing the structure so that the readback flows naturally. Experienced pilots do not write the letters C-R-A-F-T on their pad before every clearance — but the structure is still there, driving the sequence. The mnemonic is a scaffold, not a permanent fixture. Build on it until it disappears into fluency.
Frequently Asked Questions
CRAFT is an acronym for the five standard elements of an IFR clearance: Clearance limit, Route, Altitude, Frequency, and Transponder. The letters follow the order that ATC typically issues each element, which makes it a reliable framework for copying and reading back clearances without missing anything.
No. “Roger” only confirms that you heard a transmission — it does not confirm that you copied it correctly. A verbatim readback is what allows the controller to compare what they issued against what you received and catch any discrepancy before it affects the flight. FAA Order 7110.65 requires controllers to listen for and correct readback errors, but that safety check only works when pilots actually read back the critical elements — especially altitudes, headings, runway assignments, and squawk codes.
The four most common mistakes are: abbreviating the altitude (“three” instead of “three thousand”), grouping the squawk code digits (“forty-three twenty-one” instead of “four-three-two-one”), skipping the departure frequency entirely, and acknowledging a runway assignment with “roger” instead of reading back the runway number. All of these are incomplete readbacks even if they sound natural in normal conversation.
Ask for a targeted repeat using the element name — for example, “Say again altitude” or “Say again squawk.” Avoid asking for everything to be repeated unless you genuinely missed most of the clearance. If you caught most of it but missed one piece, read back what you have and flag the gap: “[Callsign] ready to copy, did not copy altitude.” The most important rule is: never fill in a blank with what you expect the clearance to say. If you did not hear it, you do not have it.
Yes. Reading back in CRAFT order — clearance limit, route, altitude, frequency, transponder — makes it easy for the controller to follow along and compare your readback against what was issued. When pilots read back elements out of order, the controller has to mentally reorder what they hear, which increases the chance that a discrepancy slips through unnoticed. Consistent order is part of what makes the readback system reliable.
Practice IFR Clearances in the Simulator
Book a session with an airline pilot instructor to sharpen your clearance readback technique and IFR communication skills.
Continue Your IFR Training
Related programs and resources for instrument pilots
Instrument Rating Training Guide
Complete guide to earning your instrument rating in NYC — curriculum, requirements, and training timeline.
IFR Currency Training
Maintain instrument currency with structured simulator sessions — six approaches, holds, and tracking.
Professional Pilot IFR Prep
Advanced IFR training for airline interviews and ATP checkrides — SID/STAR procedures and CRM.
Business Jet IFR Transition
Single-pilot jet IFR procedures — high-altitude operations, automation management, and crew concepts.
Rusty Pilot Training
Rebuild IFR confidence safely after a break from flying — structured refresher with airline pilot instructors.
FAA WINGS LOFT Scenarios
Line Oriented Flight Training with FAA WINGS credit — real-world IFR scenarios from airline training.