Subpart OOOOa LDAR Compliance: Walking Path Verification and OGI Inspection Documentation

TL;DR: Subpart OOOOa’s OGI inspection requirements are specific. Inspectors must physically walk a defined path around equipment and view every component from multiple directions. That’s the inspection. Proving it happened, position by position, timestamped and geolocated, is the challenge traditional LDAR programs can’t meet. Here’s what the regulation actually requires and why GPS-enforced inspection records are the only documentation that holds up when enforcement disputes it.

From OOOO to OOOOa: The Regulatory Timeline That Matters

Before you can build an adequate OGI compliance program, you need to know which Quad O rule governs your equipment. The answer depends entirely on construction date.

40 CFR Part 60 Subpart OOOOa covers oil and natural gas equipment constructed, modified, or reconstructed on or after June 3, 2016. Its predecessor — Subpart OOOO, promulgated in 2012 — applies to equipment built or modified on or after August 23, 2011. OOOOa substantially expanded covered equipment categories and added semi-annual OGI survey requirements for compressor stations covering pneumatic controllers, storage vessels, and associated piping.

Subpart OOOOb and subsequent rulemaking have continued tightening these requirements. The practical result: operators managing multi-vintage facilities may have equipment under three different subparts simultaneously — each with its own monitoring frequency, accepted detection methods, and documentation standards.

That’s not a corner case. It’s the normal compliance environment for any oil and gas operator with assets built across multiple construction cycles. Understanding which subpart governs which equipment is the foundational step. Build your OGI program on the wrong rule, and the inspection records you produce won’t satisfy the applicable requirement — even if every inspection was conducted thoroughly.

What OOOOa Actually Requires for OGI Inspections

OOOOa’s optical gas imaging inspection requirements are performance-based. The standard describes what an inspection must accomplish, not just that it must happen.

Specifically, the regulation requires that OGI inspections use a camera meeting the applicable performance specifications, be conducted at the required monitoring frequency (semi-annual for most covered compressor station components), and monitor each component by viewing it from multiple directions — enough to detect leaks from any angle of emission.

That last requirement is where most documentation programs fall short.

A single-pass survey that views a valve from one side doesn’t satisfy the regulation. The inspector must position themselves so that emissions from any direction would be visible in the OGI camera’s field of view — which means walking around equipment, not past it. EPA has been explicit in guidance documents that the walking path is a required element of a compliant survey, not an optional best practice. Records that don’t demonstrate path compliance are inadequate records under OOOOa. Period.

LDAR at Compressor Stations: The Walking Path Requirement

At a compressor station, the walking path requirement means defining a route that achieves complete visual coverage from all required angles. That route isn’t federally standardized — it’s specific to each station’s equipment layout, the location of emission sources, and the physical geometry of the site.

A compliant path for a typical compressor unit might include:

Front of unit — inlet and outlet piping assemblies
Each side of the unit — valve assemblies and associated connections
Rear of unit — exhaust system and rear-facing piping
Additional positions for elevated components — pipe rack connections, elevated flanges where visual access requires a closer position

Every position must give the OGI camera clear visibility of the components assigned to it. The combination of positions must cover all components from all required angles. Neither condition is optional.

Here’s the operational tension. Walking the path isn’t difficult. Proving you walked it is.

Paper logs and non-location-verified digital forms record that an inspection was conducted on a date, that a named inspector was assigned, and that the form was completed. They don’t record that the inspector was physically standing at position 3 behind the unit when they scanned the rear piping assembly. An inspector who completed the form from the truck produces a record that looks identical to one produced by an inspector who followed every required position.

That ambiguity is what creates regulatory exposure — not the inspection itself, but the inability to prove it was done at the right places.

The Documentation Gap Traditional Systems Can’t Close

An EPA inspector reviewing OGI monitoring records isn’t looking for a completed form. They’re looking for evidence that the inspection satisfies the standard — that the methane leak detection methodology actually covered what it’s required to cover.

Paper logs and unverified digital records establish that an inspection was conducted on a specific date, that a person was assigned, and that the form shows no detections. They can’t establish that the inspector physically visited each required position, that each component was viewed from the required angles, or that the walking path covered the entire monitored zone.

When enforcement targets a facility for alleged inadequate OGI methane leak detection, whether the path was actually walked often comes down to this exact documentation gap. The facility asserts compliance. The agency has documentation that neither supports nor contradicts the assertion. Under the Clean Air Act, the burden falls on the facility to demonstrate compliance with NSPS monitoring requirements.

The financial consequence isn’t abstract. Civil penalties under 42 U.S.C. § 7413 can reach $70,117 per day per violation at current penalty schedules. Violations involving failure to conduct adequate monitoring under NSPS requirements have been a consistent component of EPA oil and gas enforcement actions. At a multi-station operation, a handful of inadequately documented OGI surveys across a few inspection cycles produces a penalty calculation that moves fast.

GPS-Enforced Inspection Points for OGI Programs

GPS-enforced inspection mapping addresses the documentation problem at its root. Instead of records that show what the inspector wrote down, you get records that show where the inspector was when they wrote it — point by point along the walking path.

The setup is straightforward. For each compressor station or monitored equipment zone, you configure inspection points that correspond to the required OGI walking path positions. Each point carries GPS coordinates tied to its physical location, a proximity threshold (typically 3 to 10 meters depending on site conditions), the inspection questions associated with that position, and capacity for OGI photo or video upload.

During the survey, the mobile platform continuously validates the inspector’s location. At each inspection point, the system verifies GPS position before the form unlocks. If the inspector is outside the configured threshold — at the wrong position, still en route, anywhere other than the required location — the form doesn’t open.

The record that results doesn’t show that an OGI survey was completed. It shows, point by point, that the inspector was physically present at each required position at a documented time. That’s the evidentiary standard paper logs structurally can’t produce.

There’s also a practical workflow for access constraints — because they happen in real field conditions. A valve assembly temporarily blocked by maintenance equipment, an area under short-term construction, a component with restricted access for safety reasons. The distance deviation workflow lets the inspector document the constraint with a reason code rather than leaving an unexplained gap. The record shows the constraint was encountered and handled. That’s defensible. A silent gap isn’t.

The EHSTracks® LDAR inspection software implements GPS-enforced inspection points with zone-level distance validation for OGI and OVA programs. For oil and gas operators managing programs across multiple compressor stations and production facilities, EHSTracks goes beyond just LRAR inspection compliance and offers modules that cover the full program scope (LDAR, SPCC, Stormwater, Waste, and Safety) in a unified multi-site platform.

Method 21 Integration in Multi-Method Programs

Many LDAR programs under OOOOa use both OGI and EPA Method 21 as detection methods. Different equipment types may require different methods, some permits allow either with different triggering thresholds, and Method 21 is often used to quantify a detection that OGI initially flagged.

In those programs, keeping OGI and Method 21 records synchronized for the same components is an ongoing administrative challenge. A component that registers a detection on the OGI survey needs a corresponding Method 21 reading in its history. A component on Delay of Repair status needs that status documented in both monitoring channels. Inconsistency between the two channels doesn’t just create data management headaches — it creates enforcement exposure when the complete component history is reviewed.

Synchronization is handled at the platform level. In EHSTracks®, after a successful Method 21 inspection for a given frequency group, the system automatically copies M21 answers to the corresponding OVA frequency group. Both channels stay in sync without manual reconciliation. The component history is internally consistent whether it’s reviewed by a site coordinator or an EPA inspector pulling records.

Method 21 also requires calibration of the monitoring instrument at the start of each survey using appropriate calibration gases. EHSTracks® requires a completed calibration wizard before the inspector can begin recording component readings — structurally enforcing the calibration-before-inspection sequence rather than relying on the inspector to remember it. When records are submitted, the calibration documentation is already attached.

Corrective Action Requirements Under OOOOa

Every leak detected during an OGI survey starts a compliance clock. Under OOOOa, that clock runs in calendar days — not business days, not working hours — from the moment of detection.

Within 5 calendar days: First repair attempt. The attempt must be documented — who tried the repair, what was done, and whether it succeeded or failed. This is a deadline for attempting repair, not completing it. But the documentation requirement is binding regardless of outcome.

Within 15 calendar days: Successful repair, or a documented Delay of Repair (DOR) for components where repair within the standard window is technically infeasible. A valid DOR requires the name of the person responsible for the delay, the specific technical reason repair isn’t possible within 15 days, and the anticipated repair date. Missing any element makes it an inadequately documented open leak — not a valid DOR.

Follow-Up Monitoring (FUM): After a successful first repair attempt, the component requires follow-up monitoring within a defined window to confirm the repair held. FUM timelines are component-specific and must be tracked systematically. A component marked “repaired” with no subsequent FUM record doesn’t have a clean closure history.

For programs using OGI video documentation of detected leaks, the corrective action record should include that visual evidence alongside the written description of the source, location, and component details. The complete record connects what was seen to what was done — detection through verified closure.

When Enforcement Disputes the Walking Path

Enforcement actions involving OGI walking path deficiencies typically arise in two distinct contexts. The documentation needed to defend each one is different.

Context 1: An EPA inspector observes a detectable emission at a facility. The facility’s most recent OGI records show no emissions at that location. The agency’s next question: was the walking path followed? GPS-verified inspection records showing the inspector’s confirmed position at each required location — with timestamps at each point — let the facility demonstrate that the path was followed and that the emission wasn’t present or detectable at the time of the survey.

Without those records, the facility is asserting compliance rather than demonstrating it.

Those aren’t the same thing in an enforcement conversation.

Context 2: A records review without an observed emission. Here the question is purely documentary — whether the existing records adequately support the facility’s attestation of OOOOa compliance. Facilities whose OGI records show only that a survey occurred on a given date, with a completed form and a “no detections” result, may find that documentation insufficient under enhanced scrutiny. Records that include GPS-verified positions at each inspection point — with timestamps — provide substantially more defensibility.

The risk compounds at scale. For oil and gas EHS compliance programs covering multiple compressor stations across a region, the documentation standard applied to any individual survey becomes the de facto standard for the entire program during an investigation. Building GPS-verified records into routine OGI operations is far easier than reconstructing defensible documentation after enforcement attention arrives.

FAQ

What is the difference between Subpart OOOO and Subpart OOOOa?

Subpart OOOO applies to oil and gas equipment constructed or modified on or after August 23, 2011. Subpart OOOOa applies to equipment constructed, modified, or reconstructed on or after June 3, 2016. OOOOa expanded covered equipment categories, strengthened OGI monitoring requirements, and added semi-annual inspection requirements for compressor stations. Equipment constructed between those two dates may fall under OOOO but not OOOOa — so construction date tracking is essential for any facility with multi-vintage assets.

What LDAR software supports GPS-verified OGI walking path inspections?

EHSTracks® LDAR inspection software supports GPS-enforced inspection points with zone-level distance validation for OGI and OVA programs. The platform verifies inspector location before unlocking inspection forms at each walking path position, producing timestamped, geolocated records at every point. For components that can’t be accessed during a survey, the distance deviation workflow documents the constraint with a reason code rather than leaving an unexplained gap in the record.

How does EPA define “complete visual coverage” for OGI inspections?

EPA guidance specifies that OGI inspectors must view components from multiple directions sufficient to detect emissions from any angle of emission. In practice, this means physically walking around equipment so all surfaces and potential emission points pass through the camera’s field of view during the survey. The specific walking path isn’t federally standardized — it depends on each facility’s equipment layout — but the combined positions must cover every component from every required angle.

What happens if a component is inaccessible during an OGI walking path inspection?

Inaccessible components require a documented skip record with the reason for inaccessibility. Under OOOOa, components that can’t be accessed during the required monitoring period may qualify for alternative monitoring provisions depending on the circumstances and applicable permit conditions. The documentation requirement is non-negotiable: an unexplained gap in the inspection record creates enforcement exposure regardless of why the gap occurred.

Can OGI video serve as the primary documentation for monitoring records?

OGI video is valuable supporting evidence — particularly for detected leaks and as a quality-of-inspection record. It doesn’t replace the required written monitoring record. OOOOa requires written records with component-level findings, inspection dates, and inspector identification. For detected leaks, video documents the emission source visually and should accompany the written corrective action record. It supplements the written record — it doesn’t substitute for it.

What records must be retained for LDAR programs under Subpart OOOOa?

Required records include monitoring records for each survey (date, inspector, component ID, result), leak records for detected emissions (detection date, description, instrument readings where applicable), repair records (first attempt date and outcome, DOR documentation if applicable, FUM results), calibration records for Method 21 instruments, and component inventory records. Minimum retention under OOOOa is 2 years from the date of each record. Some state programs require longer retention — check the rules applicable to your specific facilities.

What This Comes Down To

Here’s the practical reality: defensible OGI records are substantially easier to build into routine operations than they are to reconstruct after enforcement attention arrives.

The scenario that’s hardest to defend isn’t one where the inspection was poorly done. It’s one where the inspection was done correctly, but the documentation doesn’t show it. Paper logs and non-location-verified forms leave that gap open on every survey. GPS-enforced inspection points close it.

Start with your highest-risk compressor stations. Configure walking path positions as inspection points, set proximity thresholds to match the site layout, and verify each point maps to the OGI positions your program already requires. The records your team produces from that point forward won’t just show that a survey was completed — they’ll show it was done at the right positions, in the right sequence, with a timestamp at every stop.

That’s the documentation standard that holds up when it has to.

Contact us to schedule a demo today, so that you can ensure that your subpart OOOO compliance program can run like a well oiled machine.

News