When an authority inspector reviews your corrective action plan and asks, "What root cause does this action address?" — can your team answer confidently?
For many Part-145 and Part-CAMO organisations, the honest answer is no. Root cause analysis in aviation maintenance remains one of the most misunderstood and poorly executed compliance obligations. Findings get closed with "retrain the engineer." Non-conformities recur quarter after quarter. Authority auditors raise the same Level 2 findings because the underlying systemic issues were never identified — let alone fixed.
This guide explains what effective root cause analysis actually requires in an EASA-regulated maintenance environment, when it is legally mandated, which tools work best for different situations, and why most organisations get it wrong.
What Is Root Cause Analysis — and Why Treating Symptoms Is Never Enough
Root cause analysis (RCA) is a disciplined, systematic process to identify the fundamental source of a problem so that the problem is permanently eliminated through process improvement. It traces an event to its origins — identifying what happened, how it happened, and why it happened — so that effective corrective action can be taken.
Think of it this way: painkillers treat a broken wrist's pain, but they do not heal the bone. RCA is the treatment that heals the cause, not the drug that masks the symptom.
The core principle is straightforward: if the fix does not stop the problem from happening again, you have not found the root cause.
RCA is fundamentally a reactive tool — it analyses what has already occurred. But the intelligence it generates enables proactive improvement. An organisation that feeds its RCA findings systematically into safety risk management crosses the threshold from reactive to proactive in Hudson's safety culture model. That transition is what separates organisations that simply comply from those that continuously improve.
The Five Situations Where EASA Mandates Root Cause Analysis
RCA is not optional. EASA Part-145 and Part-CAMO regulations specify five situations in which root cause analysis is a legal requirement — and critically, EASA does not provide a severity threshold below which RCA can be skipped for internal findings.
1. Findings from the Competent Authority (145.A.95 / CAMO.A.150) When the NAA or EASA issues a Level 1 or Level 2 finding following an oversight audit or ramp inspection, the organisation must identify root cause(s) and contributing factors, define a corrective action plan, and demonstrate implementation to the satisfaction of the competent authority. Level 2 findings typically carry a 30–90 day response window.
2. Internal Compliance Monitoring Findings (AMC4 145.A.200(a)(6) / AMC4 CAMO.A.200(a)(6)) Internal audit findings require the same rigour as authority findings. The AMC explicitly requires that root causes and contributing factors are identified and corrective actions are defined for all non-compliances found through compliance monitoring — not just the serious ones.
3. Mandatory Occurrence Reports (145.A.60 / CAMO.A.160 / EU Regulation 376/2014) Following submission of a mandatory occurrence report, a follow-up report must identify actions to prevent similar occurrences. RCA is the mechanism for identifying those actions. The initial report must be filed within 72 hours, with the follow-up report submitted as soon as actions are identified.
4. Internal Voluntary Safety Reports (145.A.202 / CAMO.A.202) The internal safety reporting scheme must enable identification of causes and contributing factors to any errors, near-misses and hazards reported — and address them through safety risk management. This applies even to voluntary reports that do not meet MOR thresholds.
5. Negative Trends in SMS Safety Performance Indicators (145.A.200 / CAMO.A.200) When safety performance monitoring reveals a declining trend in key performance indicators, the organisation must investigate causes and take corrective action. A negative trend is a system-level finding requiring the same depth of analysis as a specific event.
For Part-145 organisations, the RCA procedure must be documented in MOE Chapter 3.8 / 3.8.1. For Part-CAMO organisations, this is CAME Chapter 2.8 / 2.8.1. The authority inspector will ask which tools your organisation uses and will expect documented evidence that the chosen method has been applied consistently.
Related Training: Our Audit, Non-Conformity, Root Cause Analysis & CAPA course covers all five EASA trigger situations in depth with practical case studies and regulatory references — including how to structure your MOE/CAME sections to satisfy authority expectations
Symptom, Contributing Factor, or Root Cause — The Critical Distinction
The single most common RCA failure is stopping at the wrong level. Understanding the distinction between these three layers is the foundation of every effective investigation.
Symptom — the visible sign that something is wrong. It is what you observe and what triggers the investigation. An aircraft defect entry recording incorrect torque values is a symptom. The wrong number in the log is what you see. Addressing the symptom provides immediate relief but does not prevent recurrence.
Contributing Factor — any behaviour, omission, condition or deficiency that, if corrected, probably would have prevented the event. Multiple contributing factors typically exist. In the same torque example: the wrench was out of calibration, the work card lacked a duplicate inspection requirement, and the engineer was fatigued. Each of these contributed. Keep asking "Why?"
Root Cause — the fundamental source of the problem. If eliminated, recurrence is definitively prevented — not just made less likely. In this case: the organisation had no system for tracking calibration intervals on handheld tools at remote stations. Correct this, and the problem cannot recur through the same failure pathway.
If you are fixing symptoms, you are not doing RCA. If you are only addressing contributing factors, you have not finished the job.
The Management Control Test — Three Criteria Every Root Cause Must Satisfy
Not every deep cause qualifies as a root cause. The Management Control Test provides the check. All three criteria must be satisfied before you stop asking "Why?"
1. Identifiable — Can you clearly and specifically describe what the root cause is? The absence of a calibration tracking procedure for remote station tools is identifiable. "Poor culture" or "lack of attention" are not — they cannot be directly acted upon or eliminated.
2. Within Management's Control — Can the organisation fix this through its own decisions and actions? Updating a calibration procedure is entirely within management's control. A change in government import policy is not.
3. Has a Preventive Solution — If this cause is eliminated, will it definitely prevent recurrence? Implementing a compliant calibration system for all tools satisfies this test. Retraining one engineer does not — another engineer at any station faces the same absent process.
A cause that fails any one of these three tests is a contributing factor, not a root cause. The investigation must continue deeper.
This test is applied at every step of analysis — whether you are using the 5 Whys, an Ishikawa diagram, or MEDA. It is the universal stopping criterion.
Why Most Organisations Get RCA Wrong
Most failed root cause analyses reflect genuine misunderstandings about what constitutes a root cause, compounded by management pressure to close findings quickly. Here are the most persistent failures we encounter across the industry.
- Stopping at the symptom. The visible problem is corrected and the finding is closed. The system defect that allowed it remains untouched. Recurrence is almost certain.
- Blaming the individual. "The engineer didn't follow the procedure" is never a root cause. Why didn't they? Was the procedure available? Was it clear? Was it achievable within the conditions? Blame closes inquiry — and if your RCA process consistently finds "human error" as the root cause, it is your RCA process that is broken, not your workforce.
- Confusing corrective action with root cause. "Retrain the engineer" is a corrective action — not a root cause. Writing an action as a root cause prevents the organisation from ever asking what systemic issue made the training inadequate or the error possible in the first place.
- Identifying root causes outside management's control. External factors — weather events, regulatory changes, supplier quality — cannot be root causes because the organisation cannot eliminate them. The root cause must always be something the organisation can fix.
- Skipping RCA for "minor" findings. The regulatory AMC does not provide a severity threshold below which RCA is not required for internal compliance monitoring findings. Consistent application of RCA is itself a compliance requirement.
Choosing the Right RCA Tool for the Situation
EASA does not prescribe specific RCA tools by name, but the AMC is clear: the process must be structured, documented, and proportionate to the event. Your MOE or CAME must document which tools your organisation uses and when.
RCA tools fall into four broad categories, and effective investigators know all four:
Simple Causal tools — such as the 5 Whys — work best for straightforward, single-thread events with a clear causal chain. The 5 Whys is fast, requires no specialist training, and is the minimum standard for RCA on findings and occurrences. But it has a critical limitation: when the answer to "Why?" branches into multiple valid paths simultaneously, a linear tool cannot capture the full picture.
Structured Causal tools — such as the Ishikawa (Fishbone) Diagram and Boeing's MEDA — handle complex events with multiple contributing factors across different domains. The Ishikawa uses a 6M framework (Man, Machine, Method, Material, Environment, Management) to map all possible causes simultaneously before narrowing with evidence. MEDA, developed by Boeing with the FAA, British Airways, United Airlines and Continental Airlines, is specifically designed for aviation maintenance error investigation and has been adopted by over 120 organisations worldwide.
Statistical and Data-Driven tools — such as Pareto Analysis — identify patterns across a dataset. They answer the question: "Where should we focus first for the greatest risk reduction?" Essential for SMS trend analysis and compliance monitoring programme design.
Systemic and Framework tools — such as HFACS, AcciMap, and Fault Tree Analysis — provide deep systemic analysis of complex accidents or safety programme reviews. These are reserved for the most significant events.
The key selection principle is proportionality. A single maintenance error with a clear causal chain can be investigated effectively with the 5 Whys. A serious incident involving multiple departments requires the Ishikawa or MEDA. Recurring non-conformities demand Pareto analysis before any corrective tool is chosen. And the most powerful approach for complex events is the combined Ishikawa + 5 Whys method: use the Fishbone to map the full terrain of causes across all six categories, then apply the 5 Whys within each prioritised bone to drill to root cause depth. This combination consistently produces multiple evidence-backed root causes that a single-tool approach would miss.
Hands-On Practice: Our RCA & CAPA training course includes a dedicated practical workshop with six realistic aviation maintenance case studies — three using the 5 Whys and three using the Ishikawa method — so participants build genuine confidence with these tools before applying them in their own organisations.
Containment Is Not Corrective Action — The Three-Level Distinction
This is where authority inspectors most frequently reject CAPA submissions. Fixing the immediate problem is containment, not corrective action — and confusing the two is one of the most common compliance failures.
Level 1 — Containment (within hours). Stops the bleeding. Protects safety. Removes the nonconforming product. Grounding the aircraft, quarantining suspect parts, withdrawing an unapproved procedure. Does this prevent recurrence of the root cause? No — it only removes the specific instance.
Level 2 — Corrective Action (days to weeks). Eliminates the root cause so the same cause cannot produce the same non-conformity again. Revising the ambiguous procedure, implementing a duplicate inspection requirement, updating the training needs analysis. If properly implemented, this prevents recurrence.
Level 3 — Preventive Action (ongoing and proactive). Addresses a potential cause identified before any non-conformity occurs. Updating a procedure after a near-miss, adding a control after a Pareto trend analysis, revising induction content based on lessons learned. This reduces the probability that a potential cause produces a non-conformity.
Both corrective action and containment are required — but they serve entirely different purposes and must not be confused. An authority inspector will apply three tests to every corrective action: Does the CA specifically address the identified root cause? If fully implemented, would it prevent recurrence? Is there documented evidence of implementation?
Common responses that do not qualify as corrective action include: "Staff will be retrained" (addresses the individual, not the system), "Management will monitor" (watching the problem happen again is not prevention), "The aircraft was repaired and returned to service" (that is containment), and "The individual was counselled" (if the Substitution Test shows peers would have made the same error, the cause is systemic).
The non-negotiable rule: every corrective action must be traceable to a specific root cause statement. The CA must name the root cause. The action must address that cause. The connection must be explicit. If you cannot articulate this linkage, the CA is invalid.
Building RCA Capability in Your Organisation
Effective root cause analysis is not a form-filling exercise — it is a skill that must be developed, practised and embedded into your organisation's management system. The difference between organisations that genuinely improve and those that simply close findings is the depth and discipline of their investigation process.
This means investing in three areas: structured training for the people who conduct and review investigations, documented procedures in your MOE or CAME that describe which tools are used and when, and a culture where investigations seek system failures rather than individual blame. Boeing's own research through the MEDA programme found that 80–90% of contributing factors to maintenance errors are under management control. The problem is almost never the individual — it is the system that allowed the error to become likely.
If your organisation is experiencing recurring findings, rejected CAPA submissions, or authority audit findings that keep returning, the root cause is likely in your RCA process itself — and that is a solvable problem.
Take the Next Step: The Audit, Non-Conformity, Root Cause Analysis & CAPA in Aviation training course covers the complete audit-to-closure cycle — from the regulatory framework through RCA tools and investigation techniques to designing CAPA that satisfies authority inspection. The course includes a full practical workshop with six case studies, and every participant receives the Aviathrust Digital RCA Toolbox free of charge.
