AIM ¶ 4-4-7 — ATC Clearance Readback
AIM 4-4-7 explains pilot duties when receiving an ATC clearance: record it, read back altitudes, vectors, and runway assignments with your call sign.
In Plain English
AIM 4-4-7 covers what you must do the moment ATC issues a clearance. For IFR operations, write the clearance down — controllers may add or change items (like a specific departure route) compared to your flight plan, which signals other traffic is in play.
The core practice is the clearance readback. Read back the parts of any clearance or instruction that contain:
- Altitude assignments and altitude restrictions
- Vectors (headings)
- Runway assignments (including left, right, or center)
Key rules:
- Always include your aircraft identification in readbacks and acknowledgments — critical when frequencies are congested or similar call signs are on frequency.
- Read back items in the same sequence ATC gave them.
- Do not read back charted altitudes from DPs or approaches unless the controller specifically states them.
- Initial taxi, departure, or landing clearance readbacks must include the runway assignment.
Finally, it is your responsibility as PIC to accept or refuse the clearance. If something doesn't work for your aircraft or situation, say so — don't just accept it.
AIM Source Text
FAA AIM ¶ 4-4-74-4-7. 4-4-7. Pilot Responsibility upon Clearance Issuance
Record ATC clearance. When conducting an IFR operation, make a written record of your clearance. The specified conditions which are a part of your air traffic clearance may be somewhat different from those included in your flight plan. Additionally, ATC may find it necessary to ADD conditions, such as particular departure route. The very fact that ATC specifies different or additional conditions means that other aircraft are involved in the traffic situation. ATC Clearance/Instruction Readback. Pilots of airborne aircraft should read back those parts of ATC clearances and instructions containing altitude assignments, vectors, or runway assignments as a means of mutual verification. The read back of the “numbers" serves as a double check between pilots and controllers and reduces the kinds of communications errors that occur when a number is either “misheard" or is incorrect. Include the aircraft identification in all readbacks and acknowledgments. This aids controllers in determining that the correct aircraft received the clearance or instruction. The requirement to include aircraft identification in all readbacks and acknowledgements becomes more important as frequency congestion increases and when aircraft with similar call signs are on the same frequency. EXAMPLE- “Climbing to Flight Level three three zero, United Twelve" or “November Five Charlie Tango, roger, cleared to land runway nine left." Read back altitudes, altitude restrictions, and vectors in the same sequence as they are given in the clearance or instruction. Altitudes contained in charted procedures, such as DPs, instrument approaches, etc., should not be read back unless they are specifically stated by the controller. Initial read back of a taxi, departure or landing clearance should include the runway assignment, including left, right, center, etc. if applicable. It is the responsibility of the pilot to accept or refuse the clearance issued.
Oral Exam Questions a DPE Might Ask
Q1What items in an ATC clearance should a pilot read back?
Per AIM 4-4-7, pilots should read back the parts containing altitude assignments, vectors, and runway assignments as a means of mutual verification, and always include the aircraft identification.
Q2Why is it important to include your aircraft identification in every readback?
Per AIM 4-4-7, including the aircraft ID helps controllers confirm the correct aircraft received the clearance — especially important during frequency congestion or when similar call signs are on the same frequency.
Q3Are charted altitudes on a DP or instrument approach required to be read back?
Per AIM 4-4-7, altitudes contained in charted procedures such as DPs and instrument approaches should not be read back unless they are specifically stated by the controller.
Related Paragraphs in AIM Chapter 4