How to Read a Failure Analysis Report
What Is a Failure Analysis Report?
A failure analysis report (FAR) is the formal deliverable of a systematic investigation into why a material, component, or product failed in service, testing, or manufacturing. It documents the evidence collected — visual examination, fractography, metallography, chemical analysis, mechanical testing — and connects that evidence to a failure mode, a failure mechanism, and ultimately a root cause, followed by corrective recommendations. FARs are relied upon in warranty disputes, supplier corrective action requests (SCARs), regulatory submissions, litigation, and design reviews across the automotive, aerospace, medical device, oil & gas, and electronics industries.
Reading a FAR correctly matters as much as commissioning one. The technical conclusions determine whether a supplier is charged back, a design is revised, a fleet is recalled, or a process parameter is changed — so engineers and managers receiving the report must understand what each section proves, what it merely suggests, and where the limits of the evidence lie.
Structure of a Failure Analysis Report
Executive Summary
A one-page statement of what failed, the identified failure mechanism, the root cause, and the headline recommendation. Read this first — but never act on it alone. The summary states conclusions; the confidence behind those conclusions is only visible in the evidence sections.
Background and Service History
Describes the component: material grade, drawing/specification, manufacturing route, heat-treatment condition, operating environment, service hours or cycles, and the circumstances of failure. Verify this section against your own records — an incorrect load assumption or wrong material grade recorded here can invalidate the downstream analysis.
Methodology
Lists the techniques applied and the standards followed. Typical methods include:
- Visual and stereomicroscopic examination — fracture origin location, deformation, corrosion products
- SEM fractography with EDS — fracture surface features and elemental analysis of deposits or inclusions
- Metallography (ASTM E3, E407) — microstructure, case depth, decarburization, grain size (ASTM E112)
- Chemical composition (OES, ICP per ASTM E415/E1479) — conformance to the material specification
- Hardness testing (ASTM E18, E384) — heat-treatment verification, hardness traverses at the failure site
- Mechanical testing (ASTM E8) — tensile properties of exemplar material where sample size permits
A credible report ties each technique to a question it was meant to answer, not simply a list of instruments available.
Observations and Findings
The factual core of the report — micrographs, fractographs, spectra, and data tables presented without interpretation. Key fractographic indicators to recognise:
- Beach marks and striations → fatigue (progressive cracking under cyclic load)
- Dimpled rupture → ductile overload
- Cleavage facets or intergranular facets → brittle fracture, embrittlement, or environmental attack
- Branched cracking with corrosion products → stress corrosion cracking (SCC)
- Necking and shear lips → ductile overload; their absence on an “overload” conclusion is a red flag
Findings must be traceable: every image should carry magnification, location, and orientation relative to the fracture origin.
Analysis and Discussion
Here the analyst links findings to a failure mechanism. Watch for the critical distinction:
- Failure mode — how the part failed physically (e.g., fatigue fracture through the fillet radius)
- Failure mechanism — the physical process (e.g., high-cycle fatigue initiated at a machining groove)
- Root cause — the controllable origin (e.g., surface finish out of specification due to worn tooling)
A report that stops at the mechanism (“the shaft failed by fatigue”) has not delivered a root cause and does not support corrective action.
Root Cause and Recommendations
The root cause statement should be singular where the evidence supports it, or clearly ranked where multiple contributing factors exist. Recommendations should map one-to-one to the causes identified — design change, material substitution, process control, inspection addition, or maintenance interval revision. Recommendations that don’t trace back to a documented finding are opinion, not analysis.
Appendices
Raw data, calibration certificates, test protocols, and chain-of-custody documentation. In disputes and regulated industries, this section is what makes the report defensible.
How to Evaluate the Quality of a FAR
Before acting on conclusions, check:
- Evidence-conclusion linkage — Can every statement in the root cause be traced to a specific micrograph, measurement, or data table in the findings?
- Alternative hypotheses — Did the analyst consider and rule out competing mechanisms, or only confirm the first theory?
- Origin identification — Was the fracture origin actually located and examined, or was the analysis done on secondary fracture surfaces?
- Material conformance — Were composition and hardness checked against the governing specification, not just reported?
- Preservation of evidence — Were fracture surfaces protected before examination? Cleaned or corroded surfaces limit fractographic confidence, and the report should say so.
- Stated limitations — A trustworthy report states what could not be determined and why. Absolute certainty on incomplete evidence is a warning sign.
Standards and Frameworks Referencing Failure Analysis
- General practice: ASTM E2332 (product failure investigation), ASM Handbook Vol. 11 (Failure Analysis and Prevention)
- Fractography: ASTM E1820 supporting fracture mechanics context; ASM Handbook Vol. 12
- Metallographic methods: ASTM E3, E407, E112, E45 (inclusion rating)
- Corrective action systems: IATF 16949 8D process, AS9100 root cause corrective action (RCCA), FDA CAPA requirements for medical devices
- Legal/insurance: ASTM E860 (examination and preparation of items involved in litigation)
Conclusion
A failure analysis report is only as useful as the reader’s ability to separate evidence from interpretation. Read the executive summary for direction, verify the background against your records, judge the findings on traceability, and demand a root cause — not just a mechanism — before committing to corrective action. Reports that link every conclusion to documented physical evidence, consider alternative hypotheses, and state their own limitations are the ones that hold up in supplier negotiations, audits, and court.
What is the difference between failure mode, failure mechanism, and root cause? Failure mode is the physical manner of failure (fracture, wear, leak). Failure mechanism is the process that produced it (fatigue, stress corrosion cracking, creep). Root cause is the controllable origin of that mechanism (design stress concentration, out-of-spec heat treatment, incorrect material). Corrective action can only address the root cause — a report that stops at the mechanism is incomplete.
How can fatigue failure be identified in a report? Fatigue is confirmed by fractographic evidence: beach marks visible at low magnification marking crack-front arrest positions, and striations under SEM representing individual load cycles. The report should identify the initiation site (surface defect, inclusion, machining mark), the direction of crack propagation, and the final fast-fracture zone, whose size indicates the load at final separation.
Why does a failure analysis report sometimes not give a definitive root cause? Confidence depends on evidence condition. Fracture surfaces damaged by post-failure corrosion, mechanical rubbing, or improper handling destroy the features analysts rely on. Missing service history, unavailable exemplar parts, or multiple simultaneous contributing factors also limit certainty. A credible report ranks probable causes and states the limiting factors rather than forcing a single conclusion.
What should be done with a failed part before sending it for analysis? Do not clean, touch, or fit the fracture surfaces back together — this destroys fractographic evidence. Protect surfaces from corrosion (dry storage, desiccant, no tape or oil on the fracture), photograph the as-found condition, retain all fragments and mating hardware, and document service history, loads, and environment. Chain-of-custody records are essential if litigation is possible.
How long does a failure analysis take and what does it typically include? A standard metallurgical failure analysis takes 2–4 weeks depending on scope: visual and SEM examination, EDS analysis of deposits, metallographic sectioning, chemical composition verification, and hardness testing, concluding with a root cause report. Complex cases involving mechanical testing of exemplars, fracture mechanics calculations, or fire/explosion scenarios extend timelines and are typically quoted in phases.
Other Categories
