15 Real 5 Whys Examples From Industrial Incidents
POR Equipe editorial RiskoPilot · REVISADO EM 2026-07-11
The 5 Whys technique iteratively asks 'why?' up to five times to trace a symptom to its root cause. It works well for single-thread, low-severity operational issues. It fails for multi-causal, high-severity incidents where organisational failures matter — because it produces a single linear chain that usually terminates at 'human error'. Below: 15 real 5 Whys examples plus the cases where you need to switch to Tripod Beta.
Manufacturing — pump seal failure
Problem: pump P-102 seal failed at 3 a.m., spilling 40 litres of hot oil. 1) Why did the seal fail? Excessive vibration. 2) Why? Bearing wear. 3) Why? Missed 2,000-hour lubrication service. 4) Why? Preventive maintenance schedule slipped 6 weeks. 5) Why? Maintenance team down 2 techs since Q2, no backfill authorised. Root cause: resourcing decision, not equipment fault. Action: reinstate backfill or reduce operational scope.
Construction — worker fall from scaffold
Problem: worker fell 3.5 m from scaffold, sustained wrist fracture. 5 Whys terminates at: 'harness not clipped in'. This is where 5 Whys fails — the real question is why an experienced worker who owned a valid PASMA card did not clip in. Answer: production pressure to hit close-out milestone, tacit acceptance in the crew. Tripod Beta reveals: incompatible goals (production vs safety), error-enforcing conditions (rushed work), organisation (crew culture). 5 Whys stops at the operator; Tripod Beta reaches the management system.
Chemicals — reactor over-temperature
Problem: reactor R-301 exceeded 180°C limit for 4 minutes. 1) Why? Cooling water flow dropped. 2) Why? Control valve CV-42 stuck. 3) Why? Solids build-up on stem. 4) Why? Upstream filter bypass valve left open after cleaning. 5) Why? No procedural checklist for filter cleaning included the bypass position. Root cause: procedures. Action: update SOP-411, add MOC to catch similar procedural gaps.
Oil & gas — dropped-object near-miss on drill floor
Problem: 4-kg spanner fell 12 m onto drill floor, near-missed derrickman. 5 Whys goes: 1) unsecured tool. 2) worked at height without lanyard. 3) lanyard not available. 4) tool control storeman off shift. 5) no cover for tool control storeman. Sensible. But if you have four dropped-object near-misses in a year at four different sites, 5 Whys can't tell you they share a common organisational root — Tripod Beta's GFT classification reveals defences (tool control) as a systemic weakness.
When to use 5 Whys vs Tripod Beta
Use 5 Whys for: single-thread operational issues, sub-recordable events, first-pass framing before a deeper analysis. Switch to Tripod Beta when: any of severity ≥ MTC, multi-actor causation, repeat pattern across incidents, contractor involvement, regulator or insurer will read the report. Rule of thumb: 5 Whys writes tickets; Tripod Beta writes reports.
Perguntas frequentes
Executar uma investigação gratuita
Gere um relatório Tripod Beta em menos de 5 minutos — sem cartão.
Executar uma investigação gratuita