What Does EPA OOOOb Fugitive Monitoring Require?
OOOOb pushes fugitive emissions monitoring beyond an occasional walkaround into a scheduled, documented program at well sites and compressor stations. This page explains, at a practitioner level, what that program has to accomplish - finding leaks on a defined cadence, fixing them within a required window, and keeping records that prove both - without reproducing the rule text. It is written for the person who has to actually run the surveys and defend the records, not for the legal filing.
OOOOb Fugitive Monitoring in one line: OOOOb fugitive monitoring requires operators of affected well sites and compressor stations to survey for fugitive emissions on a recurring schedule using an approved detection method, repair leaks that are found within a defined timeframe, verify the repair, and keep records of each survey, finding, and repair. The core loop is survey, find, tag, repair, reverify, document - performed on a cadence rather than only when a problem is noticed.
The Survey Obligation on a Schedule
The heart of the requirement is that monitoring happens on a defined recurrence, not on convenience. Affected sites must be surveyed for fugitive emissions at intervals set by the rule for the site type, using a detection method the rule accepts. The point of a fixed cadence is that leaks are transient and cumulative: a component that was tight last quarter can loosen, and only a scheduled sweep catches the population of new leaks that appears between visits.
The detection methods contemplated include optical approaches that let a surveyor see a plume that the eye cannot, and other approved techniques. The rule also opened a path for advanced continuous or periodic screening technologies as an alternative to the traditional walking survey, provided they meet the equivalency the rule sets. The mechanics of the traditional camera-based survey are covered in the explainer on optical gas imaging, and the alternative screening route is discussed under the continuous monitoring alternative.
What matters operationally is that the schedule is a commitment you have to meet and evidence. A missed or late survey is itself a compliance gap regardless of whether leaks existed, so the survey calendar becomes a managed obligation. Treating it like a preventive maintenance schedule - planned, tracked, and closed out - is the practical way operators keep it from slipping, especially across a fleet of remote sites where a single field visit is expensive.
Finding, Repairing, and Reverifying Leaks
When a survey identifies a leak, the obligation shifts from detection to closure. The leaking component is tagged, a repair is attempted within the timeframe the rule allows, and the repair is verified by resurveying the component to confirm the leak is gone. This is the same survey, monitor, tag, repair, reverify cycle that underpins any credible leak program, and the discipline of documenting each stage is what turns a found leak into a closed compliance item rather than an open finding.
The rule recognizes that some repairs cannot be completed immediately without a shutdown, and it provides for delayed repair in defined circumstances, with the expectation that the component is fixed at the next appropriate opportunity and tracked until then. The operational risk is losing sight of a delayed-repair component; a leak that was properly deferred but never actually closed becomes a violation even though the delay itself was allowed. A tracking list that survives shift and personnel changes is what prevents that.
Reverification is the step that is easiest to skip and most important to keep. A repair is not complete until a follow-up survey confirms the emission stopped, because a torqued fitting or replaced seal can still leak. Recording the reverification result against the original finding closes the loop and produces the paired find-and-fix evidence that a compliance review looks for. Without the reverify record, even a genuinely repaired leak looks unresolved on paper.
The Records That Prove Compliance
OOOOb fugitive monitoring is judged as much on records as on field work, because the regulator was not present for the survey. Each survey needs to be documented with date, method, and coverage; each leak with its location, the date found, and the component; and each repair with the date attempted, the reverification result, and any delay justification. Together these build the paired record - this leak, found here, on this date, repaired and reverified by that date - that demonstrates the program actually ran.
The recordkeeping burden compounds across a fleet, and this is where a data platform earns its place. A cloud SCADA system such as Merobix can hold the survey schedule, log each finding and its repair status, and preserve the timeline so that an open leak, a delayed repair, and a verified closure are all visible in one history rather than reconstructed from field notes at reporting time. The site continuous-monitoring approach and its data feed are described in the guide on continuous methane monitoring.
The reporting side rolls these records up into the periodic submissions the broader methane program requires. Because the underlying survey, finding, and repair events are already timestamped and stored, assembling a report becomes a summary of an existing record rather than a scramble to recreate one. For how those methane records feed a formal submission, see the explainer on the methane monitoring compliance report.
Frequently Asked Questions
How often does OOOOb require fugitive emission surveys?
The rule sets recurring survey intervals that depend on the type of affected site, so well sites and compressor stations have defined cadences rather than a single universal frequency. The important operational point is that the interval is a fixed obligation: the survey has to happen on schedule, and a missed or late survey is a compliance gap on its own. Operators should confirm the exact interval applicable to each affected facility against the current rule and their site classification, and manage the schedule like a tracked maintenance commitment.
What counts as an acceptable leak detection method under OOOOb?
The rule accepts defined detection methods, including optical gas imaging and other approved techniques, and it created a pathway for advanced continuous or periodic screening technologies to be used as an alternative where they meet the equivalency the rule requires. Which method is appropriate depends on the site and the approach an operator chooses to demonstrate compliance. The common thread is that the method must be one the rule recognizes and must be applied consistently and documented, not chosen ad hoc per visit.
What happens if a leak cannot be repaired right away?
The rule provides for delayed repair in defined circumstances, typically where an immediate fix would require a shutdown, with the expectation that the component is repaired at the next appropriate opportunity and tracked until it is closed. The operational risk is losing track of a properly deferred component so that it is never actually repaired, which turns an allowed delay into a violation. A durable tracking list that survives personnel and shift changes is the practical safeguard, along with recording the eventual repair and reverification.
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.