Automation Glossary • OOOO Storage Vessel Controls

EPA Storage Vessel Controls for Oil and Gas Tanks

Merobix Engineering • • 6 min read

Storage tanks are one of the most common ways an oil and gas site crosses into federal emission control obligations, and the trigger is not tank size but how much the tank could emit. This page explains how the EPA methane rules treat a storage vessel as an affected facility, what controlling its vapors involves, and why keeping the control genuinely in service - not just installed - is the part that monitoring has to prove. It is written for the operator deciding whether a tank needs controls and how to demonstrate they work.

Back to Blog

OOOO Storage Vessel Controls in one line: The EPA methane rules make a storage vessel an affected facility when its potential to emit crosses a defined threshold, at which point the operator must reduce emissions, typically by routing tank vapors to a control such as a vapor recovery unit or a combustion device and keeping that control operating. The obligation is judged on potential to emit, not tank volume, and compliance depends on demonstrating the control stays in service continuously.

The Potential-to-Emit Trigger

A storage vessel comes into scope based on its potential to emit, which is the amount it could emit given the liquid it stores, the throughput, and the conditions, rather than on its nominal capacity. This is why two tanks of the same physical size can land on opposite sides of the line: the one taking fresh, higher-vapor liquid at higher throughput has a larger potential to emit and can become an affected facility while the quieter tank does not. The determination is made per vessel against the rule's threshold.

Because the trigger is potential to emit, the analysis is done up front from the fluid properties and expected throughput, and it can change if operations change. A tank that was below the threshold can cross it when a well's production increases or the liquid composition shifts, which means the affected-facility determination is not a one-time event but something that follows the tank's actual service. Documenting the basis of the determination is part of the compliance record. The concept of the vessel as a regulated unit is covered in the explainer on the storage vessel affected facility.

The practical consequence is that operators need to know the potential to emit of their tanks before assuming they are unregulated. Skipping that analysis is a common way a site ends up out of compliance without realizing it: the tank looks ordinary, no one ran the number, and it turns out to have been an affected facility that needed controls. The determination belongs in the same file as the equipment inventory used for the rest of the methane program.

Controlling and Keeping the Control in Service

Once a storage vessel is an affected facility, the operator has to reduce its emissions, and in practice that means capturing or destroying the vapors the tank produces. Vapor recovery routes the vapors back into the process or to sales, keeping the gas rather than releasing it; a combustion device destroys them. Either way, the vapor space is controlled instead of vented to atmosphere, and the tank's hatches and pressure-relief points have to be managed so vapors actually reach the control rather than escaping around it.

The requirement is not merely to install a control but to operate it. A vapor recovery unit that trips offline, a combustor with an unlit pilot, or a thief hatch left open all defeat the control while the hardware sits nominally in place. The rule's expectation is continuous control during the periods it applies, so the compliance question is really about uptime and integrity of the vapor path, not about whether a device exists on the pad. This is the same in-service principle that governs flare controls, discussed under flare combustion efficiency.

This is why open hatches and stuck relief valves are such a recurring finding. They are not equipment the rule forgot; they are the failure modes that quietly turn a controlled tank back into an uncontrolled one. Managing them - keeping hatches closed, sizing the vapor path so the control is not overwhelmed on high-throughput days, and catching a control that has tripped - is the day-to-day substance of storage vessel compliance.

Monitoring That Proves the Control Works

Because the obligation is continuous control, the compliance evidence has to be continuous too, and that is a monitoring problem. The parameters that show a control is genuinely working - a combustor's pilot or flame status, a vapor recovery unit's run status, tank pressure, and hatch position where instrumented - are exactly the kind of points a SCADA system reads and trends. A control that trips at 2 a.m. and is noticed at the next site visit represents hours of uncontrolled emissions that a live monitoring point would have flagged immediately.

A cloud platform such as Merobix supports this by trending the control's health parameters and alarming when the control drops out, so a tripped vapor recovery unit or an extinguished pilot becomes an alert rather than a surprise found weeks later. Just as important, it retains the history, so the record can show what fraction of the time the control was in service, which is the evidence the continuous-control obligation actually turns on. Tank level itself is a related monitored point, tied to the overfill and containment concerns covered under secondary containment.

The payoff is that storage vessel compliance stops being a periodic inspection and becomes a monitored state. Instead of hoping the control was up between visits, the operator can show it, and can respond to a dropout in minutes rather than days. That continuous demonstration is what the affected-facility obligation is really asking for, and it is far easier to defend with timestamped data than with a maintenance log written after the fact.

Frequently Asked Questions

Does every oil tank need emission controls under the EPA rules?

No. A storage vessel becomes an affected facility, and therefore needs controls, only when its potential to emit crosses the rule's threshold. Potential to emit depends on the stored liquid, its throughput, and conditions rather than on tank size, so tanks below the threshold are not affected facilities. The mistake to avoid is assuming a tank is exempt without running the potential-to-emit analysis, because that number, not the tank's appearance or capacity, decides whether controls are required.

What does it mean to keep a storage vessel control in service?

It means the vapor control actually operates during the periods the rule applies, not merely that a control device is installed. A vapor recovery unit that trips offline, a combustor with an unlit pilot, or an open thief hatch all defeat control even with the hardware in place. The rule's expectation is continuous control, so compliance turns on the uptime and integrity of the vapor path. Monitoring the control's status and catching dropouts quickly is what keeps a control genuinely in service rather than nominally installed.

Can a tank become an affected facility after it is already in service?

Yes. Because the trigger is potential to emit, a tank that was below the threshold can cross it when production increases or the liquid composition changes, so the affected-facility determination follows the tank's actual service rather than being fixed at installation. This is why the analysis should be revisited when operations change materially. Documenting the basis of each determination, and updating it when throughput or fluid properties shift, keeps a site from unknowingly operating an uncontrolled affected facility.

More in Pumps, Compressors & Process Equipment
Storage Vessel Affected Facility  •  Elevated Storage Tank  •  Chilled Water Thermal Storage Monitoring  •  Tank Turnover  •  API 510 Program Elements  •  All Pumps, Compressors & Process Equipment →
Free SCADA operator training
Merobix University - 70 video lessons & 261 quiz questions, from first login to compliance reporting. No demo call required.
Start free →