It is August 11th, four days before the PA DEP semiannual deadline. Your Venango County filer opens the January-through-June folder and finds two months of produced-water hauler tickets missing from three legacy conventional wells. The DEP cross-references operator waste reports against hauler reports, and the hauler already filed. The gap is going to show up on a reconciliation report either way.
Pennsylvania production reporting runs through the DEP Office of Oil and Gas Management on a semiannual schedule: January-June is due August 15, July-December is due February 15 of the following year. Filings go through the DEP’s online Well Information System on the eFACTS platform. Operators report per-well oil, gas, produced water, brine, waste disposition, and well status. GreaseBook captures the daily data behind the six-month rollup. The operator still files through eFACTS. Pennsylvania’s semiannual filing is the odd one out in the broader oil and gas regulatory production reports framework, but the data chain underneath is the same.
Semiannual sounds forgiving compared to monthly. The trap is that six months of data has to hold up at once, and PA DEP’s waste-report cross-check catches gaps almost automatically.
What Pennsylvania Requires
The PA DEP requires operators to submit:
- Oil or condensate produced (barrels) per well
- Natural gas produced (MCF) per well
- Produced water (barrels) per well
- Brine and frac flowback (treated separately from produced water in some cases)
- Waste disposition: on-lease disposal, trucked to commercial facility, injection
- Well status for each well
- API number (Pennsylvania uses the federal API format)
Pennsylvania also requires waste reporting that goes beyond what many other states track. Every cubic yard of drill cuttings, every barrel of brine, every trip to a commercial treatment facility: it all ties back to the well and gets reported.
Filing Cadence and Deadlines
Pennsylvania operates on a semiannual production reporting cycle:
- First half (January through June) is due by August 15.
- Second half (July through December) is due by February 15 of the following year.
Filings go through the DEP’s online portal. Electronic filing is the standard for any operator with more than a handful of wells.
The Data Chain Over Six Months
Six months of well-by-well data requires discipline. If the data is only assembled at the deadline, you are trying to reconstruct February’s tank gauges in August. The chain that works:
- Pumper gauges recorded daily on every tank battery, tied to the wells feeding it.
- Run tickets per pull, with API numbers and volume.
- Gas meter reads monthly at minimum, weekly or daily on the higher-volume wells.
- Waste tracking: every truck hauling produced water, brine, or cuttings gets a ticket, and the ticket gets recorded.
- Shut-in days and workover days: tagged with the well they apply to.
- Purchaser statements: reconciled as they arrive, not in a panic every six months.
The operators who get into trouble with PA DEP filings are usually the ones who wait. When you open the six-month folder and realize the pumper’s notebook from March is missing, the hole is hard to fill retroactively. Any operator running state regulatory production reporting across multiple jurisdictions knows the same chain: the state that waits longest to collect is the state that hurts most when the data is late.
How GreaseBook Supports PA Operator Workflows
GreaseBook captures the daily gauges, run tickets, meter reads, and waste hauler tickets in real time. On the operator side, the data rolls up well by well, and the rollup is current on the 1st of every month rather than waiting for a deadline scramble.
When the August 15 or February 15 deadline comes, the data for the previous six months is already built. The filing prep is a review and reconciliation, not a reconstruction project. GreaseBook does not submit through the DEP’s online system: that submission stays with the operator and their PA filer: but the data arriving at the filer’s desk is clean.
A western Pennsylvania operator with 60 legacy conventional wells across three counties described it this way: “Semiannual sounds easy until the deadline hits and you realize you don’t know what half the gauges said in April. Now we know in April what they said in April, and August 15 is just a submission.”
GreaseBook keeps PA operators current on well-by-well gauges, runs, and waste volumes so the semiannual filing is routine.
See how GreaseBook works →Common Pennsylvania Filing Mistakes
- Waste volumes underreported. PA DEP tracks waste tightly. Missing a truck is missing a report line, and the state cross-references hauler reports with operator reports.
- Produced water lumped with frac flowback. For horizontal operators, these are tracked separately in some cases. Lumping them creates downstream issues.
- API errors on legacy conventional wells. Wells drilled in the 1930s or earlier sometimes have API numbers that don’t match what the pumper writes on tickets. Reconcile before filing.
- Filing one half and not the other. Operators who file January-June on time but miss August-December end up with compounding late-filing flags.
- Estimated volumes on shut-in wells. Shut-in wells get zero, not an estimate. Estimates invite audits.
Phrases to Eliminate in PA DEP Correspondence
When PA DEP asks about a variance (particularly on the waste-report cross-check), the language in your response shapes the follow-up. Measurement language closes findings. Vague language invites an inspector.
| Instead of… | Say… | Why |
|---|---|---|
| “We probably hauled that water in April” | “Produced water hauled to [facility] on [dates], ticket numbers logged to [well API] and reconciled to the facility receipt” | PA DEP cross-references operator waste reports against hauler and facility reports. “Probably” is the difference between a closed finding and an inspection. |
| “We lumped produced water and frac flowback together” | “Produced water and frac flowback are tracked separately on [well API]; [X bbl] produced water and [Y bbl] flowback for the reporting period” | For horizontal wells, DEP tracks these on different lines. Lumping them creates a multi-period reconciliation problem. |
| “The pumper missed a gauge on that well in March” | “[Well API] gauge on [date] is reconstructed from the adjacent-day readings and the run ticket on file” | Never tell DEP a record is missing if you can reconcile it. Show the reconstruction. |
| “We missed the August 15 deadline because summer was busy” | “Filed [X] business days after August 15; variance self-reported with the amendment and the six-month waste reconciliation attached” | DEP reads “we were busy” as low operator discipline. Self-disclosure with documentation lands differently. |
Identity Framing: What the Best Pennsylvania Operators Do
The best PA operators close each month as it ends rather than reassembling six months in early August. Every hauler ticket is logged to the well the week it leaves the lease, every purchaser statement is reconciled the week it arrives, and the August 15 and February 15 deadlines are submissions instead of rescues. The waste report cross-check is a formality, not a fire drill.
Wrong Fit for This Page
If you are EQT, Range Resources, or a Marcellus major with a full production accounting stack integrating your SCADA, waste tracking, and DEP reporting end-to-end, you don’t need help on the data capture side. This page is for the Pennsylvania conventional operator and the smaller unconventional independent: 5 to 200 wells, pumpers in the field, semiannual deadlines that still show up.
FAQ
Does GreaseBook file directly with DEP through eFACTS?
No. eFACTS is still where Pennsylvania operators file. GreaseBook is what makes the eFACTS upload take 15 minutes instead of 3 days, by giving you a clean per-well, per-month rollup to submit.
When are Pennsylvania DEP production reports due?
Twice a year. The first half (January through June) is due by August 15, and the second half (July through December) is due by February 15.
Do I file through the PA DEP online system?
Yes. Production reports go through the DEP’s online Well Information System, part of the eFACTS platform.
Is Pennsylvania reporting monthly or semiannual?
Semiannual. Pennsylvania stands out from most oil and gas states in that it collects production data twice a year rather than monthly.
Do Pennsylvania operators have to report waste and brine disposition?
Yes. PA DEP tracks waste volumes and disposition in detail, including drilling cuttings, produced water, brine, and frac flowback. The state cross-references operator reports with hauler and facility reports.
Related Pages
GreaseBook automates state production reports for operators filing in Texas, Mississippi, Alabama, Wyoming, and Michigan. Pennsylvania DEP filings still go through eFACTS, but the daily data chain that feeds them works the same way.
- Oil and gas regulatory production reports: the pillar guide to state and federal production filings.
- West Virginia WR-39: West Virginia’s production filing for operators active in both states.
- Oklahoma OCC Form 300R: Oklahoma equivalent for operators with leases in the mid-continent.
GreaseBook captures tank gauges, well tests, and run tickets at source, so Pennsylvania operators file with DEP from numbers that reconciled months ago. Because the DEP audit letter arrives on its own schedule.
See how GreaseBook works for Appalachian operators →