IAA ATCO Licence Theory common mistakes
IAA ATCO Licence Theory · Understand the traps and how to avoid them.
Quoting separation minima, transition altitudes, or speed limits from memory without anchoring them to the specific rule source (e.g., stating a 5 NM radar minimum in a context where the prescribed minimum or wake-turbulence increment differs), so a plausible-sounding number is applied to the wrong situation.
Air Law and ATM numbers are learned as isolated figures in rote revision; candidates memorise the value but not the conditions, exceptions, or units attached to it, and under time pressure the most familiar number surfaces regardless of context.
What to do instead
Build a one-page 'numbers table' per domain with columns: value, unit, condition it applies to, and the exception. When practising, force yourself to state the condition before the number. If you cannot state why the value applies here, mark the item for review rather than guessing.
Confusing the roles and responsibilities in the ATM system - mixing up who issues what (aerodrome versus approach versus area control, or controller versus flight information service versus alerting service) and answering a responsibility question with the wrong unit's task.
Candidates study each unit's functions separately and never compare them side by side, so the boundaries blur; exam items deliberately place a task close to a boundary (e.g., who initiates overdue-aircraft action) and the nearest familiar function wins.
What to do instead
Draw a matrix of units against tasks (separation, traffic information, alerting, SAR initiation, clearances) and complete it from the rules. For each practice item, name the unit and the specific obligation before choosing an answer.
Misreading meteorological reports and forecasts - decoding a METAR or TAF group incorrectly (e.g., wind direction variability, RVR versus visibility, tempo versus becoming, or the meaning of a trend group) and then answering a decision question on the wrong decoded value.
The codes look familiar, so candidates skim; subtle distinctions between similar group types and between prevailing and minimum values are exactly where items are built, and decoding is often rushed to reach the 'real' question.
What to do instead
Decode every practice METAR/TAF aloud into plain language, group by group, before answering anything. Keep a personal list of confusable group pairs and drill them until each is defined in one sentence without reference.
Applying the wrong wind component or drift reasoning in navigation calculations - adding instead of subtracting magnetic variation, mixing true and magnetic, or computing drift and heading correction in the wrong direction.
The arithmetic is easy once set up, so candidates skip the sign discipline; variation, deviation, and drift all involve 'east is least' style rules that are memorised as slogans but not practised with real numbers in both directions.
What to do instead
Adopt a fixed written layout: true track, wind, drift, true heading, variation, magnetic heading, deviation, compass heading. Do twenty short numerical drills in both east and west cases and check each by reasoning whether the result should be larger or smaller than the input.
Treating aircraft performance and wake-turbulence categories as labels rather than as inputs - recalling that a type is 'heavy' or 'medium' but failing to apply the correct separation increment, or confusing approach category (based on speed) with wake category (based on mass).
Both use similar-sounding category names and both appear in separation questions, so the two schemes collapse into one mental bucket; candidates also memorise type lists instead of the definition that determines the category.
What to do instead
Write the definition of each category scheme separately and state what each is used for. For wake separation, practise deriving the required interval from the leader/follower pair rather than recalling a single number, and note where the increment is added to the radar minimum.
Answering human factors items with everyday intuition about attention, memory, or fatigue instead of the defined concepts - for example treating 'complacency' and 'confirmation bias' as interchangeable, or attributing an error to attitude when the scenario describes a slip or lapse.
Human factors vocabulary feels self-explanatory, so candidates do not learn the formal distinctions; items are written so that the intuitive answer is a near-miss of the technical one.
What to do instead
Make a glossary of error types (slip, lapse, mistake, violation) and of bias and fatigue concepts, each with a one-line definition and a concrete ATC example. Classify ten incident vignettes into these categories and justify each classification in writing.
Using non-standard or incomplete phraseology in communication items - omitting the callsign on readback, using 'roger' or 'wilco' where a full readback is required, or failing to read back a clearance item that must be read back in full.
Candidates learn phraseology as vocabulary rather than as a procedure with mandatory readback elements, and in written items the 'sounds natural' option often omits a required element.
What to do instead
Learn the readback requirement as an explicit checklist (route clearance, level, heading, speed, frequency, runway, conditional clearances) and mark each element in practice transmissions. Reject any option that drops a required readback item even if it sounds professional.
Confusing radio navigation aids and their indications - mixing up the information a given aid provides (azimuth versus range versus glidepath), the cockpit indication for on-course versus off-course, or which aid supports which phase of flight.
The aids are studied one at a time and their displays look similar on paper; items test the boundary between them (what the needle means, what happens beyond coverage, what a flag indicates) rather than basic identification.
What to do instead
For each aid, draw the cockpit display and annotate what each needle, flag, and scale means, plus its coverage and typical use. Then answer 'what does the crew see if...' questions from the drawing rather than from memory.
Handling abnormal and emergency scenarios by reciting the checklist sequence without matching it to the stated conditions - applying a generic emergency action when the scenario specifies a particular failure, or forgetting the order in which priorities (aviate, navigate, communicate) constrain the controller's actions.
Checklists are memorised as ordered lists; items present a scenario with one distinguishing detail that changes which procedure or which priority applies, and the memorised sequence overrides the detail.
What to do instead
For each major emergency type, write the trigger conditions, the immediate priority, and the controller's specific actions in that order. Practise by reading a scenario and stating the trigger before the procedure, then check whether the chosen action is consistent with the stated conditions.
Misapplying equipment and operational-procedure details - assuming a capability or procedure that depends on a specific equipment fit (surveillance type, redundancy, mode of operation) or on a defined condition such as weather below a threshold, and answering as if the default case applies.
Candidates learn the normal configuration and general procedure, then treat the exceptions and equipment-dependent variations as footnotes; items are built precisely on the conditional clause.
What to do instead
Build a conditions table for operational procedures: procedure, prerequisite equipment or condition, and what changes when it is not met. When reading an item, underline the conditional words ('provided that', 'when', 'unless') before evaluating the options.