H2S Zoning and Toxic Risk Assessment: What Good Practice Looks Like

A sour gas well test in Oman releases unignited H2S at two in the morning. The flare stack handles the flammable fraction without incident. Thirty minutes later, a control room 400 meters downwind logs a gas detector alarm at 40 ppm, a concentration that impairs judgment and can trigger respiratory distress within minutes for anyone caught in the plume. Nobody on the hazardous area classification drawing accounted for that distance, because that drawing was never built to.

This is the gap most facilities never close. Teams commission a hazardous area classification study, file it against IEC 60079-10-1, and assume the zoning question is answered. It isn’t, not for H2S. A rigorous H2S toxic risk assessment asks a different question entirely: not where a spark could ignite a flammable cloud, but how far a toxic plume travels before it drops below a survivable concentration. Get that distance wrong on a sour gas asset and the consequence isn’t a repeat drawing. It’s an uncontrolled toxic exposure zone that was never modelled, never fenced, and never briefed to the people working inside it.

This post sets out what a defensible H2S toxic risk assessment actually requires, how it differs from standard area classification, and what good practice looks like on a live sour gas facility in the GCC, India, or Southeast Asia.

Why H2S Zoning Isn’t the Same as Hazardous Area Classification

H2S zoning and hazardous area classification solve different problems. IEC 60079-10-1 classifies zones by the likelihood of a flammable atmosphere for ignition-source control. An H2S toxic risk assessment instead maps concentration-based exposure zones from a modelled release, using IDLH, ERPG, or AEGL thresholds to define how far a toxic plume remains dangerous.

Confusing the two is one of the most common errors in H2S process safety documentation. Hazardous area classification under IEC 60079-10-1 or IP 15 exists to prevent ignition. It grades zones (Zone 0, Zone 1, Zone 2) based on the frequency and persistence of a flammable atmosphere, then specifies electrical equipment ratings for each zone. H2S is flammable only at concentrations far higher than its toxic threshold, roughly 4.3% to 46% by volume for ignition versus a few hundred parts per million for lethal toxicity. A location can sit entirely outside any flammable zone and still be lethal to breathe. Treating the flammable-zone boundary as the safety boundary for personnel is the assumption that gets people hurt in a release that never ignites at all. This is precisely the blind spot an H2S toxic risk assessment is designed to close.

Aspect	Hazardous Area Classification	H2S Toxic Risk Assessment
Governing logic	Ignition source control	Concentration-based exposure control
Primary reference	IEC 60079-10-1, IP 15	ERPG/AEGL frameworks, OSHA 29 CFR 1910.1000
Output	Zone 0/1/2 equipment ratings	Toxic exposure zone radii and contours
Trigger threshold	Lower flammable limit (LFL)	IDLH, STEL, ERPG tiers
Typical boundary distance	Metres from the source	Can extend hundreds of metres downwind

Both studies belong in the same safety case, not in competition with one another. Our Hazardous Area Classification standards guide covers the IEC/ATEX/NEC/OISD framework in depth; treat that classification as the ignition-control layer and the H2S toxic risk assessment as the separate, additional layer that answers what happens to people, not equipment, when H2S is present without ignition.

How a Defensible H2S Toxic Risk Assessment Is Built

A defensible H2S toxic risk assessment starts with a credible source term, models dispersion under representative weather conditions, and maps the resulting concentration contours against IDLH and ERPG exposure thresholds. OSHA 29 CFR 1910.1000 sets the occupational exposure ceiling; the modelling determines how far that ceiling is exceeded from the release point.

Building an H2S toxic risk assessment is a sequential exercise, not a single calculation. Skipping a step doesn’t just weaken the study; it produces a zone boundary the facility will trust and then discover is wrong during an actual release.

1. Define the source term. Establish H2S concentration in the fluid stream, expected release rate, credible hole sizes, and release duration for each scenario under consideration.
2. Select representative weather conditions. Model both a worst-case scenario (typically F-stability, 1.5 m/s wind) and a more probable case (D-stability), since dispersion distance can differ sharply between the two and a design based on one alone understates routine risk.
3. Run dispersion modelling. Gaussian plume models suit steady releases over open, relatively flat terrain. Complex or congested layouts, common on process modules and offshore platforms, need CFD-based modelling instead, because a simple plume assumption breaks down around obstructions.
4. Overlay exposure thresholds. Plot IDLH (100 ppm), ERPG-2 (30 ppm), and ERPG-3 (100 ppm) contours against the site layout, not just the LFL contour already produced for area classification.
5. Map zones to site features. Control rooms, muster points, and site boundaries each need a distance-to-threshold value, not a single pass or fail line drawn once and reused everywhere.
6. Validate and document. Revalidate the H2S toxic risk assessment against any change in source composition, flow rate, or newly occupied structures nearby, consistent with management-of-change requirements.

A dispersion model built on a five-year-old source term is not a current safety case. It’s a historical document with a current-looking cover page. The OSHA hydrogen sulfide standards page is a useful reference point for the underlying exposure limits, but the modelling itself has to reflect today’s process conditions, not the conditions at first commissioning.

H2S Toxic Risk Assessment for Sour Gas Facilities in the GCC, India, and Southeast Asia

Sour gas fields across the GCC, India, and Southeast Asia carry H2S concentrations high enough that an H2S toxic risk assessment is a project-gating requirement. Regional frameworks including OISD standards in India and site HSE requirements in Qatar, Oman, and the UAE expect it to sit alongside, not inside, the area classification package.

iFluids Engineering has supported H2S toxic risk assessments across sour gas assets in Oman, Qatar, and onshore fields in India, where H2S content in raw gas can exceed 15% by volume in some formations. We are a global authority in process safety and risk engineering. That cross-regional exposure is exactly what surfaces the gaps a single-country study misses: a dispersion model calibrated for humid Gulf coastal conditions behaves differently from one built for a dry inland field, and the assessment has to reflect that difference rather than reuse a generic default.

India’s OISD guidelines reference H2S handling requirements for onshore and offshore installations alongside the national PESO framework for hazardous substances, and facilities operating under both need the H2S toxic risk assessment to satisfy each without duplicating scope. Southeast Asian sour gas developments face a comparable overlay, layering local regulatory expectations on top of the same IDLH/ERPG modelling baseline that anchors every H2S toxic risk assessment. Our Hazardous Area Classification services are frequently scoped alongside this work precisely because operators in these regions need both studies delivered as one coordinated package, not two disconnected reports arriving from different teams months apart.

Common Mistakes in H2S Zoning and Risk Assessment

The most frequent mistakes in H2S toxic risk assessments are using flammable-zone boundaries as toxic boundaries, modelling only a single worst-case weather scenario, and never revalidating the H2S toxic risk assessment after a tie-in or debottlenecking project changes the source term. Each mistake understates the real exposure zone by a meaningful margin.

The first mistake, reusing the LFL boundary from area classification as the toxic safety boundary, has already been addressed above, and it remains the costliest because it looks complete on paper while leaving a much larger toxic footprint unassessed. An H2S toxic risk assessment has to define that footprint independently, not inherit it from the classification drawing. The second mistake compounds it: teams that model only the extreme F-stability case get an impressively conservative worst-case distance, then never check whether a more frequent, less dramatic weather condition produces a chronic low-level exposure zone that the worst-case model masks entirely.

An H2S toxic risk assessment that hasn’t been revisited since first commissioning is a snapshot of yesterday’s process conditions, not a live safety case.

The third mistake is assuming gas detector coverage substitutes for a modelled zone. Detector placement is typically optimised to minimise nuisance alarms and catch a leak early, not to map the full concentration contour a release would produce. A facility can have excellent detector coverage and still have never formally modelled how far its H2S plume would actually travel under a credible release scenario.

What Good Practice Actually Looks Like

Good practice treats the H2S toxic risk assessment as a living document tied to management of change. It gets validated against both worst-case and more probable weather scenarios, and mapped directly onto site layout decisions, muster points, and PPE requirements, not filed separately from the area classification package it complements.

In practice, that means three things happen every time the process changes. First, the source term gets revisited before the H2S toxic risk assessment does, since an outdated H2S concentration figure invalidates every contour drawn from it. Second, both weather cases from the methodology above get rerun, not just the worst case used for the original design basis. Third, the resulting contours get walked against the actual site layout: does the muster point sit inside an ERPG-2 contour under the more probable weather case, not just the extreme one? Facilities that skip this last step often discover the gap only when an incident investigation asks why the muster point was where it was. That gap is precisely what a properly maintained H2S toxic risk assessment closes before an incident, not after one.

Our process safety management practice treats this kind of revalidation as a standing item, not a one-off deliverable, because an H2S toxic risk assessment that’s accurate on the day it’s issued and stale eighteen months later has done its job for one design review and nothing since.

Conclusion

H2S toxic risk assessment isn’t a compliance box next to the area classification drawing. It’s the study that tells you how far a release travels before it stops being survivable, and it answers a question the flammable-zone boundary was never built to answer. Facilities that get this right treat the H2S toxic risk assessment as a living document: revalidated after every source-term change, modelled against more than one weather case, and mapped onto actual site layout decisions rather than filed as a standalone report.

Here is the practical takeaway. If your last H2S toxic risk assessment predates your current process conditions, or if it was never clearly distinguished as a separate H2S toxic risk assessment from your area classification study, it isn’t protecting anyone against the scenario that matters most: an unignited toxic release drifting toward an occupied space.

Speak with our H2S zoning and toxic risk assessment team about validating or rebuilding your facility’s H2S toxic risk assessment against current process conditions.