JCAA CPL Theory Exam common mistakes
JCAA CPL Theory Exam · Understand the traps and how to avoid them.
On Air Law questions, answering from how the aircraft is actually flown in practice (e.g. "we always fly VFR below 3000 ft so that must be the rule") rather than from the stated rule, and confusing ICAO Annex provisions with the national implementing regulation that actually governs the flight.
Candidates learn procedures by habit and by copying what their instructor does, so the operational shortcut feels like the rule. They also read only one layer (Annex or national AIP/regulation) and assume the other says the same thing, when the national rule may be stricter or add a requirement.
What to do instead
For every Air Law item, force yourself to name the source layer first: is this an ICAO Annex standard, a national regulation, or a local AIP/ATC procedure? Then answer from that layer only. Build a one-page comparison table for the recurring topics (VFR minima, fuel reserve, documents carried, right of way, licence validity) with the Annex value and the national value side by side, and review it before each practice set.
Mixing up VMC minima and cloud-clearance values between airspace classes and altitude bands, and applying the wrong figure when the question gives a class and a level (e.g. using the 5 km flight-visibility figure at a level where 8 km applies, or applying the 1500 m cloud distance in Class F instead of the correct value for that band).
The minima are a matrix (class x altitude band x visibility/distance-from-cloud) and candidates memorise a single row or a single number instead of the whole table. Under time pressure they grab the most familiar number rather than reading the class and level in the stem.
What to do instead
Redraw the full VMC minima matrix from memory once a day until it is exact, then check it against the regulation. On each question, underline the airspace class and the altitude before choosing. Practise deliberately with questions that pair the same visibility with different classes so you feel the distinction rather than pattern-matching a number.
Confusing airframe and powerplant system logic: treating the constant-speed propeller as directly linked to manifold pressure, mis-stating what the mixture control actually does at altitude, or mixing up which system provides which indication (e.g. attributing fuel-flow indication to the electrical system or misreading the meaning of a falling oil pressure with rising temperature).
These systems are taught as separate chapters and candidates memorise components without the causal chain. They also never sit in the aircraft or a mock-up tracing where a gauge signal comes from, so the relationships stay abstract and easy to swap.
What to do instead
For each system (fuel, oil, electrical, propeller, hydraulic/pneumatic, ice protection) write a one-paragraph cause-and-effect chain: what the control moves, what the sensor measures, what the gauge displays, and what a given abnormal indication implies. Then answer system questions by walking the chain rather than recalling a fact. Use a simple schematic you draw yourself, not a borrowed diagram.
Computing performance and planning figures with the wrong units or the wrong reference: mixing kg and lb, using indicated instead of true airspeed in a navigation or performance calculation, forgetting to apply the pressure-altitude and temperature corrections before entering the chart, or ignoring wind when computing the take-off/landing distance.
Candidates learn the formula but not the entry conditions of the chart or table. Unit slips and skipped correction steps survive because the resulting number still looks plausible, so nothing signals the error.
What to do instead
Adopt a fixed written routine for every calculation: list given values with units, convert to one system, derive pressure altitude, derive density altitude, then enter the chart, then apply wind/slope/surface corrections in a stated order. Carry units through every line and sanity-check the answer against a rough mental estimate. Do ten chart-reading questions per session using this routine until it is automatic.
Answering Human Performance items from intuition about how people "should" behave rather than from the defined concept, e.g. describing hypoxia as simple tiredness, confusing spatial disorientation with a vestibular illusion by name, or attributing a decision error to personality when the question is about a specific hazardous attitude or a limitation of the senses.
The domain uses precise vocabulary (hypoxia types, illusions, hazardous attitudes, workload and vigilance concepts) and candidates answer with everyday synonyms. They also read the scenario and react to the story instead of identifying which defined phenomenon the stem is testing.
What to do instead
Build a glossary card per concept: definition, cause, recognisable symptoms, correct countermeasure. For scenario questions, first name the phenomenon in one word, then choose the option that matches that definition rather than the option that sounds most sensible. Where two options are both plausible, eliminate the one that describes a different phenomenon from your glossary.
Misreading meteorological reports and forecasts: decoding a METAR or TAF group incorrectly (e.g. treating a trend group as a temporary condition, misreading CAVOK as merely "good weather" without checking the visibility and cloud conditions it implies, or confusing QNH with QFE in an altimeter-setting question).
The coded groups look similar and candidates learn them by recognition rather than by decoding each group in order. Under exam pressure they skim the report, spot a familiar token, and answer on that token alone.
What to do instead
Decode every METAR and TAF group by group in writing: wind, visibility, weather, cloud, temperature/dewpoint, pressure, trend. Never answer from a single token. Learn the exact definitions of CAVOK, the trend indicators, and QNH/QFE/QNE, and practise with real current reports from several aerodromes so the decoding becomes a habit rather than a memory test.
Navigation errors of the "plausible number" kind: applying magnetic variation with the wrong sign, using the wrong wind triangle convention (adding instead of subtracting drift), or computing heading, track, and ground speed without keeping the three quantities distinct in the working.
Variation and drift are sign-sensitive and candidates memorise a mnemonic without understanding the geometry. When the sign is wrong the answer is still one of the options, so the error is never caught.
What to do instead
Draw the wind triangle for every navigation question, label true track, wind, true heading, and drift, and only then convert true to magnetic with the stated variation and direction. Write the conversion rule on your scratch sheet at the start of the exam and apply it explicitly each time. Check the sign by asking whether the wind or variation should push you left or right.
Operational Procedures answers that ignore the document or authority hierarchy: quoting a company practice or a checklist habit where the question asks for the regulatory or manufacturer requirement, or mixing emergency drill memory items with the written procedure sequence.
Candidates rehearse drills by rote and absorb company culture, so the practised wording overrides the published source. They also do not distinguish memory items from reference items in the procedure.
What to do instead
For each operational topic (fuel planning, alternates, emergency descent, depressurisation, diversion, passenger/crew duties) identify the governing document and the exact requirement it states. Separate memory items from reference items on a two-column sheet and learn only the memory items verbatim. When a question cites a scenario, ask "which document decides this?" before reading the options.
Principles of Flight answers that describe what happens rather than why: stating that the aircraft stalls at a fixed speed regardless of weight and load factor, confusing the four forces in a climb with an imbalance, or mis-stating the relationship between angle of attack, critical angle, and stall.
The domain is taught with simplified statements ("stall speed is a fixed number") that are useful early and wrong later. Candidates keep the simplification and never replace it with the load-factor and weight dependence.
What to do instead
Rebuild the core relationships from first principles: lift equation, angle of attack versus pitch attitude, load factor and stall-speed change, thrust and drag in climb and descent. For each question, identify which variable is being changed and which relationship governs it. Test yourself by explaining out loud why the wrong options are wrong, not just why the right one is right.
Radiotelephony and Communications errors: transmitting readback in the wrong order or omitting the mandatory elements (callsign position, level, instruction readback), using non-standard phraseology, or failing to recognise when a readback is required at all. On Radio Navigation, confusing a radial with a bearing or a QDM with a QDR.
Phraseology is learned by listening to others, including non-standard transmissions, and candidates copy the fluent-sounding version rather than the standard one. Radial/bearing and QDM/QDR are visually similar and taught in the same lesson, so they blur together.
What to do instead
Write out the standard readback template for each phase (clearance, taxi, take-off, level, approach, landing) and rehearse it aloud until the element order is fixed. Learn the mandatory readback list explicitly. For radio navigation, draw the station, the aircraft, and the radial/bearing line for every question and label which quantity is measured from the station and which from the aircraft before choosing.