Blog/

What is MARS, and how does satellite flare data fit into it?

Dark, moody storm clouds filling a night sky.

The Methane Alert and Response System, known as MARS, is a program run through the UN Environment Programme's International Methane Emissions Observatory. It uses satellite data to spot large methane plumes, the kind that come from a single malfunctioning valve or an uncontrolled vent, and sends notification letters to the relevant national government and, where known, the operator. Regulators and ESG analysts who track MARS often ask where flaring fits into that picture, since flares and methane leaks are related but different problems.

What MARS actually flags

MARS works off plume detection. A satellite instrument tuned to methane absorption bands picks up a concentration spike over a point source, IMEO's analysts confirm it, and a notification goes out with a response window attached before the detection becomes public. That's a leak-detection and disclosure workflow built around point-source super-emitters. It doesn't count flares, size them, or track whether a stack that was lit last week is still burning this week.

Why flaring is a separate problem with its own evidence trail

Flaring is often legal, permitted, and reported through the same national inventories MARS detections get compared against. A regulator checking an operator's self-reported flaring volumes against something independent needs a running log: which flares were lit, on which nights, over a monitoring period. That's closer to a production proxy than a leak alert. Flare counts and flare-size trends track with throughput, so a sudden jump in the number of stacks burning across a basin, or a flare that's bigger than the volumes reported for that field, is the kind of signal an ESG fund analyst flags before the next sustainability report lands.

Where satellite flare data fits into emissions reporting

Night-time and SWIR imagery pick up the thermal signature of a flare stack independent of what the operator reports. Run that read nightly across a monitoring area and you get a log: which flares were burning, roughly how large, night over night. That log doesn't replace MARS, and it doesn't replace stack-level metering either. It sits next to both, as a source that's harder to argue with than a spreadsheet the operator filled in itself. For a regulator building an enforcement case, or a fund analyst sanity-checking a company's flaring-intensity claims, an independent nightly count means the self-reported number stops being the only number in the room.

The resolution on this kind of read is coarse, on the order of 250 meters or wider, so it's built for counting and sizing flares across a wide area rather than inspecting a single stack up close. That trade is worth making for cadence: a nightly pass beats a one-time plume alert when what you're building is a trend line, not a single incident report.

Putting the two together

A regulator or analyst working both sides of this gets a fuller picture. MARS covers the leaks nobody meant to have, and a nightly flare log covers the burning that's happening on purpose and is supposed to be declared. Used together, they close more of the gap between what gets reported and what's actually happening in the field.

If you're assembling that second piece, the flare side, Flare Monitoring builds its nightly read around counting and sizing flares across a monitoring area, as a stand-in for the self-reported numbers everyone else is working from. Get in touch if a nightly flare log would plug into the emissions picture you're already building.

Start a project

← Back to the blog