Skip to content
OSHA Process Safety Management (29 CFR 1910.119)

Incident Investigation

Investigation of any incident with catastrophic release potential, begun within forty eight hours

Strategic context

What this element is and why it matters

OSHA PSM at 1910.119(m) requires investigation of each incident that resulted in, or could reasonably have resulted in, a catastrophic release of a highly hazardous chemical. The investigation has to begin within forty eight hours under (m)(2). A team has to be established under (m)(3) that includes members who know the process. A report under (m)(4) has to include the date, a description, the contributing factors, and recommendations. The findings have to be addressed under (m)(5), and the reports have to be retained for five years under (m)(6). Our team runs these investigations so they reach the real causes.

Incident Investigation

Individual significance for organisations

Organisations that genuinely learn from incidents prevent them from recurring, while those that do not suffer the same incidents over and over. This element is also a strong indicator of how mature the culture is, because facilities that report near misses and investigate them deeply have real psychological safety, whereas facilities that do not are carrying hidden problems waiting to surface. We help your team build the kind of investigation that earns that trust.

Contribution to OSHA Process Safety Management (29 CFR 1910.119)

Paragraph (m) closes the feedback loop for the whole OSHA PSM framework. It captures the actual outcomes against the controls that were intended, surfaces the causal chains that other elements missed, and drives corrective action through management of change in (l). The forty eight hour initiation requirement is one of the few PSM elements with a hard time based gate, and it prevents the familiar pattern of investigation delays that lose evidence.

Key requirements

What compliant execution looks like

Investigation of incidents with catastrophic release potential under (m)(1)
Initiation within forty eight hours under (m)(2)
A team that includes a person who knows the process under (m)(3)
A report with the date, description, contributing factors, and recommendations under (m)(4)
Findings addressed and reviewed with personnel under (m)(5)
Five year retention of the reports under (m)(6)
Implementation methodology

How we implement this element

A focused six step methodology calibrated to deliver incident investigation as a working capability rather than a documented compliance artefact.

Investigation Trigger

To meet (m)(1) we define the trigger as an actual or potential catastrophic release and align it with your corporate threshold and reporting matrix.

Forty Eight Hour Initiation

To meet (m)(2) we begin the investigation within forty eight hours, preserve the evidence chain, and secure control system, historian, and CCTV data.

Team Formation

To meet (m)(3) we form a multidisciplinary team that includes a person who knows the process, with contractor representation where it applies, and align it with a just culture.

Root Cause Analysis and Report Authoring

To meet (m)(4) we apply a root cause method such as TapRooT, Apollo, or the Causal Tree, document the contributing factors and recommendations, and reach the latent causes.

Findings Addressal

To meet (m)(5) we address the findings with corrective action, review them with the affected personnel, and integrate them with operator training.

Documentation and Retention

To meet (m)(6) we retain the reports for five years and integrate them with corporate lessons learned and the API RP 754 process safety event indicators.

Implementation flow

Element implementation flow chart

A decision gated workflow that shows the actual sequence of activities from initiation through steady state operation, with key decision points highlighted.

Start
An incident or near miss occurs
Decision
Catastrophic Potential (m)(1)?
Decision gate
Forty Eight Hour Initiation (m)(2)
Team formed, scene secured, and evidence preserved
Evidence Collection
Control system, historian, CCTV, witness statements, and samples
Root Cause Method Selection
TapRooT, Apollo, Causal Tree, or events and causal factors charting
Causal Chain Construction
From physical to immediate to latent to organisational causes
Report Authoring (m)(4)
Date, description, factors, and recommendations
Findings Addressal (m)(5)
Corrective action and review with personnel
Action Owner and Close Out
Integration with management of change and verification
Retention (m)(6)
Five year retention and lessons learned shared
Deliverables

What we produce

  • An investigation procedure with a forty eight hour trigger
  • Guidance on selecting the root cause methodology
  • Just culture facilitation training
  • A corrective action tracking database
  • A lessons learned sharing protocol
  • A five year retention procedure
Common pitfalls

Where execution fails

  • An investigation that stops at the conclusion of operator error
  • Initiation delayed past forty eight hours under operational pressure
  • Corrective actions that are filed but never closed
  • Lessons learned that are never shared across sites
Standards & references

Codes this element is built on

OSHA 29 CFR 1910.119(m) (Incident Investigation, US)CCPS Guidelines for Investigating Process Safety IncidentsIEC 62740 (Cause Analysis Methodology)API RP 754 (PSE Indicators)Factories Act 1948 Section 88 (India Incident Reporting)MSIHC Rules 1989 Rule 5 (India)
Implement this element

Talk to us about implementing Incident Investigation

We can scope this element implementation against your facility, regulatory context, and existing management system maturity, then integrate it with the other OSHA Process Safety Management (29 CFR 1910.119) elements you already operate.