The standard LDAR walk-down survey has been the backbone of regulatory compliance for oil and gas facilities since the early 1990s. An OGI technician with a FLIR camera walks the site on a scheduled basis, sweeps through the equipment register, flags anything visible, logs the findings, and the facility generates a repair schedule. For the regulatory framework of the early 2000s, this worked. For the compliance environment of 2026, the model has structural problems that scheduled walk-downs cannot fix by simply doing more of them.
The Gap Is Not a Technology Problem
When operators talk about improving their LDAR programs, the conversation often goes immediately to whether a newer OGI camera has better sensitivity or whether drone-mounted imaging would speed up the survey. Those are real considerations, but they address the wrong bottleneck. The core problem with walk-down LDAR is not detection sensitivity during a survey. It is detection latency between surveys.
A quarterly OGI survey schedule means that in the worst case, a leak that begins the day after a survey runs for 89 days before the next camera sweep. At a compressor station running at typical throughput, an undetected seal leak over that period is not just a regulatory exposure. It is product loss, methane to atmosphere, and accumulated repair complexity as the underlying problem worsens. The camera can detect leaks at very low flow rates when it is pointed at the right equipment. But 89 days of pointing somewhere else produces the same outcome as a less sensitive camera: the leak continues.
What OOOOb Changed About This
The EPA's OOOOb final rule did not eliminate OGI walk-downs as an approved monitoring method. It preserved them for certain facility categories. But it also introduced a superemitter response program that creates consequences for leaks that are detected by third parties rather than by the operator's own program. An aerial survey contractor flying for another purpose, a satellite methane detection pass, or a community monitoring sensor can trigger a superemitter notification to EPA, and the operator has five days to acknowledge and begin investigation.
This is where the walk-down model breaks down most visibly. If your facility has a significant leak event and a third-party detection source reports it to EPA before your next quarterly survey, you are already in a reactive position. The notification has been filed. The investigation clock is running. The question of whether you had a monitoring program in place becomes secondary to the question of why the program did not catch the event before an external source did.
What Walk-Downs Are Actually Good At
This is not an argument that OGI walk-downs have no value. They have real strengths that continuous monitoring does not fully replicate. A trained OGI technician walking through a site can observe physical conditions that sensors do not capture: ice forming on valve bodies in cold weather indicating a pressure differential, unusual sounds near compressor rod packing, visual inspection of seals and connectors that may be developing wear patterns but have not yet become active leak sources. The human observation layer, combined with the camera, produces a different kind of information than a sensor array does.
Walk-downs are also well-adapted to the existing regulatory documentation framework. The survey report format, the component identification scheme, and the repair timeline tracking are all built around the walk-down output. Operators who have been running LDAR programs for years have internal processes tuned to this workflow. Continuous monitoring introduces new data formats, new alert types, and new repair verification workflows that require process changes, not just technology purchases.
The Monitoring Gap in Practice
When we have looked at detection timing across pilot sites, the pattern that emerges is consistent with the theoretical prediction: most events that generate a significant cumulative emissions volume are events that began between survey dates and ran until the next scheduled walk-down. The distribution is not uniform. Certain component types generate events at higher base rates, certain site conditions accelerate deterioration, and certain seasons produce more events than others. Quarterly surveys cannot adapt their schedule to this variation.
What we saw more often than expected was events that had already been detected by the operator's walk-down program, logged for repair, and where the repair had been completed, but where the underlying component had not been monitored again to verify that the fix held. In multiple cases, the initial repair did not fully seal the fitting, and the leak continued at a lower rate until the next quarterly survey. Continuous monitoring would have caught the partial repair within days. Walk-down detected the original event, created the work order, and then had no visibility into the repair outcome for the next 60 to 90 days.
Combining Walk-Down and Continuous Monitoring
The operators we work with who have gotten the most value from continuous monitoring have not replaced their walk-down programs. They have restructured the role that each method plays. Continuous monitoring handles the between-survey gap: it catches the events that start after a survey day and ensures that repair verification is not a three-month wait. Walk-down surveys are retained for their physical inspection value, applied at lower frequency and used as a deeper equipment health assessment rather than as the primary detection mechanism.
This restructuring also changes the economics. An operator who moves from quarterly to semi-annual walk-down surveys, enabled by continuous monitoring handling the coverage gap, often finds that the combined cost is comparable to the previous walk-down-only program while the coverage is substantially better. The OGI contractor time gets redirected toward more valuable uses: equipment condition assessment, complex source identification in multi-component areas, and post-repair verification of large events.
What Does Not Change
Continuous monitoring does not reduce the importance of well-maintained equipment records. Sensor data is only as useful as the component inventory it maps to. If your equipment register is not current, an alert that a sensor identifies as a compressor fitting may actually correspond to an instrument tap that is located 15 feet away from where the register says it is. Getting the physical layout right before deploying sensors prevents a lot of unnecessary field effort chasing locations that do not match the alert data.
The regulatory documentation obligation also does not change. Monitoring data from a continuous system still needs to be retained, organized, and producible on request. An alert that is detected, acknowledged, and then lost in an inbox before generating a work order represents the same compliance gap as a missed walk-down. The technology improves the detection side. The process discipline and documentation are still on the operator.
This article reflects operational patterns observed during early-access pilot deployments. Specific outcomes will vary based on site configuration, equipment condition, and operational parameters. The observations described here are illustrative, not guaranteed results. This is not a substitute for qualified environmental compliance review.