EASA Module 8 common mistakes
EASA Module 8 · Understand the traps and how to avoid them.
Classifying every unintended outcome as a 'mistake' - e.g. calling a technician who picks up the wrong torque wrench a 'mistake' instead of a slip, or calling a skipped step in a procedure a 'mistake' instead of a lapse.
The three terms are taught together and all sound like synonyms in everyday speech; candidates remember 'mistake' as the generic word and never anchor it to the intention/execution distinction.
What to do instead
Decide in two steps: (1) was the intention correct? If no → mistake (rule-based or knowledge-based). (2) If yes, was the action carried out as intended? Wrong action executed → slip; action omitted / forgotten → lapse. Practise with 10 short scenarios until the decision tree is automatic.
Labeling a deliberate shortcut (e.g. signing off a check without doing it, or not using a torque wrench because 'it's always fine') as an error, or treating all violations as deliberate sabotage.
Error models taught earlier (Reason) put violations alongside errors in one diagram, so candidates merge them; they also miss that most violations are routine, socially accepted and non-malicious.
What to do instead
Use the intention test: unintended deviation from intended action or plan = error; deliberate deviation from a rule/procedure = violation. Then sub-classify violations as routine (normalised by the group), situational (time/access pressure) or exceptional (rare, high-stakes). If the stem says 'to save time' or 'everyone does it', the answer is a violation, not an error.
Treating peer pressure, company production pressure and 'bad safety culture' as interchangeable, or selecting 'peer pressure' whenever a group appears anywhere in the stem.
All three involve other people influencing behaviour, so the labels blur; stems deliberately describe, for example, a supervisor pushing a deadline, which is not peer pressure at all.
What to do instead
Identify who holds the influence: equals/workmates wanting you to conform → peer pressure; a person with formal authority, targets or job security influence → management/supervision pressure; shared, embedded beliefs ('we always do it this way, no one gets hurt') across the whole organisation → culture/norms. Match the source of influence in the stem, not just the presence of a group.
Drawing the arousal–performance curve as a straight line or a U-shape (performance improving steadily with stress, or worst at medium stress) instead of an inverted U, and using 'stress' and 'fatigue' as synonyms.
Everyday language says stress is bad and harder effort is better; the inverted U looks counter-intuitive and is easily inverted under exam time pressure. Fatigue and stress share visible symptoms (irritability, poor concentration).
What to do instead
Memorise one picture: low arousal = boredom/underload, moderate = optimum performance, high = anxiety, narrowed attention and errors - an inverted U. Then separate the concepts: stress is a response to a perceived demand exceeding capability (short-term, situational); fatigue is a cumulative decrement from prolonged effort, lack of sleep or sustained workload that persists after the stressor goes.
Assuming a night-shift worker fully adapts within a few days, that caffeine or willpower solves night-shift fatigue, and picking midday rather than the small hours as the circadian low point.
Candidates reason from personal experience of 'getting used to' late nights and underestimate how slowly circadian rhythm shifts (roughly an hour a day at best, and usually not at all on rotating rosters).
What to do instead
Anchor the facts: circadian adaptation is slow and often incomplete, especially on rapidly rotating shifts; the body's low points are approximately 0300–0500 and 1500–1700 - hence the early-hours error peak. Caffeine and stimulants mask rather than remove fatigue. Countermeasures with evidence: strategic napping, controlled rest, bright light at the right time, and rostering forward rotation (day → afternoon → night).
Accepting verbal handover as sufficient for a task that continues across a shift, or agreeing that a defect 'can be sorted by the next shift' without any written record.
In the hangar handover feels complete when the departing technician explains it face to face; candidates transfer that informal experience into the exam and forget the formal recording requirement.
What to do instead
Apply the rule: anything that affects airworthiness, anything incomplete, and anything a following shift needs must be recorded in writing in the appropriate document (logbook, work pack, NCR, shift handover sheet), signed and dated. Verbal briefing supplements but never replaces the written record. If a stem offers 'tell the next shift verbally' as the corrective action, it is almost always the wrong option.
Assuming colour vision and fine-detail vision remain reliable in dim hangar or night lighting, or that the eyes adapt to darkness in 'a minute or two'.
Candidates recall that 'rods are for night vision' but not the consequence - that the fovea (where detail and colour are resolved) is rod-poor, so staring directly at a dim object makes it vanish. Dark adaptation is also intuitively fast.
What to do instead
Fix the two facts and their practical consequences: cones are concentrated in the fovea and handle colour and detail but need good light; rods dominate peripherally, are colour-blind and need 20–30 minutes for full dark adaptation (hence 'look slightly to one side' of a dim object). Colour-coded warnings, wires and placards cannot be trusted in low light - use adequate task lighting instead.
Answering noise questions as if the only risk is hearing damage, and treating a 3 dB increase as 'slightly louder' rather than a doubling of sound energy.
Hearing damage is the headline hazard, and the decibel scale is not intuitive because it is logarithmic - everyday loudness perception is roughly linear.
What to do instead
Learn both halves: (1) noise also degrades communication, causes annoyance, raises arousal and increases error rates well below damage thresholds; (2) because dB is logarithmic, +3 dB = double the energy (halved permissible exposure time) and +10 dB ≈ double perceived loudness. Anchor on the exposure limit: 85 dB(A) over an 8-hour day, with exposure time halved for each 3 dB rise.
Assuming a trained inspector looking at a component will reliably find a defect, or choosing 'tell the inspector to concentrate harder' as the fix for missed defects in repetitive inspection work.
Inspection feels like a simple perceptual act; candidates do not know the vigilance decrement, and 'try harder' is a plausible-sounding remedy that shifts blame to the individual.
What to do instead
Treat inspection as a vigilance task subject to a measurable decrement in detection over time, worse in low light, high noise, monotony, and with no feedback. The effective fixes are systemic: limit inspection periods, rotate tasks, provide adequate illumination and magnification, use checklists, reference standards and multiple independent inspectors, and provide feedback on results. 'Concentrate harder' and 'be more careful' are never the correct answer.
Choosing 'tell the technician to be more careful', 'wear PPE' or 'put up a warning sign' as the primary control for a hazard, and treating hazard/error reporting as optional or as something that gets the reporter into trouble.
These feel like active, cheap, visible actions and are the everyday response in many workplaces; reporting is also widely (and wrongly) associated with blame.
What to do instead
Apply the hierarchy of control in order: eliminate the hazard, substitute, engineer it out (guard, interlock, ventilation), then administrative controls (procedures, training, rotation), with PPE last as a backstop. For reporting, memorise the purpose: a confidential, non-punitive reporting system exists to feed the organisation's safety data and prevent recurrence - failure to report removes the barrier and makes the next occurrence more likely, so a stem where the technician 'says nothing to avoid trouble' is always the wrong choice.