The window is not a permission slip — it needs a cause, a timeline and an end point. Log the event as it happens: reason code, start, stop, volume, who was responsible, what fixed it. The clock runs itself and the record prints.
One-time purchase. No subscription. No account. Works offline.
Pick the reason and the window comes with it. Elapsed time runs against that window and colour-codes itself: within window, approaching, or over. A blowdown and a pipeline curtailment are not the same clock, and the app does not pretend they are.
Record when the incident was resolved as well as when the flaring stopped. If flaring carried on after the cause was fixed, the app says so on the record instead of leaving you to explain the gap from memory months later.
Print a single event record for a question about one day, or a period roll-up that separates every reason code instead of blending it into one flare line — with every exigent-circumstance narrative written out in full.
| Reason code | Window used |
|---|---|
| Malfunction, including for safety | 72 hours |
| Repair or maintenance, including blowdowns | 72 hours |
| Bradenhead test, packer leakage test, production test, commissioning | 72 hours |
| Gas does not meet pipeline specifications | 72 hours |
| Temporary interruption — gathering or pipeline system | 30 days |
| Drilling / post-completion potential testing | State allowance you enter |
| Other | None assumed — written basis required |
Where flaring runs past 72 hours on an exigent circumstance, the app opens a separate block for the written description, the start and end of the circumstance, the steps taken and the flaring stop time — then checks the test that actually applies, which is whether flaring ceased within 72 hours of the end of the exigent circumstance. It also states plainly that internal operational matters an operator is expected to plan for, such as personnel shortages from a labour dispute or illness, are not exigent circumstances.
EPA finalised amendments to NSPS OOOOb and EG OOOOc on 4 April 2026, extending temporary associated-gas flaring to 72 hours and adding the exigent-circumstance pathway. The flexibility came with a prescribed record: a written description, the steps taken, and start and end times for both the circumstance and the flaring, carried into the annual report.
Underneath that sit the state rules. Texas wants flared volumes on monthly lease-level production reports. New Mexico's gas-capture requirement is dated 31 December 2026. Colorado revised Regulation 7 in February 2026. One field record has to serve all of them, and it has to have been written at the time.
From Oil Rigs Now — trusted by oilfield professionals since 2011.
We build practical tools for the people who work in the field, not the office. No subscriptions. No data collection. Everything stays on your device.
No refunds. All sales are final. Instant access on purchase.
This is a recordkeeping aid, not a submission tool. It does not file anything with EPA, BLM, a state agency or a railroad commission, and it does not determine whether an event is compliant. The window durations it uses are those in the amendments to NSPS OOOOb and EG OOOOc finalised on 4 April 2026; those rules remain under reconsideration, so confirm the current limits and your own applicability before relying on them. State notes in the app are prompts to check your own obligations, not statements of them, and they do not replace your permit or professional judgement.