Emissions Reporting for Rigs: Subpart W and the Paper Trail

Emissions reporting used to be a back-office spreadsheet that nobody on a rig ever thought about. That ended the day EPA's greenhouse gas reporting program put oil and gas operations on a reporting schedule. Subpart W of 40 CFR Part 98 collects emissions data from the industry by the facility, and the data behind it comes from the field: fuel consumed, gas flared, vents measured, wells counted. The rig and the location are where that data starts, and the quality of the report is decided by the quality of the records made on location.

What the rig contributes to the report

On the drilling side, the biggest lines are fuel: the diesel burned by generators and pumps while the well is drilled, and the gas flared or vented when a well is flowed back or tested. The flare line is the one that gets the attention, because flaring is both a measurement problem and a public question: the volume of gas sent to the flare, the duration, and the reason it flared instead of being captured. Operators report these under the federal program, and a growing set of state programs run parallel requirements, so the data collected on location feeds two masters.

The diesel fuel management guide on this site is the fuel side of the same coin. The fuel tickets, the tank gauges, and the delivery records that catch theft and shrinkage are the same records that support the emissions calculation, because a rig that cannot account for its fuel cannot report its fuel-based emissions. The operations team that treats fuel records as cost data only is throwing away half the value of the same paperwork.

Measurement, calculation, and the audit trail

Subpart W is built on two approaches: direct measurement and calculation. Direct measurement means meters, continuous or periodic, that read the actual flow. Calculation means applying a formula to an activity value, like fuel burned or gas flared, times an emission factor. Either way the rule is the same: the numbers have to be supported by records that a reviewer can trace back to the source. A reported flare volume needs the flow meter read, the time logged, and the reason coded. A fuel-based number needs the delivery ticket, the tank inventory, and the hours run.

That traceability is where operations records enter the picture. The shift report data on this site and the morning report on this site carry the equipment hours, the pump runs, and the test periods that the emissions team needs. When the shift report is written by hand and the flare log is a notebook, the annual report becomes a reconstruction job, and reconstructed numbers are the ones that fail review.

The cost of getting it wrong

Emissions reports are verified, and the verification looks at whether the reported numbers are consistent, complete, and supportable. An operator that reports a flare volume with no supporting meter log, or fuel figures that disagree with the purchase records, gets the report flagged, and a flagged report is a cost, a delay, and an invitation for a deeper look. The operators that treat the annual submission as the deadline are building the report backward from memory; the ones that treat the field record as the deliverable are building it forward from data.

There is also a second audience: the buyers. Operators selling assets increasingly answer emissions questions in the data room, and the record retention discipline on this site is what makes the answer clean. The well file that includes the flare logs and the fuel tickets is worth more at the sale than the spreadsheet the seller was asked for twice.

If your flare logs are notebooks and your fuel records are a stack of tickets that never reconcile, book a working session with the OpsFlo operations team. Book a call here to see fuel, flare, and equipment-hour data captured at the source and assembled into a supportable emissions file.