Iran CAO PPL Theory common mistakes
Iran CAO PPL Theory · Understand the traps and how to avoid them.
Applying the standard 1:60 descent-gradient rule and the usual 3-degree slope figures to Iranian terminal procedures without checking the published descent angle and the actual threshold elevation, then computing a top-of-descent point that is late by several miles.
Candidates memorise a single rule-of-thumb from training material and never re-derive it for each procedure; Iranian plates often publish non-standard angles, high threshold elevations, and step-down fixes, so the memorised figure silently produces wrong numbers.
What to do instead
For every descent question, first extract the published angle, the fix altitudes, and the threshold elevation from the stated data, then compute the required rate (groundspeed x gradient) or the distance (height difference / tan angle). Practise at least ten mixed-angle calculations so the formula, not the memorised constant, becomes automatic.
Treating the altimeter subscale setting as a formality: setting QNH where QFE is required (or the reverse) during approach and circuit work, and failing to apply the correct transition altitude/level logic when climbing or descending.
The QNH/QFE distinction is taught early and assumed known, so candidates skim questions and answer from habit; in Iranian airspace the transition altitude is fixed by AIP and the regional pressure is often high, so a wrong subscale gives a large, exam-relevant altitude error.
What to do instead
Build a one-page decision table: below transition altitude use QNH (or QFE if the operator/procedure specifies), above transition level use standard 1013.25 hPa, and always state which reference the question is asking about. Redo every altimeter question by writing the subscale and the reference datum before choosing an answer.
Mixing up magnetic and true directions when applying wind correction, drift, and heading calculations, and forgetting to apply variation and deviation in the correct order.
Candidates learn the mnemonic but apply it in the wrong sequence under time pressure, and Iranian charts use large easterly variation in some regions, so a sign error produces an answer that is plausible but wrong.
What to do instead
Use a fixed written sequence every time: true course, apply wind to get true heading, add easterly/subtract westerly variation to get magnetic heading, then apply deviation for compass heading. Show the intermediate values in the working so a sign error is visible before selecting an answer.
Answering radiotelephony questions with conversational phrasing instead of the prescribed ICAO phraseology, omitting the aircraft call sign on readback, and failing to read back mandatory items such as runway, clearance limit, altimeter setting, and heading.
Candidates translate from everyday English or from their native-language radio habits, and they underestimate how strictly the examiner marks readback content; phraseology is memorised as vocabulary rather than as a complete exchange.
What to do instead
Practise full exchanges aloud, not isolated words: clearance delivery, taxi, line-up, take-off, approach, and landing, each with complete readback of the mandatory items. Compare your readback against the ICAO standard phraseology list item by item until every mandatory element is present.
Confusing the units and reference conditions in performance questions: quoting take-off distance without stating whether it is to 50 ft or ground roll, using the wrong pressure altitude, or ignoring the effect of runway slope and surface.
Performance charts are dense and candidates grab the first number that looks close, skipping the chart's stated conditions; they also mix units (feet versus metres, knots versus km/h) because Iranian documentation and aircraft manuals use both.
What to do instead
Before reading any chart, write down the four inputs (pressure altitude, temperature, mass, runway condition) and the output definition required by the question. Convert all units to one system first, then interpolate and state the result with its definition. Do a sanity check that the answer moves in the expected direction when one input changes.
Treating mass and balance as a single centre-of-gravity check and forgetting to verify that the zero-fuel mass and the forward and aft limits are all satisfied after loading, or forgetting that fuel burn moves the centre of gravity.
Candidates compute one total moment and stop, because the arithmetic feels complete; they also forget the empty-mass moment arm is given in the manual and must be added, not assumed.
What to do instead
Use a fixed table with columns for mass, arm, and moment for every item, sum them, then plot the result on the envelope and check both limits plus the zero-fuel case. Repeat with fuel burned off to confirm the centre of gravity stays inside the envelope throughout the flight.
Answering human-performance questions from personal intuition about stress, fatigue, and hypoxia rather than from the stated physiological facts, and confusing the symptoms and timescales of hypoxia with those of hyperventilation and carbon monoxide poisoning.
These topics feel like common sense, so candidates do not revise the specific numbers and symptom lists; the symptoms genuinely overlap, which makes an intuitive answer feel correct.
What to do instead
Learn a comparison table: time of useful consciousness at given altitudes, hypoxia symptoms versus hyperventilation symptoms versus carbon monoxide signs, and the recovery action for each. Test yourself by writing the distinguishing feature before looking at any options.
Applying the wrong stability or control relationship in principles-of-flight questions, for example assuming a forward centre of gravity improves stability, or mixing the effects of flaps on the stall speed, the approach path, and the pitch change.
The individual effects are learned separately and never integrated, so a question that combines two of them (flaps plus centre of gravity, or thrust plus angle of attack) defeats a one-fact answer.
What to do instead
Draw a cause-and-effect chain for each configuration change: what happens to lift, drag, pitching moment, stall speed, and static stability, in that order. Answer combined questions by walking the chain rather than recalling a single fact.
Misreading meteorological reports and forecasts: decoding a METAR or TAF group in the wrong order, missing the meaning of a trend group, or confusing the coverage and height conventions in cloud and wind groups.
Candidates memorise the group order but not the exceptions, and Iranian reports frequently include regional coding and non-standard remarks; time pressure in the exam encourages skimming past the trend and remarks sections.
What to do instead
Decode a full METAR and TAF from scratch every day for two weeks, writing each group's meaning in plain language, including trend, wind variation, and remarks. Then answer exam-style questions only after the full decode is written out.
Confusing radio-navigation and GNSS concepts: mixing the indications of a localiser and a glide slope, treating a GPS approach as precision, or misstating what RAIM and the integrity monitoring actually guarantee.
The underlying signals are invisible and candidates learn the definitions verbally without a mental picture, so closely related terms collapse into one another; GNSS questions are also newer than the rest of the syllabus and get less revision time.
What to do instead
For each aid, write what the cockpit indicator shows for on-course, fly-left/fly-right, and fly-up/fly-down, plus what happens when the signal is lost. For GNSS, state explicitly the difference between accuracy, integrity, and availability, and which approach types require which. Sketch the ground station layout for each aid.