AAK ATPL (Kazakhstan) common mistakes
AAK ATPL (Kazakhstan) · Understand the traps and how to avoid them.
Answering regulatory questions from company SOP habit or from generic ICAO defaults instead of from the regulation actually named in the stem - for example quoting a duty-limit or document-carriage rule that comes from an operator manual rather than the applicable air law.
Most candidates prepare inside one operator's environment, where the manual is a condensed, local version of the rule. The manual is easier to remember than the source text, so recall defaults to it even when the question asks about the underlying requirement or about a Kazakhstan-specific variation.
What to do instead
Build a one-page 'rule source map': for each Air Law topic (licensing, documents, minima, duty and rest, rules of the air, accident reporting) write which instrument actually governs it and one distinguishing detail. When a stem names a regulation, answer only from that layer; treat SOP knowledge as a distractor.
Computing the centre of gravity correctly in linear units but converting to %MAC with the wrong datum, or mixing station arms given in inches with a chart scaled in metres, and then accepting an answer that falls outside the envelope.
The arithmetic is easy, so candidates rush it and treat the unit conversion and the %MAC formula as an afterthought. Chart axes are often in different units from the data table, and the leading-edge reference is stated once in the header and then ignored.
What to do instead
Standardise a written routine: list every mass with its arm and moment, state the units on each line, sum, divide, then convert with the explicit formula (CG% = (CG - LE) / MAC x 100) writing the datum value down. Finish every calculation by plotting the result on the envelope - a sane-looking number outside the envelope is a warning, not an answer.
Reading take-off or landing distance straight off the chart for the aerodrome elevation without correcting for pressure altitude, temperature above or below ISA, wind, slope and runway surface, then choosing the first plausible figure.
The chart looks like a single-entry graph and the correction tables are on a separate page. Candidates under time pressure skip the second stage, especially at high-elevation Central Asian airfields where the correction is largest and most easily forgotten.
What to do instead
Practise every performance question through a fixed four-step template: field conditions to pressure altitude, pressure altitude and temperature to base distance, apply wind/slope/surface factors in the prescribed order and direction, then compare with the limiting mass (field length, climb, obstacle, tyre, brake). Write the intermediate values in the margin so a missed stage is visible.
Planning fuel as trip fuel plus a token margin, omitting taxi, contingency, alternate and final reserve, or mixing units - kg against litres, imperial against US gallons, specific consumption per hour against per kilometre.
Fuel questions combine a narrative with a table, and candidates latch onto the largest number (trip fuel) as 'the answer'. Unit traps are invisible when both numbers look reasonable, and density is often given but not applied.
What to do instead
Always build the fuel log in the same order the regulation requires (taxi, trip, contingency, alternate, final reserve, extra, total) and total it before touching the options. Convert every quantity to one unit at the top of the working and annotate the conversion factor; if a density is given, use it explicitly rather than assuming 0.72.
Naming a model or threshold from memory without applying it - for example stating a hypoxia onset altitude, or labelling a scenario as somatogravic illusion when the described cues are somatogyral, or confusing hyperventilation with hypoxia.
Human performance is learned as vocabulary lists that feel familiar, so recognition substitutes for discrimination. The two conditions share dizziness, tingling and a sense of unreality, and the exam deliberately describes the shared symptoms before revealing the distinguishing cue.
What to do instead
For each phenomenon memorise one discriminator, not the name: hypoxia responds to oxygen and worsens with altitude; hyperventilation improves with slowed breathing and does not respond to oxygen alone; somatogravic illusion is a false pitch in linear acceleration, somatogyral a false turn in rotation. Rehearse by classifying short scenarios into the discriminator before naming the condition.
Misreading a coded report or forecast - treating a trend group as a temporary fluctuation, reading QNH as QFE, treating CAVOK as merely 'good visibility', or taking the first visibility figure in a METAR when a later group is the prevailing value.
Coded weather is decoded quickly by pattern, and candidates who 'know the code' stop reading left to right. The change groups (BECMG, TEMPO, trend) and the position of the visibility group are exactly where speed produces errors.
What to do instead
Decode in strict field order using a written skeleton, and mark each item as prevailing, temporary or forecast. Explicitly state in the working what QNH and QFE would each give for the aerodrome in the stem, and convert CAVOK into its full meaning (visibility 10 km or more, no cloud below 5000 ft or MSA, no significant weather) every time.
Applying variation and deviation in the wrong direction, or solving the drift triangle with heading and track swapped, producing a heading that is internally consistent but wrong by twice the drift.
The mnemonic for east/west is easy to recall in one direction and easy to invert under pressure, and the wind triangle is usually drawn hastily with the wind vector at the wrong end. Candidates then check only the arithmetic, not the geometry.
What to do instead
Draw the triangle every time with a fixed convention (true track and TAS from the start point, wind vector from the end of the track line), measure drift from the diagram, and only then apply variation and deviation using a written 'variation east, magnetic least' reminder. Sanity-check the final heading: with a wind from the left, heading must be left of track.
Confusing radial with bearing and inbound with outbound when working a VOR/NDB intercept, mis-setting the OBS to give reverse sensing, or treating DME distance as ground distance when the aircraft is high and close to the station.
The instruments are taught with a picture, and without the picture the words radial, bearing and course collapse into each other. Slant-range error is invisible on the indicator, so the number looks authoritative.
What to do instead
Adopt a single rule set and rehearse it aloud: a radial is always from the station, a bearing is always to or from the aircraft as stated, and set the OBS to the course you intend to fly so the CDI sense is always normal. For DME, remember the error is largest at high altitude and short range, and correct only when the stem's numbers make it material.
Mixing memory items with reference items, or applying a procedure belonging to a different aircraft type or a different phase, and answering an emergency scenario with checklist recall rather than with a priority sequence.
Procedures are learned by drilling the checklist document, and the candidate remembers the content but not the status of each item or the applicability. Scenario stems then trigger the nearest familiar checklist instead of the correct first action.
What to do instead
Maintain a two-column table per aircraft type separating immediate-action memory items from items to be read and done. When answering a scenario, state the priority framework first (aviate, navigate, communicate, manage the situation), then select the procedure by aircraft and phase, then say whether the first items are memory or reference.
Treating induced drag as increasing with speed in the cruise, or quoting a fixed stall speed without applying the load-factor relationship, so that a question about accelerated stall or about the speed for minimum drag is answered from a memorised sentence.
The four-force diagram is learned as a shape and the drag curves as a picture; the exam then asks about a point on the curve in words, and the picture is recalled without its axes. Load-factor questions are missed because the square-root relationship is remembered as linear.
What to do instead
Redraw the drag curve from first principles whenever the question involves drag: induced drag falls with speed squared, parasite drag rises with speed squared, total drag minimum at the intersection. For stalls, always write the relationship (stall speed varies with the square root of load factor) and compute the new value before reading the options.