
The Dirty Dozen are the 12 error preconditions that make mistakes more likely during maintenance. Countermeasure lists exist everywhere. Running them day-to-day in a real shop is what separates compliance from control.
This article provides a matrix mapping each factor to prevention controls and audit evidence. You'll also get a workflow playbook for shift turnover, task execution, and discrepancy closure.

The Dirty Dozen is a set of 12 human error preconditions. Gordon Dupont identified them in 1993. He developed them while building Transport Canada’s Human Performance in Maintenance training program.
These conditions increase the chance of a maintenance error. Errors can happen during task execution, shift handover, inspection, or sign-off. Dupont wanted a shared set of terms. and for crews to talk about why mistakes happen in a clear way. He also wanted teams to spot warning signs early.
Three decades later, FAA, EASA, and ICAO human-factors curricula still use the framework. Many Directors of Maintenance (DOMs) used to treat human-factors training as optional. Audit expectations have changed. FAA guidance now pushes for documented mitigations that hold up during an audit.
NTSB 2025 findings on the Alaska Airlines 1282 door-plug event pointed to gaps in training, guidance, and oversight. Several of those gaps map directly to Dirty Dozen factors.
A shared vocabulary helps. Documented and repeatable controls matter more. Training without controls becomes a classroom exercise. Controls turn training into real risk reduction.
Effective countermeasures to the dirty dozen human factors fall into four lanes:
One lane alone rarely works. Training can help with complacency. Complacency returns fast without a process or tool that backs it up.
Use the matrix below to anchor your next safety meeting or prepare for an internal audit.

The same 12 factors affect each department in different ways. Each team needs to see the Dirty Dozen aviation framework in daily work. A generic poster will not change behavior.
Lack of resources, pressure, and lack of communication show up the most.
Missing parts or thin staffing create workarounds. Teams start jobs without what they need. Task cards get compressed to meet a dispatch window. Shortcuts become tempting. Incomplete instructions create confusion. Missing engineering orders leave mechanics guessing.
They face complacency and norms most acutely.
Repetitive inspections on the same fleet type breed assumptions. Deviations from approved data become invisible when they've been accepted for years.
Lack of resources and lack of awareness show up the most.
Missing parts can stop work or trigger last-minute purchases. Expired shelf-life items can sit on a rack unnoticed. Teams can lose track of reservations. Reserved components may get issued to the wrong job.
This team primarily contends with lack of communication and fatigue.
Unclear pilot-reported discrepancies slow troubleshooting. Illegible write-ups create delays. Maintenance teams may guess at symptoms. Fatigue can also reduce detail in reporting and handoffs.

Here’s a breakdown of each of the dirty dozen human factors in aircraft maintenance, the countermeasures that address it, and the records to keep as proof.
When information fails to move accurately between people, shifts, or departments, the person who needs it most never gets it.
Countermeasures:
What to document:
Over-familiarity with a routine task erodes vigilance. The mechanic stops verifying and starts assuming.
Countermeasures:
What to document:
When staffing, parts, tools, technical data, or time fall short, the task doesn't get done correctly.
Countermeasures:
What to document:
With a projected 10% shortfall in certificated mechanics for 2025, per ATEC, resource-gating is more critical now than ever.
A break in focus during a task, like a radio call, means the mechanic resumes at the wrong step or skips one entirely.
Countermeasures:
What to document:
Acute or chronic stress—from Aircraft on Ground (AOG) pressure, overtime, or personal circumstances—narrows focus and degrades decision-making.
Countermeasures:
What to document:
Also, maintain access to employee assistance resources.
When two techs work opposite sides of the same system without coordinating, steps get duplicated or missed.
Countermeasures:
What to document:
Schedule demands that conflict with procedural requirements create conditions for shortcuts. If dispatch needs the aircraft released before an inspection step is complete, someone must be empowered to say no.
Countermeasures:
What to document:
A tech unfamiliar with a new fleet type misses a unique inspection access point. Or a crew doesn't know about concurrent fuel operations nearby.
Countermeasures:
What to document:
Assigning a task beyond a mechanic's demonstrated proficiency—or working from an outdated Aircraft Maintenance Manual (AMM) revision—sets the stage for procedural errors.
Countermeasures:
What to document:
Overwork without adequate rest breaks leads to poor judgment and avoidable mistakes.
Countermeasures:
What to document:
When "the way we've always done it" overrides the current revision of approved maintenance data, an unauthorized practice becomes invisible.
Countermeasures:
What to document:
A fear of reprisal or conflict can block raising a critical concern. For example, a junior tech spots a discrepancy but stays quiet because the lead already signed it off.
Countermeasures:
What to document:
Listing these factors and their countermeasures is table stakes. Enforcement through repeatable workflows every shift, not just during training week, separates functional programs from posters.

Embed controls at workflow points to catch and correct each human factor.
Verbal-only handoffs are where communication errors breed. A written turnover log—signed by both outgoing and incoming leads—should capture the items below. If an open item doesn't carry both signatures, treat it as unresolved.
During task execution, build mandatory stop points into task cards wherever a second set of eyes is needed. When a mechanic gets pulled away mid-task, a return-to-task protocol requires backing up at least three steps before continuing.
With US airline maintenance costs averaging $18.30 per block minute in 2024, per Airlines for America, even one rework event from a missed step carries a real dollar figure.
Independent inspections require a qualified inspector who didn't perform the work. The inspector's stamp, employee number, and timestamp must appear on the task card or digital sign-off record. No exceptions.
Every discrepancy follows a closed loop:
Each transition demands a sign-off and a timestamp. If any step is missing, the discrepancy stays open.
Operators who centralize work orders, discrepancies, and inspection steps in a single aviation maintenance management system reduce the risk of items falling off between disconnected tools or spreadsheets.
No task card opens until parts, tools, and current tech data are confirmed and reserved against that specific work order. This is a hard gate.
Stores confirms availability and attaches trace documentation to the work order before the mechanic begins. If parts are delayed, the task stays in planning.
SOMA Aircraft Document Management module brings those prevention controls into a single audit-ready system. Work orders, discrepancies, inspection sign-offs, and parts readiness all live in one place.
The mitigations in your matrix become repeatable daily workflows instead of laminated posters. That means fewer last-minute scrambles before inspections, and cleaner proof that work was controlled. Evidence is traceable across shifts, departments, and aircraft.
Ready to close the gap? Get a quote to connect your controls matrix to your daily maintenance execution.
Yes. Present the matrix as your hazard-mitigation map. Then show that the controls in each cell exist as traceable artifacts in your maintenance system. Auditors expect to see the link between identified hazards, mitigations, and evidence.
Prioritize the factors that map to your highest operational risks. Build those controls first. Document the risk-acceptance rationale for deferred mitigations in your SMS or QA manual.