What Is Sour Gas?
Sour gas is natural gas that contains significant hydrogen sulfide. It is one of the most consequential distinctions in gas production because it dictates the safety precautions, materials, and processing a field requires before the gas can be sold.
Sour Gas in one line: Sour gas is natural gas containing appreciable amounts of hydrogen sulfide (H2S), and often carbon dioxide. It is corrosive and toxic and cannot enter pipelines or be sold until the H2S is removed. Gas with little or no H2S is called sweet gas. The line between them is set by pipeline and sales specifications, commonly around 4 ppm H2S.
Sour versus sweet
Whether a gas is sour or sweet is defined by its hydrogen sulfide content relative to the specification it must meet. U.S. pipeline sales specifications typically cap H2S at about 4 ppm (roughly a quarter grain per 100 standard cubic feet), so gas above that must be treated. Gas at or below the limit is sweet and can be sold; anything meaningfully above it is sour.
Sourness is a spectrum. Some reservoirs carry only a few ppm of H2S; others contain several percent, and a handful worldwide exceed 15 to 30 percent H2S, which is extraordinarily hazardous. Carbon dioxide often accompanies H2S; together they are called acid gas because they form acids in water and are removed in the same treating step.
Why sourness matters
Two problems make sour gas demanding. First, safety: H2S is acutely toxic, so sour fields require gas detection, personal monitors, escape breathing apparatus, and emergency planning throughout drilling, production, and processing. Second, corrosion: wet H2S attacks ordinary carbon steel and can cause sulfide stress cracking and hydrogen-induced cracking, sudden brittle failures of pressurized equipment.
Because of the cracking risk, sour service requires special materials selected under standards such as NACE MR0175 / ISO 15156, controlled-hardness steels, and corrosion inhibition. Handling sour gas therefore costs more in metallurgy, monitoring, and procedure than sweet gas at every stage from wellhead to plant.
Sweetening the gas
Before sour gas can be sold, the acid gases are removed in a process called sweetening, most commonly with an amine unit that absorbs H2S and CO2 into a circulating solvent and then strips them back out. The concentrated acid gas stream is then routed to a sulfur recovery unit, often a Claus plant, that converts H2S into elemental sulfur, or is otherwise disposed of by acid gas injection.
The result is pipeline-quality sweet gas plus a sulfur or acid-gas byproduct. In the field, sour operations lean heavily on continuous monitoring, H2S detector readings, treating-unit performance, and inlet gas quality, so that any upset that lets H2S slip downstream or accumulate on site is caught immediately.
Instrumenting a Sour Site
Fixed-point H2S detection is the backbone of a sour site. Because H2S is denser than air, it pools in low places - cellars, pits, tank berms, buildings, and the downwind side of separators - so fixed sensors belong low and close to the likely release points rather than at head height in open air. Wind socks at the entrance and at the wellhead give everyone an upwind escape direction at a glance. Placement is site-specific and belongs in the facility's safety design, but the principle is constant: put the sensor where the gas will go, not where it is convenient to mount. The steps in commissioning an H2S gas detector cover getting a new point into service properly.
Fixed detectors alarm the site; personal monitors protect the person. Everyone entering a sour facility wears one, and both kinds of instrument are only trustworthy if they are challenged with test gas on a schedule - the routine of bump testing and calibrating a gas detector exists precisely because a sensor that has quietly died looks identical to a sensor reading zero. Detector outputs are wired to the site controller for alarming, telemetry, and shutdown logic, with the safety trips themselves executed in dedicated local hardware.
Working Practices Around Sour Gas
The cruel property of H2S is that it disables the nose. At low concentrations it smells of rotten eggs; at dangerous concentrations it deadens the sense of smell quickly, so the absence of odor proves nothing at all. Field practice is built around that fact: approach equipment from upwind, trust the monitor and not the nose, and treat any personal alarm as an instruction to leave immediately. Entry into pits, tanks, or enclosed buildings on a sour lease is a permitted activity governed by the site's H2S contingency plan, and those decisions belong to qualified safety personnel, not to whoever happens to be on location.
The high-exposure moments are the routine ones: pulling a sample, draining a vessel, breaking a flange, blowing down a line. Sour-site procedures wrap those tasks in gas testing, permits, and standby arrangements because opening the process is when the gas reaches people. None of that is bureaucracy; it is the operational answer to a hazard that gives little warning.
Before Tying a New Well Into a Sour System
A new tie-in changes the composition of everything downstream, so the homework happens before the valve opens:
- Obtain a full gas analysis for the new well, including H2S and CO2, rather than assuming it matches its neighbors.
- Verify every component the new stream will touch against NACE MR0175 / ISO 15156 sour-service limits, including the small items - fittings, springs, and instrument wetted parts.
- Confirm the treating system has capacity for the added acid-gas load, whether that is an on-lease unit or a downstream gas processing plant.
- Recheck the blended stream against the sales contract's H2S specification, since a small sour well can push a large sweet stream out of spec.
- Update detector coverage, signage, and the contingency plan to reflect the new source.
Skipping the analysis step is the classic failure: a well assumed sweet because the field is sweet, discovered sour only after the metallurgy question has already been answered the wrong way.
Frequently Asked Questions
At what H2S level is gas considered sour?
There is no universal number; it depends on the specification the gas must meet. In practice, U.S. pipeline sales contracts commonly limit H2S to about 4 ppm, so gas above that threshold must be sweetened and is treated operationally as sour. Some definitions use higher processing thresholds.
Is CO2 what makes gas sour?
Not by itself. Sourness specifically refers to hydrogen sulfide. Carbon dioxide is an acid gas that often accompanies H2S and is removed in the same treating step, and high-CO2 gas is corrosive, but gas is labeled sour because of its H2S content.
What role does SCADA play in sour gas operations?
Operators continuously watch H2S detectors, amine-unit parameters, and inlet gas quality. A cloud SCADA system such as Merobix can consolidate those signals from field controllers over Modbus, DNP3, or OPC UA so remote engineers monitor treating performance and site H2S status, while the safety trips remain in dedicated local hardware.
Can sour gas be flared?
Combustion converts H2S into sulfur dioxide, which is itself a regulated pollutant, so flaring sour gas is constrained by environmental permits and often by dispersion modeling of the plume. Some jurisdictions restrict it tightly or require specific combustion arrangements. Whether and how a given site may flare is a permit question - the answer lives with the operator's environmental and regulatory staff, not in a rule of thumb.
Why is smell not an acceptable H2S detection method?
Because H2S causes olfactory fatigue: at hazardous concentrations it rapidly deadens the sense of smell, so the gas can be present and getting worse while a person smells nothing. Every sour-site protocol therefore treats odor as irrelevant and relies on fixed detectors and personal monitors, backed by routine bump testing to prove the sensors respond.
Sources and verification
This page references the protocol specifications published by the organizations below. Editions, product capabilities, and documentation change over time - confirm current requirements and specifications directly with the source.
- Modbus Application Protocol Specification - Modbus Organization
- Overview of DNP3 (IEEE Std 1815) - DNP Users Group
- OPC Unified Architecture Specification (IEC 62541) - OPC Foundation
Merobix is not affiliated with, endorsed by, or sponsored by these organizations; their names are used only to identify the standards and products discussed.
Automation services
Need help turning this into a working system?
Merobix integrates SCADA, programs Allen-Bradley and Siemens PLCs, and designs and fabricates industrial control panels.
Meeting requests are reviewed before confirmation.