GCAA ATC Licence common mistakes
GCAA ATC Licence · Understand the traps and how to avoid them.
Answering regulatory questions from ICAO Annex text (Annex 2, Annex 11, Doc 4444) instead of from the GCAA Civil Aviation Regulations and the associated GCAA advisory publications, so the answer cites the ICAO figure or rule structure where the national regulation sets a different requirement, definition or approval process.
Most study material available to candidates is ICAO-derived, and ICAO wording is what gets memorised first. Because the GCAA framework implements ICAO standards through its own CAR parts and numbering, the ICAO answer is often close enough to feel right and wrong enough to fail the item.
What to do instead
For every rule you learn, write a two-column note: ICAO source on the left, GCAA CAR part/section on the right, plus a third column for any GCAA difference. When an item is worded with a GCAA or UAE reference, answer from the CAR column only, even if the ICAO answer comes to mind first.
Stating a separation value without stating the conditions that make it valid - giving '5 NM' or '1000 ft' as a free-standing answer when the item is testing whether the candidate knows which standard applies to the situation described (radar or procedural, same or crossing tracks, wake category of the pair, or the unit's published local instructions).
Separation minima are learned as a table of numbers rather than as a decision sequence. Under time pressure the candidate recognises the number in the option list and stops reading the condition clause in the stem.
What to do instead
Practise answering in a three-part chain: source of the rule, triggering condition, then the value. If your written answer cannot produce all three parts, you have not finished the question. Before selecting an option, underline the condition words in the stem (surveillance/procedural, tracks, aircraft types, altitudes).
Treating airspace classification as a single 'controlled/uncontrolled' label, so the candidate cannot say what a Class C or Class D user must actually do - whether a clearance is required, whether a service is provided, whether VFR is permitted - and confuses the airway or ATS route designator system with the airspace class that contains it.
Classes are memorised as a list rather than as a matrix of clearances, services and flight rules. Route designators look like classification information, so the two get blended.
What to do instead
Build and redraw a blank matrix of ATC classes against the questions 'clearance required?', 'service provided?', 'VFR allowed?', 'speed/level constraints?', and refill it from memory until it is stable. Separately revise the route designator convention on its own so it is not learned inside the airspace-class topic.
Issuing or accepting a ground movement clearance that omits a safety-critical element - the holding point, the runway to be crossed, or the limit of the taxi clearance - and not insisting on full readback of those elements before the aircraft moves.
The candidate focuses on the route ('taxi to the apron') and treats the boundary details as obvious or already known by the pilot. Readback is treated as a courtesy rather than as the defence against a runway incursion.
What to do instead
Adopt a fixed issue-and-check template for every taxi clearance: destination, route, any runway crossing, holding point, and any condition. Then verify the readback against the same five items before responding. Practise items by writing the clearance out before looking at the options.
Misreading coded meteorological reports - confusing BECMG with TEMPO and their time groups, reading RVR as visibility or visibility as cloud base, misinterpreting the meaning of the trend or change group, or treating a TAF validity period as the period during which conditions are forecast to occur.
METAR and TAF codes are learned as vocabulary lists rather than as structured messages, so the candidate decodes individual groups correctly but assembles them wrongly. Time groups are the most easily skipped element under exam pressure.
What to do instead
Decode reports element by element in a fixed order, always writing down the time group meaning in words before interpreting the weather. Drill specifically the difference between temporary, becoming and probability groups, and between prevailing visibility and RVR, until you can state each in one sentence without notes.
Mixing up the speeds and categories used in performance and separation reasoning - using indicated airspeed where true airspeed or ground speed is meant, ignoring the effect of altitude and temperature on true airspeed, or confusing wake turbulence category with approach/performance category.
The three speeds and the two category systems are taught close together and share vocabulary. Candidates recognise the term in the stem and answer with the definition they rehearsed most recently.
What to do instead
Write a one-page comparison for the three speeds (what it is measured relative to, what changes it) and a separate one for the two category systems (what they are based on, who uses them). Do calculation items twice: once for the answer, once to check that the speed or category you used matches the one the stem specified.
Reading aeronautical charts by shape and familiarity rather than by legend - misreading minima, altitude constraints on SIDs and STARs, or aerodrome chart symbology, and treating chart information as interchangeable with the textual AIP entry when the two differ in status or currency.
Chart symbols look self-explanatory, so the legend and the effective date are skipped. Candidates also assume the chart is the authoritative source for everything it displays.
What to do instead
For each chart type, list the five symbols or annotations most likely to be misread and check them against the legend during practice. Always locate the chart's effective date and title block before answering, and treat any conflict between chart and text as a prompt to check which document governs.
Using non-standard phraseology or accepting an incomplete readback for a safety-critical clearance - for example substituting everyday wording for a prescribed phrase, failing to distinguish a conditional clearance from an unconditional one, or letting a take-off or line-up clearance go unread back.
Standard phraseology is learned as vocabulary rather than as a closed-loop procedure, and in practice items the candidate responds to the apparent intent of the transmission rather than to its exact wording.
What to do instead
Rehearse clearances as call-and-response pairs out loud, including the required readback items, until the readback is automatic. In written items, compare the transmission word by word against the prescribed phrase before deciding whether it was correct.
Answering human factors items with the general textbook virtue instead of the behaviour the scenario shows - for example choosing 'improve communication' or 'be more assertive' for a case that is actually about workload management, fatigue, or a breakdown in cross-checking between controller and assistant.
Human factors content is abstract and easy to memorise as slogans. Candidates match on the emotional tone of the option rather than on the specific observable behaviour in the scenario.
What to do instead
For every scenario, first write down what the person actually did and what was missing (information, time, cross-check, authority to speak up). Only then look at the options and reject any that name a different concept than the one you identified.
Handling emergency and contingency items by listing actions in the wrong priority or leaving out a step entirely - omitting the protection of the runway and surrounding airspace, failing to record times and decisions, or forgetting the notification chain after the immediate workload has passed.
Emergency procedures are learned as a narrative rather than as a checklist with an order. Under pressure the candidate recalls the dramatic actions (vector, descend, alert) and drops the administrative and protective ones.
What to do instead
Memorise a fixed skeleton: aviate and separate, protect the airspace, gather information, notify, record, then hand over or debrief. Practise by writing that skeleton from memory and then fitting each specific emergency type into it, checking that no stage is empty.