Operator self-reported flaring data vs. satellite-observed flare counts

Every state oil and gas regulator has the same pile of paperwork: monthly or quarterly flaring volumes, reported by the operator, rolled up by lease or by API number. Every ESG fund analyst building an emissions estimate for a portfolio company starts with the same 10-K footnote or sustainability report, which cites the same operator-submitted number. The question nobody likes to ask out loud is whether that number reflects what was actually burning in the field that month.

It often doesn't. The reporting chain has gaps built into it, and those gaps don't require anyone to be lying. A flare that runs for six days during a pipeline outage and gets logged as "intermittent" looks very different from one that burns continuously for a quarter. A well pad flaring under an exception permit may not show up in the routine-flaring tally at all. And in basins where metering on the flare line is sparse or estimated rather than measured, the reported volume is a modeled number dressed up as a measured one.

Why self-reported flaring numbers drift from what's burning

Three mechanics drive most of the drift. First, timing: self-reports are backward-looking, filed weeks or months after the activity, so a regulator reviewing a permit renewal today is working off data from last quarter at best. Second, aggregation: volumes get rolled up to the lease or facility level, which hides which specific flare stacks were lit and for how long. Third, incentive: nobody filling out a flaring report is rewarded for flagging more flaring than the minimum the rule requires them to disclose.

A field engineer logging flare events by hand across a dozen pads, on top of a full workload, is going to miss some and round others. The gap is structural, and it's the reason independent flare verification exists as a category at all, not an accusation against any one operator.

What a satellite flare count actually gives you

Night-time and SWIR imagery sees combustion directly. A lit flare stack produces a thermal signature that shows up against the dark background of a field at night, independent of what gets typed into a permit form later. Run that pass nightly across a monitoring area and you get a count: how many flares are lit tonight, and roughly how large each one is, without waiting on a filing deadline.

That doesn't replace metered volume data. Satellite imagery gives you presence, count, and relative size at the coarse resolution a wide-area nightly scan allows, not a precise cubic-foot reading on any single stack. What it gives a regulator or an analyst is a second, independent line of evidence that runs on its own schedule. If the nightly count for a lease shows flares burning on sixteen nights in a month and the self-report for that same lease describes flaring as occasional, that's a gap worth a phone call before the report gets filed as final.

Closing the gap: using both data sets together

Cross-referencing a nightly satellite count against the operator's self-reported volumes for the same lease and period turns a one-sided disclosure into a check. Where the two agree, the self-report stands on firmer ground. Where they diverge, that divergence is itself information, and it's the kind of thing a fund's ESG team can flag in an engagement letter, or a state agency can reference when it asks for supporting records on a permit renewal.

This is the use case Flare Monitoring is built around: a nightly count and size read on gas flares across a monitoring area, run as a proxy for production activity and an input to emissions reporting, so a regulator or ESG analyst has an independent reference sitting next to operator self-reports instead of standing in for them.

If your current flaring picture depends entirely on what gets filed, it's worth seeing what a nightly, independently observed flare count looks like for your monitoring area.