A huge amount of automation in the oil field runs on pressurized natural gas rather than electricity, and that convenience comes with a cost: the controllers that use it vent gas as part of how they work. A gas-driven pneumatic controller uses well-site natural gas as its power supply, and much of that gas ends up in the atmosphere. This guide explains how pneumatic controllers emit gas and the difference between high-bleed, low-bleed, and intermittent devices.
Pneumatic Controller Emissions in one line: Pneumatic controller emissions are natural gas released by gas-driven instrument controllers as they operate. These controllers use pressurized well-site gas to sense and actuate valves for level, pressure, and flow control, and they vent that gas to the atmosphere either continuously (bleed) or in bursts when they actuate. They are classified as high-bleed, low-bleed, or intermittent-vent depending on how much and when they release gas, and collectively they are a major and heavily regulated emission source.
At remote sites without grid power, it has long been simplest to run instrumentation on the one energy source that is everywhere on a gas facility: the pipeline gas itself. A pneumatic controller taps pressurized natural gas as its supply, uses that pressure to sense a process variable and drive a control valve, and - critically - exhausts gas to atmosphere as part of its normal operation. The gas is not leaking from a fault; venting is designed into how the device functions.
That is the essential point about pneumatic controller emissions. Because the working fluid is natural gas rather than instrument air, every exhaust of that fluid is a methane and VOC release. Multiply one modest controller by the thousands of them spread across a producing basin, and the aggregate becomes one of the largest emission sources in the upstream sector, which is exactly why these devices attract so much regulatory attention.
Understanding this makes the mitigation options obvious in hindsight: either change what the controller vents (from natural gas to air), change how much it vents (low-bleed or intermittent designs), or eliminate the vent entirely (electric or self-contained devices). Those alternatives are the subject of the zero-bleed page.
Continuous-bleed controllers vent gas steadily as part of maintaining their control signal. A high-bleed device releases gas at a relatively high continuous rate; a low-bleed device does the same thing but is engineered to vent far less continuously. Swapping a high-bleed controller for a low-bleed one, where the application allows, cuts emissions substantially without changing the basic gas-driven design, which is why low-bleed retrofits became an early and common step.
Intermittent-vent controllers work differently. Instead of a steady bleed, they release gas only when they actuate - when a level or pressure crosses a threshold and the controller strokes a valve. Between those events they ideally emit little or nothing. Their emissions therefore depend heavily on how often the process makes them actuate and on whether they seal tightly between events; a healthy intermittent device that is cycling rarely emits far less than one that is cycling constantly or leaking through when idle.
The classification matters because it drives both regulation and estimation. Rules distinguish among these types, and emission inventories apply different assumptions to each. An accurate site inventory depends on knowing which controllers are high-bleed, low-bleed, or intermittent, and, for intermittent devices, how frequently they actually cycle.
For intermittent-vent controllers especially, emissions are tied to behavior that a control system can observe: how often the associated valve strokes, and whether the process is cycling normally or thrashing. A dump valve that is chattering, or a controller actuating far more than its process should require, is both a mechanical problem and an emissions problem, since each actuation vents gas. The actuation pattern is a window into both.
A cloud SCADA platform like Merobix helps by trending the valve movements and process variables these controllers manage - tank and separator levels, dump cycles, and pressures - so an operator can spot a controller cycling abnormally often or a device that seems to be venting when it should be idle. Merobix does not directly measure the cubic feet of gas a controller bleeds, but by revealing abnormal actuation and process behavior it points operators to controllers that are both malfunctioning and emitting more than they should.
That behavioral visibility complements the fleet-level view. Knowing which sites still run high-bleed devices, and seeing which intermittent controllers are cycling excessively, helps operators prioritize where a low-bleed swap, a repair, or a conversion to a non-emitting alternative will cut the most gas - turning a diffuse, hard-to-see source into targeted action.
Because they use pressurized well-site natural gas as their power source instead of electricity or instrument air. The gas provides the pressure the controller needs to sense a process variable and stroke a valve, and exhausting that gas to atmosphere is part of how the device operates. It is a designed release, not a leak, which is why switching the working fluid or the device type is the way to cut it.
Both are continuous-bleed devices that vent gas steadily to maintain their control signal, but a high-bleed controller releases gas at a much higher continuous rate than a low-bleed one. Replacing high-bleed controllers with low-bleed models, where the application allows, substantially reduces emissions while keeping the same basic gas-driven design, which made it a common early mitigation step.
It is a controller that releases gas only when it actuates - when a process variable crosses a threshold and it strokes a valve - rather than bleeding continuously. Between actuations it ideally emits little. Its emissions depend on how often the process makes it cycle and how well it seals when idle, so a device cycling constantly or leaking through when it should be closed emits far more than a healthy one cycling rarely.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.