Sofema Aviation Services (SAS) looks at the implications of Latent & Active Failures related to MEDA Investigations.
Definitions (simplified)
- Active Failures: Front-line deviations that directly precede the event-slips, lapses, mistakes, or rule violations at the point of work (e.g., step omitted, wrong torque, cross-mated connector).
- Latent Conditions: Hidden system weaknesses that sit in the background until they combine with other factors-e.g., unclear task cards, missing tools, time pressure, poor lighting, weak handover, unrealistic plans, confusing interfaces, counterproductive KPIs.
Think of active failures as the visible spark; latent conditions are the dry tinder and wind that make a fire inevitable.
Why MEDA Emphasises Latent Conditions
- Predictive Value: Latent conditions repeat across tasks, fleets, and shifts; fix one and reduce multiple event types.
- Fairness & Learning: Focusing only on the last human action invites blame and misses deeper levers (design, planning, resources, culture).
- Action Quality: Latent-condition fixes usually change a barrier (better task card, kit-complete gate, staffing rule) rather than defaulting to “retrain the tech.”
Typical Latent Conditions in Maintenance (With Signals)
- Information Quality (task cards, AMM/CMM, EO/STC)
- Signals: frequent step queries, tiny diagrams, recurring misinterpretations.
- Planning & Kitting
- Signals: “tool not available,” missing O-rings, late task starts near shift end.
- Work Environment & Access
- Signals: repeat errors on night shifts, cramped bays, glare on ramp.
- Human–Machine Interface
- Signals: look-alike parts, similar connectors, buried torque notes.
- Supervision & Coordination
- Signals: “I thought they checked it,” parallel jobs interference, thin buy-backs.
- Organisational Pressures & KPIs
- Signals: on-time release prioritised over check completeness; normalised shortcuts.
- Competence & Recency
- Signals: seldom performed tasks with higher rework; no targeted brief.
How Active Failures Present (& How Latent Conditions Set Them Up)
- Slip/Lapse (unintentional): Omission of a safety wire.
- Latent setup: cramped access + poor lighting + step buried on page 3.
- Mistake (unintentional but wrong rule applied): Wrong fluid.
- Latent setup: similar packaging + ambiguous label + rushed plan.
- Violation (intentional deviation): Skipping an independent check.
- Latent setup: normalised local practice + inspector unavailable + KPI pressure.
Turning Findings Into SMS Practice
Risk Management
- Convert latent conditions into named hazards (“ambiguous torque call-outs on ATA 27 tasks”; “critical tool non-availability”).
- Rate likelihood/severity; select barrier-level controls (e.g., kit-complete gate, second-person verification only on named critical steps).
Safety Assurance
- Track barrier health metrics that reflect latent conditions:
- % work packages launched kit-complete
- Tool availability rate for critical tools
- % critical buy-backs completed on time
- Task card change lead-time and defect rate post-change
- Repeat-event rate (30/90 days)
- Verify the effectiveness of actions through spot checks and targeted reliability signals.
Safety Promotion
- Share anonymised case stories that show the chain: latent conditions → active failure → barrier change → measurable improvement.
- Use toolbox talks to reinforce early signals (“If you hit a missing-kit item, stop and trigger the kit-complete gate.”).
Next Steps
Sofema Aviation Services and Sofema Online delivers Maintenance Error Management System (MEMS) and Maintenance Event Decision Aid (MEDA) training as Classroom, Webinar and Online training. For details please see our websites or email [email protected].
Tags:
MEDA, SAS blog, SafetyManagementSystem, AviationSafety, HumanFactors, AviationMaintenance, MaintenanceErrorManagement, LatentConditions, ActiveFailures, AircraftMaintenanceTraining
