Employer Guide

Investigating Incidents: Finding the Root Cause, Not the Blame

When someone gets hurt on a location, the instinct is to find out who is to blame and move on. That instinct produces more injuries, not fewer. An investigation exists to answer one question: what failed in the work system, and what do we fix so the next crew does not get hurt the same way? This guide covers the steps in order: why investigate at all, the reporting deadlines you cannot miss, securing the scene, immediate cause versus root cause, and corrective actions that actually get done.

Why investigate at all

An investigation has three jobs, and none of them is assigning blame.

The first job is prevention. Every incident is a warning that part of the way you work is not safe enough. A hand injury on a valve manifold tells you the procedure, the tooling, or the training failed. Find the failure and fix it, and you have protected the next person who reaches for that valve. Skip the investigation, and the same failure waits for a repeat.

The second job is meeting your duties. Under OSHA's recordkeeping rules, most injuries go on the 300 log, and some must be reported to OSHA within hours. Those records feed your safety program and prove to anyone, including an inspector, that you know what happened. The recording side is covered in our guide on OSHA recordkeeping for oilfield employers.

The third job is protecting the crew. A crew that watches a supervisor treat an injury as a personal failure learns to hide the next one. A crew that sees an injury turned into a fix learns that reporting is safe. That behavior change is worth more than any single corrective action.

The reporting clock

Reporting to OSHA is not optional and it is not slow. Under 29 CFR 1904.39 the deadlines are strict:

A work-related fatality must be reported to OSHA within 8 hours of the employer learning about it. A work-related in-patient hospitalization, an amputation, or the loss of an eye must be reported within 24 hours.

Reports go to the nearest OSHA area office, by phone or the agency's online form, and OSHA will typically open an inspection in response. Note where the clock starts: when you learn of the incident, not when you finish gathering facts. The first call is to OSHA, not to the paperwork. Make the call with what you have and refine the details after. The full text of the rule is linked in the sources below.

Secure the scene and gather facts

Care for the injured person first. Our guide on first aid and CPR at oilfield locations covers the response. The investigation starts after the person is stable, not before.

Then the scene is evidence. Do not let it be cleaned up, moved, or put back before anyone looks at it. If the incident involves fire or a wider emergency, the emergency action and fire prevention plans for the location govern how responders move in. Beyond that, everything stays as close to the moment as possible.

Photograph the scene from every angle before anything is touched. Mark where the equipment sat, where the person stood, what guards and tools were in place. Interview witnesses one at a time, on location, while memory is fresh, and write down their words rather than your summary of them. Check the equipment: was a guard missing, a valve seized, an alarm bypassed? Pull the maintenance records. Then write a timeline covering the hour before and the last seconds.

Facts gathered this way give the investigation something real to work from, and they protect everyone involved: the record shows what was actually found, not what someone later remembers.

Immediate cause vs root cause

The immediate cause is what happened in the moment: the line was pulled, the step was missed, the guard was off. The root cause is why the system allowed it: the procedure was unclear, the guard was never replaced after a repair, the crew was short-handed, the training never covered that task.

The classic mistake is stopping at the immediate cause. "He slipped" explains nothing and fixes nothing. Why was the surface slick? Why was the walkway routed through a mud spill? Was there a job safety analysis covering the task, and did the crew follow it? If the JSA never mentioned the hazard, the JSA failed, not the worker. Our guide on job safety analyses for field operations walks through building one that matches the work as it is done.

Keep asking why until you hit something you can change. Every answer should land on a thing: a procedure, a tool, a guard, a schedule, a training gap. If an answer lands on a person's character, you have stopped too early. Root causes usually come in groups: a weak procedure plus a missing guard plus a rushed schedule. List them all; the next section sorts them out.

Corrective actions that stick

An investigation is only worth the actions that come out of it. A report that ends with "retrain the crew" and nothing else is a report that will be repeated. Corrective actions that stick share four traits.

They are specific. "Improve training" is not an action. "Add a step to the valve replacement procedure covering lockout, and drill it with the night crew" is an action.

They have an owner. Every action carries one name, not a department. A department does not miss a deadline; a person does.

They have a deadline, and the deadline is checked. Follow-up is where most programs fail. Corrective actions with owners and deadlines, tracked past the investigation, are the kind of follow-up software like OpsFlo keeps: tickets, dispatch, approvals, timesheets, and documents in one place, so the action does not disappear into a file.

They are verified. The fix is done when someone checks that the guard is back on, that the procedure says the new thing, that the crew works the new way. A verification visit two weeks later is worth more than a signature on a form.

Close the loop the same way the investigation opened it: with the crew. When an action is verified, tell the crew what changed and why. That is what turns a report into a safer location.

Sources and further reading

Want this applied to your field operation?

OpsFlo turns tickets, dispatch and approvals into one clean billing flow.

Book a working session