NSPS OOOOb does not just ask whether liquids unloading vented. It asks for the best management practices you planned, whether each one was actually performed on each event, a deviation entry with a start, a duration and a reason for every step that was not, and an annual count that puts all of it in one table. A pumper's notebook cannot produce that. This can, on a phone, at the wellhead, with no signal.
One-time purchase. No subscription. No account. Works offline.
Define your best management practices as an ordered list of named steps — create differential pressure, stage the operation, monitor at the wellhead, close the well to the atmosphere when flow stabilises, plus whatever your own procedure adds. Every event you log gets that exact checklist.
If an event vented to the atmosphere, every step must be ticked as performed or recorded as a deviation with its start, duration and reason. The app refuses to save it otherwise. A blank is how a good year becomes an enforcement finding.
Pick the reporting period and get it: each well that unloaded and vented, the total unloading operations, the number that vented with BMPs followed, the number with deviations, and a per-well table showing every event's step log. Printable, and exportable as CSV.
A live status view puts wells with unresolved deviations first, then wells with no BMP plan defined, then events missing required fields — so the gaps surface in March rather than the week the report is due.
For an affected gas well that unloads liquids and vents to the atmosphere, the standard is a set of best management practices that minimise venting: creating differential pressure before unloading, staging the operation, monitoring at the wellhead, and closing the well to the atmosphere as soon as flow stabilises. The alternative is routing the unloading gas to a closed vent system for 95% control, which the app records as a well's compliance route.
The practices only count if they were performed, and the record has to show which were and which were not. A step that was not performed is a deviation, and a deviation needs its own date and time, its duration and a reason.
The annual report identifies each well that unloaded and vented, gives the total number of unloading operations, the number that vented to the atmosphere with best management practices followed, and the number with deviations. When none vented with BMPs followed, the answer is zero — and zero is a number the report has to state, not a line left blank.
The app builds that summary from the events themselves and prints the explicit 0 where the count is none, so the figure comes from the record rather than from somebody's recollection of the year.
The unloading events are in the pumper's route sheets. The BMP plan is a paragraph in a procedure binder nobody opened this year. The deviations, if anyone noticed them, are in a text message. Then in the first quarter someone reconstructs a year of unloading operations into a table, and every figure in it is an estimate.
This is the record kept as it happens: one register, one plan, one step log per event, and a summary generated from the whole thing in a tap.
Every registered well sits in exactly one band, so the exposure is always on the first screen rather than found in February.
Well name, US Well ID (API number), field or lease, facility or pad, the unloading method used, and whether it complies via BMPs or a closed vent system for 95% control.
Plunger lift, plunger with automation, swabbing, velocity or critical-flow tubing, soaping, compression or differential pressure, manual blowdown, or another method you name.
Date and time started, duration, the person who conducted it, the method actually used on the day, and whether it vented to the atmosphere.
For every step in your plan, a tick that it was performed — or a deviation entry with the date and time the deviation began, how long it lasted and why.
Wells that unloaded and vented, total operations, vented with BMPs followed, vented with deviations, and a per-well event table with every step log in full.
Full JSON export and re-import so the record moves between devices and survives the retention period. CSV for the summary and the event detail.
Built to the same shape as our other field-compliance logs, so if your crew already uses one, this one reads the same on day one.
It does not file anything with the EPA or a state agency, does not decide which of your wells are affected facilities, does not estimate vented volumes, and does not replace 40 CFR part 60 subpart OOOOb, your permit or your own written procedure. It records what was done, by whom, when, and whether the plan was followed — and prints that record in the shape the annual report asks for.
Everything stays on your device. Nothing is uploaded, no account is created, and the app keeps working when the lease road has no bars.