CAAB CPL Theory Exam common mistakes
CAAB CPL Theory Exam · Understand the traps and how to avoid them.
Quoting air-law numbers (VFR visibility and cloud-clearance minima, fuel/endurance reserves, licence and medical validity periods, recent-experience windows) from vague memory instead of from the defined figure, and picking whichever option 'sounds about right'.
Air law is studied as reading rather than as data. Numbers feel familiar after one pass, so candidates never test themselves on them in isolation, and similar-looking values (e.g. 30/60/90-day and 12/24-month rules) blend together under exam pressure.
What to do instead
Build a single one-page numbers sheet (limit, unit, source reference) covering the syllabus. Cover the right-hand column and recite the figures weekly, then do closed-book numeric-only drills until each figure is reproduced with its unit and condition (day/night, single/multi-crew) without hesitation.
Describing a system's behaviour from the label rather than from its control logic – for example assuming a constant-speed propeller overspeeds when power is reduced, or misidentifying which bus feeds an essential item after a generator failure.
Systems are memorised as names and diagrams, not as cause-and-effect chains. Without a mental model of what drives what, candidates reason by analogy with car or simple electrical systems and get the direction of the effect backwards.
What to do instead
For each system, draw the block diagram from blank paper and annotate it with 'if this fails, then...' arrows. Practise failure scenarios verbally: state the indication, the immediate effect, and the resulting limitation, then check each against the approved description.
Entering a performance chart with field elevation or QNH where pressure altitude is required, forgetting the temperature correction, and then reading the graph to a spurious precision without interpolating between the two nearest curves.
The chart is visually simple, so candidates skip the four-step setup and jump straight to the graph. Mixed units (feet/metres, hPa/inHg, kg/lb, litres/imperial gallons) also creep in when converting aerodrome data to chart units.
What to do instead
Always write the four lines first: pressure altitude, temperature (and deviation from ISA), weight, then chart entry. Interpolate explicitly between the bracketing curves, and finish with a sanity check (e.g. does the take-off run plausibly exceed the landing run at the same weight in still air?). Convert units as a separate, written step.
Computing a mass and balance total without adding crew, unusable fuel, oil, and any optional equipment, or reading the final point against the envelope without checking both the forward and aft limits at the actual take-off mass.
The arithmetic dominates attention, so the item list is abbreviated 'to save time', and the envelope is only checked roughly in the middle where almost anything looks legal.
What to do instead
Use a fixed rows template (empty/basic mass, crew, pax, baggage, fuel, oil, extras) and total it twice. Plot the point and then check it against the envelope boundary at that exact mass, not at maximum mass. Finish by computing the maximum permissible traffic load or fuel margin so the answer is verified by a second route.
Mixing hypoxia symptoms with hyperventilation, or confusing somatogravic and somatosensory illusions with the leans, and answering from the most dramatic-sounding symptom rather than the distinguishing one.
The presentations genuinely overlap (dizziness, tingling, euphoria), and candidates study each condition separately instead of side by side, so the discriminating feature is never isolated.
What to do instead
Build contrast tables of paired conditions with three columns: shared signs, distinguishing sign, correct response. Rehearse the in-flight recovery actions for each, and mark questions by finding the discriminator (e.g. cyanosis and response to 100% oxygen versus recovery from slowed breathing) before looking at the options.
Misreading coded reports – treating a TAF validity period or a BECMG/TEMPO group as applying to the whole forecast, confusing QNH with QFE in a METAR, or overlooking a significant weather group buried at the end of the report.
Reports are decoded by scanning for familiar groups and skipping the rest. The time groups and the trailing weather/trend elements are the least practised and the easiest to skim past.
What to do instead
Decode a fresh METAR and TAF every day in fixed order, announcing each element in words including validity and change groups, and finish by stating the practical effect on the planned flight. Practise with deliberately awkward examples containing BECMG, TEMPO, PROB and a late significant-weather group.
Applying magnetic variation with the wrong sign, forgetting deviation in the compass-to-magnetic step, or getting the drift correction sign backwards so the heading is corrected away from the required track.
The true/magnetic/compass chain has several sign conventions, and candidates try to hold them in working memory while doing the arithmetic. Mnemonics are remembered but their direction is not verified.
What to do instead
Adopt one written convention ('variation east, magnetic least') and use it identically every time on paper. Sketch the wind triangle to check drift direction, and apply the deviation card as an explicit last step. Verify by asking whether the final heading is on the expected side of track.
Reciting emergency memory items in the wrong order or inserting checklist items that belong to a later stage, and choosing an option that addresses the symptom before securing the aircraft state.
Emergency procedures are learned as a list of actions rather than as priorities (fly, navigate, communicate; then diagnose). Under exam conditions the most alarming symptom attracts the answer.
What to do instead
Drill each memory sequence as a physical flow with the priority framework stated aloud first. Practise teach-back: explain to someone else why each action comes where it does, and be able to say what would go wrong if the order were reversed.
Asserting that induced drag rises with increasing speed, or that stall speed is unaffected by weight, bank angle or load factor – answering from remembered slogans rather than from the relationships.
Drag curves and the stall-speed relationship are learned as pictures with arrows, and the accompanying formula is never connected to the graph, so the direction of each effect is guessed when the picture is not reproduced in the exam.
What to do instead
For every relationship, write the governing expression and derive the trend from it (total drag as the sum of a falling induced term and a rising parasite term; stall speed proportional to the square root of load factor). Then predict the answer from the formula before looking at the options.
Omitting or abbreviating readback items (altitude, heading, speed, frequency, clearance limit), using 'take-off' outside an actual take-off clearance, and producing position reports with the elements in the wrong order.
Radiotelephony is remembered as natural English rather than as prescribed phraseology, and readbacks are treated as a courtesy confirmation instead of a required, complete exchange. Candidates also never practise speaking it aloud, so the gaps only appear when the words must be produced.
What to do instead
Write standard templates for readback, position report, and distress/urgency calls, and practise them aloud with a partner at speaking pace, deliberately including the mandatory readback items every time. Record yourself and check each transmission against the required element list.