Root Cause Analysis

Quick Answer

Root cause analysis is an incident investigation method that looks past the immediate, visible cause of an incident to identify the underlying systemic factors that actually allowed it to happen — asking 'why' repeatedly until reaching a fixable root issue, rather than stopping at the first obvious explanation.

Root cause analysis is a systematic method for investigating incidents that deliberately looks past the immediate, obvious cause to find the deeper, systemic factors that actually allowed the incident to occur.

Why “The Obvious Cause” Usually Isn’t the Real Answer

If a crew member is injured because they weren’t wearing PPE, “didn’t wear PPE” is the immediate cause — but stopping there misses the real question: why weren’t they wearing it? Was PPE not available? Was there no enforcement culture? Was the task rushed due to schedule pressure? Root cause analysis pushes past the first answer to find the systemic issue, because fixing only the immediate cause (telling that one person to wear PPE next time) doesn’t prevent the same underlying conditions from causing a similar incident with someone else.

The “Five Whys” Technique

A commonly used, simple root cause method: ask “why” repeatedly (typically around five times, though not a strict rule) until reaching an answer that’s genuinely fixable at a systemic level, rather than an individual blame point.

Example:

  1. Why did the crew member get injured? — They slipped on a wet deck
  2. Why was the deck wet? — A pump was overflowing
  3. Why was the pump overflowing? — The level alarm wasn’t working
  4. Why wasn’t the alarm working? — It hadn’t been tested in the PMS schedule
  5. Why wasn’t it in the PMS schedule? — It was never added when the pump was installed

The real, fixable root cause here is a gap in the PMS setup process — not “the crew member should have been more careful.”

Root Cause Analysis and the ISM Code

Investigating incidents and near-misses to identify genuine root causes — not just documenting what happened — is a required element of a vessel’s Safety Management System under the ISM Code. A superficial investigation that stops at “human error” without asking why the error was possible in the first place fails this genuine purpose.

Why This Matters Beyond Compliance

Root cause analysis done properly prevents recurrence; done superficially, it produces the same type of incident again under a different name. The distinction between genuine systemic investigation and blame-focused, surface-level reporting is exactly what separates an effective safety culture from a paperwork exercise.

Exam Relevance

Root cause analysis principles, particularly the distinction between immediate and systemic causes, are core Safety Management topics in deck and engineering officer competency exams, especially at senior officer level.

🤖

Ask SailorGPT About This Topic

Get deeper explanations, real-world examples, and personalized guidance on any maritime topic.

🩺 Free Financial Health Check

You know the terms. Do you know where your money stands?

Emergency Fund · Term Insurance · Health Cover · Debt · Investments — 5 questions. Instant score. Free.

Check My Financial Health — Free →
Ask SailorGPT AI Talk to Chief
)} })) }