H2S on the Rig: Drills, Training Records, and What Compliance Requires

Hydrogen sulfide does not announce itself. It smells like rotten eggs at low concentrations, then deadens the nose at higher ones, and at the concentrations that occur in sour wells it can kill in seconds. That is why H2S safety is not a training topic on a rig; it is a operating system. And like every operating system, it runs on records.

What API RP 49 requires

API RP 49 applies to well drilling, completion, servicing, and workover operations where H2S may be present. It is not a single rule; it is a package: hazard assessment, detection equipment (fixed and portable), training for everyone on location, respiratory protection, contingency plans, and emergency response procedures. OSHA's respiratory protection standard at 29 CFR 1910.134 governs the breathing apparatus side, and state rules like Railroad Commission of Texas Rule 36 add their own sour gas requirements. Industry training programs also align with ANSI Z390.1, the H2S training standard.

The practical core is detection and response: everyone on location knows what the alarms mean, where the wind socks point, and what to do when the monitor trips. The well control guide on this site covers the kick and pressure side; H2S is the chemical hazard that rides along with it.

Where rigs fall short: the records

The equipment gets inspected. The monitors get calibrated. The gap is usually the file: who on this crew is trained, when, by whom, and is the ticket still current. H2S certification is not a one-time course; it expires and must be refreshed. On a rig with rotating crews and contractor churn, the training matrix goes stale quietly. The first time it matters is the audit, or the incident.

Drills that mean something

Records are only as good as the drills behind them. A monthly H2S drill that walks the crew to the muster point and tests the alarms is a safety system. A drill signed on a clipboard without anyone leaving the doghouse is paperwork. Operators that treat drill documentation as evidence, not formality, are the ones whose crews respond correctly when the monitor trips for real. The same logic runs through the rig crew training and certification guide on this site: the ticket is proof of training, the drill is proof of behavior.

What a compliance file looks like

Per role: a training record with course, date, provider, and expiry. Per rig: a drill log with date, scenario, attendance, and findings. Per crew change: a handover that confirms every incoming member's tickets are current before the outgoing crew leaves. That matrix is small, but it is exactly the file that keeps a crew alive on a sour well and keeps an operator out of the citation pile.

If your H2S records live in a binder that nobody opens, book a working session with the OpsFlo operations team. Book a call here to track training, drills, and certifications against every crew member.