092 IFR Communications topic guide
IFR Clearances and Mandatory Readbacks
An ATC clearance is permission to proceed within the air traffic system under stated conditions. It does not suspend any rule the pilot would otherwise have to follow, and it does not guarantee terrain or obstacle clearance by itself; the pilot remains responsible for flying the aircraft safely within whatever the clearance allows. A clearance limit, the point to which the clearance is valid, matters for exactly this reason: reaching it without a further clearance means the flight has run out of authorised routing, not that it may simply continue on its own judgement.
Readback exists to close the loop on that authority. Not every transmission needs one, and the exam leans hard on knowing exactly which ones do. The list is not arbitrary: it groups around the categories where a single mishear turns directly into a collision risk or a lost aircraft, and everything else is left to a plain acknowledgement.
The readback list, and why these items and not others
The items requiring a full readback are en-route clearances, any clearance to enter, land on, take off from, backtrack, cross, or hold short of a runway, the runway in use, altimeter settings, SSR codes, level instructions, heading and speed instructions, and transition levels. Grouped by purpose, three categories emerge, and each one earns its place on the list for a different reason.
Runway-related clearances sit on the maneuvering area, where two aircraft occupying the same piece of ground or the same runway at the same moment is the most direct collision risk in the whole system, so nothing about them is left to assumption. Heading, speed, and level instructions change the aircraft's actual trajectory through the air; a mishear here does not just misinform, it physically moves the aircraft somewhere the controller does not expect, which is what separation from other traffic depends on. Altimeter settings and SSR codes are how the system measures and labels the aircraft: a wrong QNH quietly corrupts every subsequent altitude reading, and a wrong squawk makes the aircraft appear, to a controller's screen, as a different aircraft or no aircraft at all.
- Runway-related: entering, landing on, taking off from, backtracking, crossing, or holding short of a runway; runway in use
- Trajectory-changing: level, heading, and speed instructions; en-route clearances
- Measurement and identity: altimeter settings, SSR codes, transition levels
Conditional clearances
A conditional clearance ties an instruction to a condition the pilot must confirm personally, most often traffic the pilot is expected to see. The fixed format opens with the callsign of the aircraft being addressed, then states the condition, then the instruction, and the pilot's readback repeats the condition alongside the instruction to demonstrate that the correct reference has actually been identified, not merely heard. A conditional clearance is always issued to one specific aircraft or vehicle; it is never a shared instruction for several aircraft to interpret against each other, because that would reintroduce the very ambiguity the format is designed to remove.
The strictness of the format matters more than it looks. If either the condition or the callsign is missing from the exchange, or the order is scrambled, the exchange no longer meets the definition of a conditional clearance, and a pilot who acts on it without the full readback has acted on an assumption rather than a clearance.
Worked example
Worked example: which items must be read back
Not quite. The correct answer is B.
Correct answer: B
- A. This treats the take-off clearance as the whole of the mandatory content and misses that the heading, altitude, and squawk in the same transmission are each separately on the readback list.
- B. Correct. The runway clearance, the heading and level instructions, and the SSR code each belong to a different category on the mandatory list; the wind is situational information, not an instruction.
- C. This reads back a piece of information that needs no confirmation while dropping the heading, level, and SSR items, which are exactly the ones the mandatory list exists to protect.
- D. This over-includes: reading back situational information such as wind adds nothing and clutters the one transmission where the genuinely mandatory items should be unmistakable.
Step by step
- Separate information from instruction: the wind describes conditions and needs no confirmation, unlike everything that follows it.
- Identify the runway-related item: 'cleared for take-off, runway 27' is a clearance to take off from a runway, which sits on the mandatory list.
- Identify the trajectory items: the heading of 310 and the altitude of 3000 feet are a heading instruction and a level instruction, both mandatory because a mishear here changes where the aircraft actually goes.
- Identify the identity item: squawk 4521 is an SSR code, mandatory because it is how the aircraft is labelled on the controller's display.
- Combine the four mandatory items into the readback and leave the wind out of it.
Common mistakes
Reading back only the headline clearance and treating the rest as separate, optional instructions
Heading, level, and squawk items are independently mandatory even when bundled into the same transmission as a clearance; a controller who hears only the take-off readback still has no confirmation on the items most likely to cause a level bust or a track conflict.
Reading back situational information such as wind or general traffic remarks
This adds frequency time without adding safety value, and on an exam stem it signals that the candidate has not distinguished information from instruction, which is the exact distinction the mandatory list is built on.
Acknowledging a conditional clearance with a plain 'roger' instead of repeating the condition
Only a readback that repeats the condition and the callsign proves the pilot has identified the correct aircraft or vehicle the condition refers to; a bare acknowledgement leaves the controller unable to confirm the pilot saw the same traffic they did.
Free tools for this topic
Related topic guides
Practise IFR Communications the way the exam asks it.
SkyStudy turns IFR Clearances and Mandatory Readbacks and every other IFR Communications topic into exam-style practice questions with explanations, spaced repetition, and timed mock exams. Free to start.
Important information
This page is general educational information for student pilots and may be out of date.
Aviation rules, training requirements, costs, medical standards, and exam details change over time and vary by country, authority, and training organisation, so details here may no longer be current or may differ in your case.
Always confirm the current details with your approved training organisation (ATO) and national aviation authority before relying on them.
SkyStudy is an independent study aid, is not affiliated with EASA or any aviation authority, and does not guarantee any exam or licence outcome.
Last reviewed July 2026