There is no single root cause analysis (RCA) method that is universally “most common” across aerospace, but a consistent pattern shows up:
- 5 Whys and fishbone (Ishikawa) diagrams are widely used as practical, day-to-day tools to structure thinking and quickly converge on likely causes.
- 8D-style investigations (or equivalent structured CAPA templates) are common for issues that touch safety, airworthiness, customer escapes, or formal regulatory reporting.
- Fault Tree Analysis (FTA) and similar system-safety methods are used where failure can affect flight safety or mission performance, especially in design and system engineering.
Which method is used in practice depends on:
- Severity and criticality of the event (e.g., cosmetic defect vs potential safety-of-flight issue).
- Where the problem is found (design, manufacturing, maintenance, supplier).
- Customer and contract requirements (many primes specify their own RCA / 8D formats).
- Existing QMS and IT systems (CAPA workflows in legacy QMS, MES, and ERP often embed one method).
Common RCA methods and how they are actually used
5 Whys
- Very common as a first-pass technique on the shop floor and in maintenance.
- Often embedded inside 8D or CAPA templates as the core root cause logic.
- Strength: simple, fast, easy to teach. Weakness: highly dependent on facilitator skill and data quality, and can stop early under schedule pressure.
Fishbone (Ishikawa) diagrams
- Common in manufacturing and process engineering to map possible causes across categories like Man, Machine, Method, Material, Measurement, Environment.
- Frequently paired with 5 Whys: fishbone to identify candidate causes, 5 Whys to drill into the most plausible ones.
- Strength: good for complex, multi-factor problems. Weakness: can become a brainstorming list without clear evidence or prioritization.
8D (Eight Disciplines)
- Very common for customer-reported issues, escapes, and safety-relevant defects, particularly in aerospace OEM and tiered supply chains.
- Many primes require suppliers to submit 8D reports or close equivalents, and legacy QMS platforms often have baked-in 8D workflows.
- 8D itself is a framework. The actual RCA inside D4 typically uses 5 Whys, fishbone, or a combination, supported by data.
- Strength: enforces containment, verification, and documentation. Weakness: can become paperwork-driven if not supported by real analysis and data.
Fault Tree Analysis (FTA) and other system-safety methods
- Common in system and design engineering, less so for everyday shop-floor defects.
- Used where regulatory and certification expectations (e.g., for flight safety) require probabilistic and logic-based analysis of failure modes.
- Strength: structured and traceable for complex systems. Weakness: time-consuming, and requires specialist skills and validated models.
Brownfield reality and system coexistence
In most aerospace environments, RCA does not live in a vacuum. It is constrained by existing tools, templates, and validation:
- Legacy QMS / CAPA tools often enforce an 8D-like structure, with 5 Whys or fishbone as embedded steps.
- MES and ERP systems may only support limited attachment and traceability, so engineers end up mixing whiteboards, spreadsheets, and scanned diagrams with system records.
- Replacement of RCA tooling or workflows is non-trivial because changes affect audit trails, training, and validated processes. Many plants layer new methods on top of existing systems rather than ripping them out.
Because of this, “most common” in practice tends to mean:
- 5 Whys and fishbone used informally and in standard work for problem solving, and
- Those analyses documented inside a structured 8D or CAPA template to satisfy customer and regulatory expectations.
Choosing methods in your context
For a typical aerospace manufacturer or MRO:
- Use 5 Whys + fishbone for most process, defect, and escape investigations, ensuring evidence links each “why” to actual data.
- Wrap that analysis in your existing 8D or CAPA framework when dealing with customer issues, systemic nonconformities, or anything safety-relevant.
- Reserve FTA and related methods for system-level and safety-of-flight problems, typically led by design/system engineering, not just manufacturing.
Whatever mix you choose, the real differentiators in aerospace are not the brand name of the method but:
- Quality of data and traceability across systems.
- Consistency of application under schedule and delivery pressure.
- Evidence that the method is embedded in your validated QMS and change-control processes.
