What must be read back: SERA.8015 and CAP 413, item by item

The items SERA.8015(e) says must always be read back, what CAP 413 Edition 24 adds in the UK, and a CAP 413 example for each.

Published 22 Oct 2026 by Jan Hobler, CEO.

Under SERA.8015(e)(1) of Regulation (EU) No 923/2012, the flight crew must always read back route clearances, runway clearances and instructions, runway-in-use, altimeter settings, SSR codes, new frequencies, level, heading and speed instructions, and transition levels. UK SERA.8015(e)(1) has the same list, and CAP 413 Edition 24 (effective 1 July 2026) adds taxi instructions, approach clearances, VDF information and type of ATS service. Every readback includes the aircraft callsign.

A readback repeats all, or the specified part, of a message "exactly as received" (CAP 413, Table 8). Examples use OK-BWG and fictional stations.

What does SERA.8015(e) require?

The EU text, in EASA's Easy Access Rules for SERA (August 2025 revision; SERA.8015 last amended by Regulation (EU) 2024/1111) [1]:

(1) The flight crew shall read back to the air traffic controller safety-related parts of ATC clearances and instructions which are transmitted by voice. The following items shall always be read back: (i) ATC route clearances; (ii) clearances and instructions to enter, land on, take off from, hold short of, cross, taxi and backtrack on any runway; and (iii) runway-in-use, altimeter settings, SSR codes, newly assigned communication channels, level instructions, heading and speed instructions; and (iv) transition levels, whether issued by the controller or contained in ATIS broadcasts.

(2) Other clearances or instructions, including conditional clearances and taxi instructions, shall be read back or acknowledged in a manner to clearly indicate that they have been understood and will be complied with.

Point (e)(3) obliges the controller to correct any discrepancy; (e)(4) exempts CPDLC messages. UK SERA.8015(e) [2] has points (1) to (4) word for word; the EU points (5) and (6), on vehicle drivers, have no UK equivalent.

What does CAP 413 add in the UK?

CAP 413 paragraph 2.69 lists 14 ATS messages the pilot or driver reads back in full [3]. Compared with SERA.8015(e)(1), it:

  • requires taxi and towing instructions in full, where SERA allows a clear acknowledgement off the runway;
  • adds approach clearances, VDF information and type of ATS service;
  • requires altimeter settings to include the units when the value is below 1000 hectopascals;
  • allows a route clearance to be acknowledged "in a positive manner" where the ATS authority authorises it (paragraph 2.68).

Other items may take an abbreviated readback (paragraph 2.70).

Which items must be read back, and how?

"SERA" is SERA.8015(e); "CAP" is the list in CAP 413 paragraph 2.69; "SERA App. 1" is Appendix 1 to AMC1 SERA.14001. Each example follows the pattern named.

ItemRequired byATC transmissionReadbackPattern
Route clearanceSERA (1)(i); CAP 5OK-BWG, after departure cleared to zone boundary via route Echo. Climb to altitude 2000 feet QNH 1012, squawk 6522After departure cleared to zone boundary via route Echo. Climb to altitude 2000 feet QNH 1012, squawk 6522, OK-BWGCAP 413 2.68
Runway-in-useSERA (1)(iii); CAP 7OK-BWG, departure runway 24 wind 250 8, QNH 1012, temperature 14, dewpoint 9Runway 24, QNH 1012, OK-BWGCAP 413 4.8
TaxiSERA (2); CAP 1OK-BWG, taxi holding point A1 runway 24 via CharlieTaxi holding point A1 runway 24 via Charlie, OK-BWGCAP 413 4.12
Enter (line up)SERA (1)(ii); CAP 8OK-BWG, runway 24, line upRunway 24 line up, OK-BWGCAP 413 4.20
Take offSERA (1)(ii); CAP 8OK-BWG, runway 24 cleared for take-offRunway 24 cleared for take-off, OK-BWGCAP 413 4.27, 4.35
LandSERA (1)(ii); CAP 8OK-BWG, runway 24, cleared to land, surface wind 250 8Runway 24 cleared to land, OK-BWGCAP 413 4.51
CrossSERA (1)(ii); CAP 8OK-BWG, taxi to the flying club, via A1 cross runway 24, report vacatedTaxi to the flying club, via A1 cross runway 24, wilco, OK-BWGCAP 413 4.12
Hold shortSERA (1)(ii); CAP 8OK-BWG, hold short of runway 24Holding short, OK-BWGSERA App. 1 item 1.4.8; CAP 413 4.39
BacktrackSERA (1)(ii); CAP 8OK-BWG, backtrack runway 24Backtrack runway 24, OK-BWGSERA App. 1 item 1.4.7(p); CAP 413 Ch. 11, Figure 6, note 3
Altimeter settingSERA (1)(iii); CAP 10OK-BWG, QNH 998 hectopascalsQNH 998 hectopascals, OK-BWGCAP 413 2.71, 3.9
SSR codeSERA (1)(iii); CAP 9OK-BWG, squawk 64026402, OK-BWGCAP 413 2.68, 2.69
Frequency changeSERA (1)(iii); CAP 12OK-BWG, contact Birch Approach 129.125Birch Approach 129.125, OK-BWGCAP 413 2.60
LevelSERA (1)(iii); CAP 2OK-BWG, descend to altitude 2000 feet QNH 1012Descend to altitude 2000 feet QNH 1012, OK-BWGCAP 413 3.9
HeadingSERA (1)(iii); CAP 3OK-BWG, for spacing turn left heading 050 degreesLeft heading 050 degrees, OK-BWGCAP 413 5.13
SpeedSERA (1)(iii); CAP 4OK-BWG, maintain present speedMaintain present speed, OK-BWGCAP 413 3.19
Type of ATS serviceCAP 13 onlyOK-BWG, Basic ServiceBasic Service, OK-BWGCAP 413 Ch. 11, Figure 26
Transition levelSERA (1)(iv), including ATIS; CAP 14No CAP 413 exampleIn full
Approach clearance, VDF informationCAP 6, 11 onlyNo example hereIn full

In the UK, HOLD SHORT is used only where no suitable holding point exists or to reinforce a clearance limit (CAP 413 Table 8). ROGER and WILCO are insufficient for HOLD, HOLD POSITION and HOLD SHORT OF: the reply is HOLDING or HOLDING SHORT (SERA App. 1, item 1.4.8).

How is a readback ended, and how is it corrected?

CAP 413 paragraph 2.68: "Read backs shall always include the aircraft callsign." SERA.14075(a)(1) requires it in any acknowledgement from an aircraft. CAP 413 examples normally place it at the end, and the pilot abbreviates it only after the ground station has (paragraph 2.26). A wrong readback draws NEGATIVE and the correct version (paragraph 2.71):

  1. TOWEROK-BWG, QNH 1003
  2. OK-BWGQNH 1013, OK-BWG
  3. TOWEROK-BWG, negative, QNH 1003
  4. OK-BWGQNH 1003, OK-BWG

SERA.14075(d) specifies "NEGATIVE I SAY AGAIN"; CAP 413 Table 8 keeps that phrase for repeated incorrect readbacks.

What does not need a readback?

Information is outside both lists: surface wind, temperature, dewpoint, traffic and aerodrome information. It is acknowledged with the callsign or "Roger" and the callsign, not "copy the weather" (CAP 413 paragraph 2.56). CAP 413 reads back runway and QNH from departure information but not wind or temperature (paragraph 4.8). A request to report takes WILCO, added to any readback in the same transmission (paragraphs 4.12, 4.47). Other clearances and instructions still need a readback or a clear acknowledgement (SERA.8015(e)(2)).

How is a conditional clearance given and read back?

Under SERA.8015(ec), a conditional phrase affecting the active runway is used only when controller and pilot both see the aircraft or vehicle concerned, which must be the first to pass in front. CAP 413 paragraph 4.33 sets the order: callsign, condition, identification of the subject, clearance, reiteration of the condition. It limits the clearance to one movement; for landing traffic, that is the first aircraft on approach [3].

The pilot's reply differs. In EASA states, Appendix 1 to AMC1 SERA.14001, item 1.4.10, gives the controller "(condition) LINE UP (brief reiteration of the condition)" and the pilot "(condition) LINING UP (brief reiteration of the condition)"; GM1 SERA.8015(ec) gives the example "SCANDINAVIAN 941, BEHIND DC9 ON SHORT FINAL, LINE UP BEHIND" [1]. SERA adds the runway number where multiple runway operations could cause confusion (item 1.4.10(g)). In the UK, the worked example in CAP 413 paragraph 4.33 names the runway, and the pilot repeats the clearance verbatim [3].

EASA (SERA)
  1. TOWEROK-BWG, behind the PA28 on short final, line up behind
  2. OK-BWGBehind the PA28 on short final, lining up behind, OK-BWG
UK (CAP 413)
  1. TOWEROK-BWG, behind the PA28 on short final, line up runway 24 behind
  2. OK-BWGBehind the PA28 on short final, line up runway 24 behind, OK-BWG

SERA.8015(e)(2) lets conditional clearances be read back or acknowledged, but a conditional line-up is an instruction to enter a runway, which (e)(1)(ii) puts in the always list. Under both forms the pilot repeats the condition, the movement and the reiteration.

Does the list apply at a UK AFIS or air/ground aerodrome?

At a UK AFIS aerodrome, CAP 797 paragraph 14.13 requires a full readback of taxi instructions, runway-in-use, runway crossing and hold-short instructions, SSR instructions, altimeter settings, frequency changes, type of service and transition levels, plus clearances relayed from ATC [4]. At an air/ground station, a relayed ATC clearance is read back in full (CAP 413 paragraph 4.152). More in AFIS, air/ground and ATC: what changes in the radio call.

Where BeWinged fits

BeWinged is a radiotelephony simulator, in beta. It is not an air traffic service; the controller is simulated and controls no traffic. Every session ends in a debrief of the student's radio calls, with each readback's verdict element by element, on the student's dashboard and visible to the instructor. Reading back a frequency does not retune the radio: the first call on the new frequency is a separate step. Set up three student sessions (45 minutes of the school's time).

Sources

FAQ

Must taxi instructions be read back?

SERA.8015(e)(2) requires taxi instructions to be read back or clearly acknowledged; taxiing on a runway is always read back. In the UK, CAP 413 paragraph 2.69 requires taxi instructions in full.

Is the surface wind read back?

No. It is in neither the SERA.8015(e)(1) list nor the CAP 413 paragraph 2.69 list.

Is ROGER or WILCO enough for a hold instruction?

No. The reply is HOLDING or HOLDING SHORT (Appendix 1 to AMC1 SERA.14001, item 1.4.8).