Incident Reporting on the Rig: What Gets Reported and What Gets Missed

Every safety program on a rig starts with the same raw material: knowing what is going wrong. That is what incident reporting is for. The problem is that the raw material is incomplete. Injuries in oil and gas are chronically underreported, the recordkeeping is inconsistent across contractors, and the incident that never gets reported is the one that cannot be fixed.

BLS research on injury data quality concludes that work-related injuries and illnesses in the United States are chronically and even grossly underreported. The gap is not a paperwork nuisance; it is a blind spot in every safety decision made from the data.

What the rules require

OSHA recordkeeping requires employers to record work-related injuries and illnesses that meet the criteria, and the severe injury rule tightens it further: amputations, loss of an eye, and inpatient hospitalizations must be reported to OSHA within 24 hours. The rules are not optional, and they apply to contractors on location, which means a rig can have five different employers with five different reporting habits on the same pad.

The scale of the problem

CDC analysis of OSHA severe injury reports found 2,101 severe work-related injuries reported by the oil and gas extraction industry between January 2015 and July 2022, and the burden is lopsided: well servicing support companies accounted for 70 percent of them. The same analysis notes the industry's workers are overrepresented in injuries and fatalities, and that contract workers often get less training and less information about the hazards they face. Reporting discipline is weakest exactly where the risk is highest.

Why incidents get missed

Underreporting on rigs is rarely a single lie. It is a thousand small pressures: a contractor worried about a client relationship, a crew worried about the drug test that follows the report, a supervisor who decides a sprained wrist is "not that bad," a first-aid kit that handles the case without a record. None of those feel like fraud in the moment. All of them remove the data point that would have told the operator where the real risk was. The training and certification guide on this site makes the related point: the ticket proves the training, but only honest reporting proves the behavior.

Near misses are the leading indicator

The most useful report a rig can file is the near miss: the dropped object that missed the crew, the slip that caught a railing, the gas reading that was high but below alarm. Near misses are leading indicators; they show the failure mode before it produces a body. The crews that log them consistently are the crews whose serious incidents drop, because they are fixing the cause while it is cheap. The gas detection article on this site shows the pattern at the instrument level: the crew that treats every excursion as data is the crew that stops the blowout before it starts.

What a reporting workflow looks like

Capture at the rig, with a timestamp and an owner. A simple form that takes minutes: what happened, what was the cause, what was the response. A review loop that closes the report with an action. And a record that survives crew changes and audits. That is not bureaucracy; it is the difference between knowing your risk and guessing at it.

If incident forms are filled out after the fact and filed in a drawer, book a working session with the OpsFlo operations team. Book a call here to capture incidents and near misses at the rig with the record attached.

Sources

Filling incident forms after the fact?

Book a working session with OpsFlo to capture incidents and near misses at the rig with the record attached.

Book a session
← Back to rigs.work