Part-66 Module 1 common mistakes
Part-66 Module 1 · Understand the traps and how to avoid them.
Applying a formula without converting all quantities to consistent SI units first (e.g. feeding kilonewtons into a stress calculation expecting newtons, or minutes into a speed/time problem expecting seconds).
The formula is memorised as a symbol string, so the candidate substitutes numbers as they appear in the question without checking the units attached to them.
What to do instead
Before substituting, write out every given quantity with its unit, convert each to the base unit the formula requires (N, m, s, Pa), then substitute. Do a unit check on the answer: if the result's units are not what was asked for, an unconverted value is the usual cause.
Treating a vector quantity as a scalar: adding forces or velocities arithmetically without resolving into components or accounting for direction.
Early arithmetic habits dominate, and the candidate sees two numbers and adds them rather than sketching the geometry.
What to do instead
For any problem involving forces, velocities or accelerations at an angle, draw a free-body or vector diagram before calculating, resolve into perpendicular components, and only then combine. Practise the resultant-of-two-perpendicular-vectors and inclined-plane cases until the diagram step is automatic.
Confusing series and parallel rules for resistance, capacitance and voltage/current division, and applying the wrong rule to the circuit shown.
The rules look symmetrical and are learned as paired formulas, so under time pressure the candidate recalls the correct family but the wrong member.
What to do instead
Anchor each rule to a physical statement rather than a formula: in series the same current flows through every element and voltages add; in parallel the same voltage appears across every element and currents add. Check the answer against those statements (e.g. total resistance in parallel must be less than the smallest branch).
Mixing up the characteristics and operating regions of the basic semiconductor devices: diode forward/reverse bias, transistor terminal functions (which terminal controls which), and the difference between a thyristor latching on and a transistor being continuously controlled.
The devices are studied as a list of symbols and facts without a working mental model of what carries the current and what controls it.
What to do instead
For each device, be able to state in one sentence what turns it on, what turns it off, and which way conventional current flows. Draw the symbol from memory and annotate each terminal with its function. Test yourself by predicting circuit behaviour, not by reciting device names.
Treating digital signals as continuous: misreading a logic truth table, confusing binary and decimal/hex conversions, or failing to distinguish an analogue quantity from its digitally converted representation (resolution, quantisation).
Candidates memorise gate names and conversion procedures but never build the habit of checking a result against the allowed values (0/1) or the stated word length.
What to do instead
Always state the number base and bit width when converting, and verify by converting back. For logic problems, complete the full truth table rather than reasoning in prose, and check that each output column contains only permitted logic levels.
Confusing similar-sounding material and hardware properties: strength versus stiffness versus hardness, fatigue versus creep, and identifying a fastener or fitting by appearance rather than by its stated function.
The vocabulary is dense and the terms are learned in clusters, so definitions blur together and are recalled by association rather than meaning.
What to do instead
Build a comparison table for each confusable set (what it measures, what test reveals it, typical failure it causes). For hardware, learn each item by the load it carries and the failure mode it prevents, then describe the item from that description alone.
Answering maintenance-practice questions from general workshop intuition rather than from the prescribed procedure: skipping torque/calibration/safety-factor reasoning, or choosing the 'practical' option that contradicts documented practice.
Hands-on experience or common sense produces a plausible answer that is not the regulated or specified one, and the candidate does not check which is being asked for.
What to do instead
For each question, identify whether it is asking for the specified procedure or for a physical explanation. Where a procedure is involved, recall the controlling requirement (calibration traceability, torque values from the manual, lockwiring direction, inspection interval) and choose the option consistent with it, even if another option seems more convenient.
Misapplying aerodynamic relationships: attributing lift or stall to the wrong variable, confusing angle of attack with pitch attitude, or mixing up the four forces and their balance in climb, descent and turn.
The relationships are learned as slogans ('lift depends on speed') without the underlying proportionality, so direction and magnitude of the effect are guessed.
What to do instead
Learn lift as proportional to density, wing area, lift coefficient and the square of speed, and be able to say what happens to each term in a given manoeuvre. Separate angle of attack (wing to relative airflow) from pitch attitude (nose to horizon) with a sketch, and always resolve the four forces for the stated flight condition.
Answering human-factors questions with the 'obvious' behavioural answer instead of the recognised error model: misclassifying a slip as a mistake, or attributing an outcome to attitude when the question concerns a systemic or perceptual factor.
Human factors reads like everyday psychology, so candidates rely on intuition and never fix the technical distinctions between error types, perceptual limitations and organisational factors.
What to do instead
Learn the error taxonomy with one concrete aviation example each (skill-based slip/lapse, rule-based and knowledge-based mistake, violation), plus the sensory-illusion and fatigue/stress effects by name. For each question, first label the error or factor category, then select the option that matches that label.
Confusing the roles and scope of the regulatory bodies and documents: mixing up which organisation makes which rule, what a licence category or rating permits, or which document contains a given requirement.
Legislation is learned as a list of acronyms and document titles without a map of who does what and which instrument controls which activity.
What to do instead
Build a one-page map: organisation to function, document to subject matter, licence/rating to privileges. For each question, identify the actor (who) and the instrument (which document) before looking at the options, and eliminate any option that assigns a function to the wrong body.