Blog/

Field notes: the basin where flare counts kept climbing after the pledge

Silhouette of an oil pump jack against a vivid orange sunset sky

A couple of years ago an operator in a mid-sized producing basin signed on to a zero routine flaring commitment, the kind that comes with a target year and a press release and a logo on a sustainability page. Reasonable people took it at face value. Then the flare count in that basin didn't go down. It went up, slowly, for three straight reporting cycles, and nobody on the outside noticed for a while because nobody was counting nightly.

This isn't a story about bad actors. Most of the time the gap between a flaring reduction pledge and what's burning at the wellhead isn't fraud, it's lag. Gas-to-wire infrastructure takes years to permit and build. A well comes online faster than the pipeline that would carry its associated gas, so the operator flares in the meantime and calls it "non-routine" because technically it is, this specific flare, this specific well. Multiply that across a drilling program and you get a basin where every individual flare has a defensible one-off explanation and the aggregate trend line still climbs.

The self-reported numbers rarely catch this in real time. Flaring volumes get rolled up quarterly, sometimes annually, and the reporting window is usually long enough that a six-month surge gets smoothed into a number that looks flat next to last year's. By the time a regulator or an ESG analyst sees the filing, the spike already happened and the operator has moved past it. The pledge gap is, almost always, a timing problem, and quarterly paperwork is built badly for catching timing problems while they're still happening.

What a nightly count does differently is boring in the best way. It doesn't care about explanations. A flare is lit or it isn't, it's bigger than last week or it isn't, and you get that read every night instead of every quarter. Watch a basin for a few months this way and the pattern usually tells you something the self-reported summary doesn't: whether the flaring is actually trending down toward the pledge, holding flat while someone waits out a permit, or quietly climbing because new pads are coming online faster than the gas-gathering system can absorb them.

That third case is the one worth sitting with, because it's the one that looks the most like compliance on paper right up until the aggregate numbers come due. An operator can point to specific curtailment events, specific pipeline delays, specific regulatory approvals still pending, and every one of those points can be true. The flare count climbing anyway is also true. Both things can be true at once, and the only way to see that is to count the fires, not read the narrative around them.

For an analyst building an emissions estimate or a regulator weighing whether a basin is tracking toward its stated reduction target, that distinction matters more than any single quarter's self-reported figure. A count and size read taken nightly, independent of what gets filed, is the closest thing available to watching the trend as it happens instead of after the fact. That's the gap a basin-level flare log is built to close, and it's worth a look at what a nightly read on an area's flares shows you before the next pledge anniversary rolls around.

The basin in question will probably hit its target eventually, or it won't, and either way the number that matters is the one counted while it's happening, not the one filed after.

Start watching a basin's flares the night they happen, not the quarter they get reported.

Start a project

← Back to the blog