ATC clearance readbacks: what to say back and why

What a readback is

A readback is repeating the safety-critical parts of an ATC clearance or instruction you just heard. It is not politeness. It is how pilot and controller confirm they share the same picture before the airplane moves.

In the US, the FAA Aeronautical Information Manual (AIM) covers this in AIM 4-4-7 (Pilot Responsibility upon Clearance Issuance) and related pilot/controller roles. In Europe the hard list sits in SERA.8015(e); the idea is the same even when the wording differs.

What the FAA expects you to read back

AIM 4-4-7 says pilots of airborne aircraft should read back parts of clearances and instructions that contain altitude assignments, vectors, or runway assignments, so both sides catch misheard numbers.

Also:

• Include your aircraft identification in every readback and acknowledgment
• Read back altitudes, altitude restrictions and vectors in the same sequence they were given
• Do not read back altitudes that only appear on a charted procedure (DP, approach, etc.) unless the controller states them
• The initial readback of a taxi, departure or landing clearance should include the runway assignment (including Left/Right/Center when applicable)

Hold-short instructions are a classic must-read-back item in pilot/controller roles guidance: if tower says hold short, say it back.

Tip: if you are choosing between a vague “roger” and repeating the number, repeat the number.

How to read back cleanly

• Call sign first or last, but always there
• Numbers in the same order you heard them
• Short: return the safety items, do not rewrite the whole clearance
• If you are unsure, say “say again” instead of guessing

Example: taxi and hold short

Runway assignment and hold-short are the items you cannot skip.

Example: takeoff clearance

Example: altitude and heading

Altitude and vector (heading) are exactly the “numbers” AIM 4-4-7 wants verified.

Example: frequency change

Conditional clearances

A conditional clearance (“behind the landing Cessna, line up and wait…”) is only valid if the condition is true. Read back the condition, not just the action. If you lose sight of the traffic in the condition, do not enter: tell the controller.

Common student mistakes

1. “Roger” only after a runway, altitude or heading assignment
2. Missing call sign on a busy frequency with similar N-numbers
3. Reordering numbers and confusing yourself
4. Reading back while still listening - if you get stepped on, ask “say again”
5. Assuming silence means correct - controllers listen for readbacks, but you still own not flying a wrong clearance

Roger, wilco and readback

“Roger” means you heard the transmission. “Wilco” means you will comply. Neither replaces a readback when altitude, heading, runway, hold-short or a newly assigned frequency needs verification.

What a readback does not replace

A readback does not replace checking charts before you fly, asking when a clearance would create a safety conflict, or refusing a clearance you cannot comply with and requesting an amendment. AIM 4-4-7 also reminds you that accepting or refusing the clearance is your responsibility.

ICAO / EASA vs FAA (quick contrast)

Under SERA.8015(e) in Europe you also always read back route clearances, runway-related clearances/instructions (enter, land, take off, hold short, cross, taxi, backtrack), runway-in-use, altimeter setting, SSR code, newly assigned channel, level/heading/speed instructions, and transition levels. FAA AIM is framed more around altitudes, vectors and runway assignments, with hold-short called out in roles guidance. If you train on both sides of the Atlantic, learn both lists; do not assume the US habit covers every SERA item.

Practice

• Pause a real clearance recording and read it back out loud before you hear the pilot
• Use the same pattern: critical items + call sign
• Record yourself: cut filler, keep the numbers

If you want to practice readbacks with a controller that answers you, try KoAir in English or Spanish.

Related: ICAO phonetic alphabet.