As states have tightened their focus on wasted and emitted gas, more of them now require operators to file a monthly report of exactly how much gas they flared and vented, broken down by why it happened. The flaring and venting report is that filing. It is not simply a total; it asks the operator to separate routine flaring from upset and maintenance flaring, to distinguish flared gas from vented gas, and increasingly to show a gas-capture performance figure against the total produced. Because these categories carry different regulatory weight, and because routine flaring in particular is under pressure to shrink, how volumes are measured and how events are classified determine whether the report is a defensible measured account or a contested pile of estimates. This page covers what volumes the report captures, how the categories differ, and why a metered flare header combined with categorized event logs turns the filing from estimate-heavy into measured.
Flaring and venting report in one line: A flaring and venting report is a periodic filing, often monthly, in which an operator reports the volumes of gas flared and vented from a lease or facility, categorized by cause such as routine, upset, and maintenance flaring, and distinguishing flared from vented gas. Many states now use it to track wasted gas and to measure gas-capture performance against total production. Metering the flare header and logging each flaring and venting event with its cause turns the report into a measured, defensible filing rather than one built from estimates.
The flaring and venting report captures two related but distinct quantities: gas that was burned in a flare and gas that was released unburned to the atmosphere. The distinction matters because vented gas, being uncombusted, has a very different environmental and regulatory profile than flared gas, and regulators generally treat venting as worse. An operator has to report each separately, which means the field has to be able to tell how much gas went to the flare and burned versus how much was released through a vent, rather than lumping all non-sold gas together.
Within flaring, the report typically asks the operator to categorize by cause, because not all flaring is treated equally. Routine flaring, the ongoing flaring of associated gas that could in principle be captured, is the category under the most pressure and is often subject to limits or reduction targets. Upset flaring, driven by equipment failures or process trips, and maintenance flaring, associated with planned work, are treated as more excusable because they are episodic and tied to specific events. Reporting the same total under the wrong category can misrepresent an operator's performance and can be the difference between compliance and a violation.
Increasingly the report also serves as the basis for a gas-capture percentage, comparing the gas an operator captured and sold against the total it produced, with flared and vented volumes representing the shortfall. This turns the report from a simple waste tally into a performance metric that states use to hold operators to capture targets. Because the capture percentage depends on both the produced volume and the flared-and-vented volume being measured accurately, the report's role as a performance yardstick raises the stakes on measurement quality: a poorly measured flare volume distorts the capture figure the operator is judged by.
Distinguishing routine from upset from maintenance flaring in the report is not a formality; each category answers to different rules and carries different consequences. Routine flaring is what regulators most want to eliminate, so a well that shows large routine-flaring volumes month after month attracts scrutiny and may face limits, permit conditions, or curtailment. Reporting flaring accurately as routine is uncomfortable but necessary, because the pressure on routine flaring is the point of tracking it.
Upset flaring, arising when a compressor trips, a sales line goes down, or a process upset forces gas to the flare, is episodic and tied to identifiable events, and regulators generally accept it as a consequence of keeping operations safe, provided it is genuinely upset-driven and not routine flaring relabeled. The report has to tie upset volumes to the events that caused them, so an operator who claims a volume was upset flaring should be able to point to the trip or failure that produced it. Without that linkage, an upset claim is just an assertion.
Maintenance flaring, associated with planned activities such as blowdowns for maintenance or commissioning, is likewise event-driven and generally accepted when it corresponds to scheduled work. The common thread across upset and maintenance categories is that they are defensible only if the operator can associate the flared volume with a specific, documented event. This is precisely why the report becomes contentious when volumes are estimated and events are not logged: an operator who cannot show which flaring was routine and which was event-driven has no basis to defend the favorable categories, and regulators may treat unexplained flaring as routine by default.
The reason flaring and venting reports are so often estimate-heavy is that much flaring historically was not metered; operators estimated flared volumes from the gas that should have been sold but was not, or from engineering assumptions about the flare's throughput. Those estimates are inherently soft, and when a report is built from soft numbers, every figure is arguable and the category breakdown rests on judgment rather than evidence. The fix on the volume side is a flare header meter that measures the gas actually routed to the flare, turning the flared volume from an inference into a reading.
Measurement alone is not enough, though, because the report also demands that each volume be categorized by cause, and a meter measures how much flared, not why. That is where event logging comes in. When each flaring and venting event is recorded with its cause, whether a routine condition, a specific compressor trip, a sales-line outage, or a scheduled maintenance blowdown, the metered volume for a period can be apportioned across the categories the report requires, with each category's volume tied to the events that produced it. The meter provides the how much; the event log provides the why.
Bringing the meter and the event log together in a monitoring platform is what makes the report defensible rather than contentious. Where a cloud SCADA platform such as Merobix trends the flare header flow continuously and logs the operational events, the trips, and the planned activities that drive flaring, the flared volume and its categorization are both grounded in captured data. An operator filing such a report can show the metered total and, for each upset or maintenance claim, the logged event that justifies it, while the routine remainder is what is left after the event-driven volumes are accounted for. That evidentiary chain turns a filing regulators would otherwise probe into one the operator can stand behind, and it is the difference between a measured report and an estimate the operator has to defend on faith.
Flared gas is combusted in a flare, while vented gas is released to the atmosphere unburned, and the report requires them to be reported separately. The distinction matters because uncombusted vented gas has a worse environmental and regulatory profile than flared gas, and regulators generally treat venting as the more serious. The field therefore has to distinguish gas that went to the flare and burned from gas released through a vent rather than lumping all unsold gas together.
Because each category carries different regulatory weight. Routine flaring of associated gas that could be captured is under the most pressure and is often subject to limits or reduction targets, while upset flaring from equipment failures and maintenance flaring from planned work are treated as more excusable because they are event-driven. An operator has to be able to tie upset and maintenance volumes to specific events, or regulators may treat unexplained flaring as routine by default.
A flare header meter measures the gas actually routed to the flare, replacing soft estimates with a reading. Paired with an event log that records the cause of each flaring and venting event, the metered volume for a period can be apportioned across the routine, upset, and maintenance categories the report requires, with each event-driven volume tied to the trip or activity that produced it. That combination of a measured total and a documented cause turns the filing from an arguable estimate into a defensible measured account.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.