A mid-size Permian Basin operator ran the numbers on their reported methane emissions across 140 flare points and did not like what they saw. Under the EPA's Waste Emissions Charge, their calculated exposure sat close to $2.8 million a year, driven less by how much gas they were actually wasting and more by how that gas was being measured in the first place. Eighteen months later, that exposure was gone, not through a rate reduction or an exemption, but through better data. This is the story of how continuous AI flare monitoring closed the gap, and Book a Demo to see the same approach applied to your flare fleet.
From $2.8M in Penalty Exposure to Zero, Without Touching Production
A composite look at how one Permian Basin operator used continuous AI flare monitoring to replace default emission factors with measured performance data, cutting Waste Emissions Charge exposure to zero across a 140-point flare portfolio.
The Challenge: A Penalty Built on Assumptions, Not Measurements
Like most operators reporting under Subpart W of the Greenhouse Gas Reporting Program, this facility had been calculating flare emissions using standard AP-42 style emission factors — generalized destruction efficiency assumptions applied uniformly across every flare, regardless of how well that specific flare was actually performing on a given day. The problem is that default factors assume a fixed destruction removal efficiency, typically around 98 percent, whether a flare is burning cleanly or is unlit, over-steamed, or under-assisted at the moment gas hits the tip. When those defaults run high relative to actual field conditions, the calculated waste emissions climb right along with them, and so does the charge.
This is not a problem unique to one operator. EPA's own reporting program has acknowledged the gap between emission-factor-based estimates and empirically measured emissions, which is part of why the agency has been actively soliciting ways to incorporate satellite and advanced measurement technology into Subpart W going forward. For any operator with a large flare-heavy footprint, that gap between assumption and measurement is not an abstract accounting detail — it is real dollars sitting on the compliance ledger every single reporting year until better data closes it.
Default Factors Overstate Real Performance
Standard emission factors do not distinguish between a flare running at 99 percent destruction efficiency and one intermittently under-assisted. Both get reported the same way, and neither reflects reality.
Periodic Audits Miss Short-Duration Events
Quarterly visual inspections and infrequent optical gas imaging surveys cannot catch a flare that goes unlit for six hours overnight, yet that single event can materially change the annual emissions total.
No Defensible Record When the Charge Is Calculated
Without continuous documentation, an operator has no way to show that a specific flare performed better than the default factor assumes, leaving no path to challenge an inflated exposure figure.
What Actually Drives a Destruction Efficiency Score
Destruction removal efficiency, or DRE, is the percentage of hydrocarbon gas sent to a flare that is actually combusted rather than released unburned. It is not a fixed property of a flare tip — it moves constantly based on how the flare is operating at any given moment, which is exactly why a single default assumption applied year-round misses so much of the real picture. The AI model built for this deployment pulled together three signal families to generate a continuously updated DRE estimate for every flare, replacing a single static number with a curve that tracked actual combustion quality hour by hour.
Flame Presence and Stability
Infrared imaging confirms whether a pilot and main flame are lit and stable, catching the intermittent unlit periods that a quarterly inspection has almost no chance of observing.
Assist Gas Ratio
Steam-assisted and air-assisted flares need the right ratio of assist medium to hydrocarbon flow. Too little assist causes smoking and incomplete combustion; too much can pull cold air into the flame and reduce efficiency.
Exit Velocity and Flow Rate
Gas exiting the tip too fast can blow the flame off entirely, while flow far below the tip's design range can cause flashback risk. Both extremes correlate with measurably lower destruction efficiency.
Combined, these three signal families let the model move each flare's reported DRE away from a blanket 98 percent assumption and toward a number that reflected what the sensors were actually observing — in this operator's case, an average of 99.2 percent across the fleet once tuning was complete, with a small number of chronically under-assisted flares identified and corrected along the way.
Value Beyond the Waste Emissions Charge
Eliminating the charge exposure was the headline result, but the same continuous monitoring layer created value the operator had not originally budgeted for. Once a facility has hour-by-hour visibility into every flare on its acreage, that data tends to get used for more than one purpose.
Flare Gas Recovery Prioritization
Continuous flow data at every flare made it possible to rank pads by recoverable gas volume, feeding directly into flare gas recovery investment decisions that had previously relied on rough estimates.
Faster ESG and Investor Reporting
Measured destruction efficiency and flaring volume by pad gave the sustainability team a defensible, auditable data set for investor disclosures instead of estimates built on industry averages.
Fewer Emergency Field Visits
Automatic alerts on lost pilots and under-assist conditions let field teams respond to a specific flare instead of running blanket rounds across every pad on a fixed schedule.
A Reusable Compliance Template
The reporting methodology built for this rollout is now the operator's standard approach for every new pad brought online, rather than a one-time project built to solve a single year's exposure.
Understanding the Waste Emissions Charge
The Waste Emissions Charge, created under the Methane Emissions Reduction Program, applies to facilities reporting more than 25,000 metric tons of CO2-equivalent emissions annually that exceed a statutory methane intensity threshold. The rate was set by Congress to step up over time, which means the cost of every ton of miscalculated excess emissions has been climbing every year the charge has been in effect.
| Reporting Year | Charge Rate per Metric Ton | Applies To |
|---|---|---|
| 2024 | $900 | Emissions Above Waste Threshold |
| 2025 | $1,200 | Emissions Above Waste Threshold |
| 2026 and Beyond | $1,500 | Emissions Above Waste Threshold |
At the 2026 rate, roughly 1,870 metric tons of over-reported excess methane is enough to generate a $2.8 million annual charge on paper. Reducing that exposure did not require this operator to physically eliminate that much gas — it required proving, with continuous field data, how much of that figure was measurement error rather than actual waste. That distinction is the difference between a compliance strategy built around chasing a moving penalty and one built around simply reporting what is really happening in the field, and it is the reason this approach scales to any operator with a large enough flare-heavy footprint to feel the charge.
The Solution: Continuous Destruction Efficiency Documentation
The response was not a lobbying effort or an appeal to EPA — it was a data project. The operator's EHS and data engineering teams worked together to build a monitoring layer that could stand behind every number in the next Subpart W filing, replacing a single facility-wide assumption with flare-by-flare measured performance.
Optical Sensor Deployment Across All 140 Points
Infrared imaging and flame-detection sensors were installed at every flare tip, feeding continuous pilot status, flame presence, and combustion quality data back to a central monitoring layer.
AI-Based Destruction Efficiency Scoring
Instead of a single assumed DRE value, the AI model calculated a continuous destruction efficiency estimate per flare, per hour, based on flame characteristics, assist gas ratios, and exit velocity.
Automatic Unlit-Flare and Under-Assist Alerts
Any flare showing a lost pilot, incomplete combustion, or an assist gas ratio outside the efficient operating range triggered an immediate alert to the field team, well before a scheduled inspection would have caught it.
Measured-Data Reporting Package for Subpart W
Continuous performance data was compiled into a defensible, time-stamped record that replaced the blanket default factor with the facility's actual measured destruction efficiency for the reporting period.
See What Your Own Flare Fleet Is Actually Reporting
iFactory's continuous monitoring layer replaces assumed emission factors with measured performance, giving you a defensible record before your next Subpart W filing.
Periodic Manual Audits vs. Continuous AI Monitoring
The gap between what a quarterly audit can see and what continuous monitoring sees is the entire story behind this case study. The table below lays out that gap point by point, and it is worth reading with one flare in mind: the busiest, highest-throughput point on your own portfolio, and how confident you would be today in its actual destruction efficiency at three in the morning last Tuesday.
| Factor | Periodic Manual Audits | Continuous AI Monitoring |
|---|---|---|
| Inspection Frequency | Quarterly or semi-annual | Every flare, every hour |
| Unlit Flare Detection | Only if inspection window overlaps | Immediate alert |
| Destruction Efficiency Basis | Assumed default factor | Measured, per-flare, per-hour |
| Audit Trail for Regulators | Sparse, snapshot-based | Continuous, time-stamped record |
| Emissions Reporting Accuracy | Systematically conservative-high | Reflects actual field performance |
Penalty Exposure, Quarter by Quarter
Coverage expanded across the flare portfolio in phases rather than all at once, and the calculated exposure dropped in step with each phase as more of the fleet moved from default-factor reporting to measured reporting. This phased pattern matters for any operator planning a similar project: the financial benefit does not wait for a ribbon-cutting moment at full deployment, it accrues continuously as each additional flare gets instrumented, which is part of why the business case held up even before the eleven-month rollout was complete.
What This Operator Almost Got Wrong
None of this went perfectly on the first attempt. A rollout of this size across a live production environment surfaces friction that a planning document rarely anticipates, and being honest about where the timeline slipped is as useful to another operator as the final result itself.
Treating It as an IT Project, Not a Compliance Project
Early planning routed the deployment through the data team alone. It only accelerated once the EHS and regulatory reporting teams were brought in to define exactly what Subpart W needed from the data.
Prioritizing the Wrong Flares First
The initial rollout order was based on installation convenience rather than exposure size. Re-sequencing to cover the highest-throughput flares first cut the timeline to material savings almost in half.
Underestimating Sensor Housing Requirements
Standard enclosures did not hold up to the heat and vibration at several high-throughput sites, causing early data gaps until hardened housings were specified for the remaining phases.
Waiting for a Full Year of Data Before Reporting
Measured data can be phased into reporting as coverage expands rather than held until every point is live, which is what let the exposure reduction show up well before full deployment finished.
We were reporting against an assumption, not against what our flares were actually doing. Once we had real destruction efficiency data behind every point, our exposure dropped almost exactly as fast as our coverage grew. It was not a negotiation with EPA — it was better math.
Frequently Asked Questions
What is the Waste Emissions Charge and who does it apply to?
The Waste Emissions Charge is a fee established under the Methane Emissions Reduction Program that applies to oil and gas facilities reporting more than 25,000 metric tons of CO2-equivalent emissions per year to the Greenhouse Gas Reporting Program, where those emissions exceed a statutory methane intensity threshold. The rate has stepped up each year since it took effect, reaching $1,500 per metric ton for 2026 and beyond, which means the cost of an inflated or inaccurate emissions calculation grows every reporting cycle. Facilities below the reporting threshold are not subject to the charge regardless of flare performance, and facilities that stay under the intensity threshold owe nothing even if they report a large absolute volume of production-related emissions.
How can better monitoring reduce a charge that is based on actual emissions?
Emissions reported under Subpart W are calculated, not directly metered at most facilities, which means the number that determines the charge often comes from a standard emission factor rather than a real-time measurement of a specific flare's performance. When continuous monitoring shows that a flare is destroying gas more efficiently than the default factor assumes, that measured data can replace the assumption, and the calculated emissions total — along with the charge based on it — comes down to reflect what is actually happening at the stack.
Why did this deployment take eleven months instead of rolling out all at once?
A 140-point flare portfolio spans multiple pads with different electrical infrastructure, network backhaul options, and physical access constraints, so sensor installation and validation happen in waves rather than a single event. Phasing the rollout by exposure size, starting with the highest-throughput flares, let the operator capture the largest share of the benefit early while the remaining sites were brought online in sequence.
Does continuous flare monitoring replace the need for physical flare tip maintenance?
No. Monitoring tells you when a flare is underperforming — an unlit pilot, an over- or under-assisted flame, a degraded tip — but a technician still has to respond and correct the physical issue. What changes is how quickly that response happens, since a continuously monitored flare surfaces a problem in minutes instead of waiting for the next scheduled inspection to catch it weeks later. For help designing a monitoring layer that fits your existing maintenance workflow, Book a Demo with our team.
Is this approach specific to the Permian Basin or does it apply elsewhere?
The underlying compliance mechanics apply to any facility reporting under Subpart W with a flare-heavy emissions profile, regardless of basin. The Permian's high flare-point density made the exposure and the savings especially visible in this case, but Eagle Ford, Bakken, and Gulf Coast operators reporting against the same default-factor assumptions face the same gap between calculated and measured performance. Our support team can walk through what this looks like for your specific reporting profile.
Turn Your Flare Data Into a Defensible Compliance Record
iFactory replaces default emission factor guesswork with continuous, measured destruction efficiency data across your entire flare portfolio.
