Texas RRC Flare/Vent Exception Query Retrieval Provenance Worksheet

Direct answer

Give one official SWR 32 Flare/Vent Exception query attempt a neutral ID. Record its route, source-displayed criteria and values, visible statuses, access time, source limitation, retained reference, and only located, not located, or unverified. This proves how the query was attempted. It does not prove that an application applies to private mineral rights, flaring or venting occurred, an operator complied, or any property, production, royalty, value, offer, or transaction consequence exists.

Key takeaways

• Start from the official RRC Research Queries route and retain the complete SWR 32 public-query route chain.
• Record only source-displayed criteria, values, statuses, coverage, and navigation observed during the attempt.
• Keep the query, any result detail or attachment, current rules, and other RRC record channels as separate retrieval steps.
• Record access time, timezone, and source limitations for every retrieval step.
• Use only located, not located, or unverified, then stop before property, occurrence, compliance, environmental, production, valuation, legal, or transaction conclusions.

Public-record retrieval boundary. This article records one Texas RRC Flare/Vent Exceptions (Statewide Rule 32) Query retrieval attempt. It does not interpret an application, status, result row, attachment, property label, operator, date, location, exception, or rule. It does not establish that flaring or venting occurred, that an exception applies to a private interest, that an operator complied or failed to comply, or that a mineral owner has a property, title, lease, production, royalty, payment, value, offer, environmental, legal, or transaction consequence. It does not provide legal, title, land, tax, accounting, appraisal, engineering, geological, environmental, regulatory, or financial advice. MRX may have an economic interest in a later transaction; when that applies, the buyer relationship is disclosed in writing before an agreement is signed.

A Texas RRC Flare/Vent Exception query retrieval worksheet answers one narrow question: exactly how was one official SWR 32 public-query attempt performed? Record the entry route, source-displayed criteria labels, entered or selected values, visible status and result labels, retained reference, access timestamp and timezone, source limitations, and one bounded retrieval status.

Use only located, not located, or unverified. Those terms describe the retrieval attempt. They do not decide whether an application is complete, current, accurate, applicable, approved, connected to a private interest, or evidence of an occurrence or consequence.

Start with the separately named official query

The Railroad Commission of Texas Research Queries directory lists Flare/Vent Exceptions (Statewide Rule 32) Query as a separate oil-and-gas query and identifies its update frequency as nightly. Preserve that complete directory route and the separately named SWR 32 public-query address instead of writing only “RRC lookup.”

The RRC’s About the Flare/Vent Exceptions Query page says the query searches Form R-32 exception applications submitted on or after May 2, 2021. It also says that authorized exception information is available in PDF format through the query when an application has been approved. Those are source-coverage and interface statements, not proof that a private mineral interest is connected to a record or that any operational event occurred.

This worksheet owns one SWR 32 query attempt. It does not merge the route with Drilling-Permit, Wellbore, Organization P-5, P-4, H-10, Inactive-Well, Oil-Proration, Gas-Proration, Injection-Storage, Pooling-Filing, Severance, production-data, Imaged Records, or private lease-review work. For broader orientation, use Texas Railroad Commission: How to Use Public Records to Understand Your Mineral Rights.

Create an attempt header before entering criteria

Give the attempt a neutral ID such as TX-SWR32-RET-01. The ID labels a retrieval session, not an application, operator, property, mineral interest, finding, or transaction conclusion. Record the purpose, official entry routes, visible query-page label, access date and time, timezone, preparer role, worksheet version, and every source-stated coverage, update, access, display, or result limitation observed.

Create a new attempt for a rerun. Do not overwrite the prior criteria snapshot simply because the page, date, status, or displayed results changed. Separate attempt records let an authorized reviewer compare what was queried without treating either attempt as a regulatory or property conclusion.

Capture the criteria exactly as displayed

The current SWR 32 public query displays criteria including Filing Number, Exception Number, Filing Type, Exception Status, District, date ranges, Property Type, Property ID, Lease/Plant Name, Operator Number, Operator Name, Site Name, Permanent Exception, Flare or Vent Location District, Flare or Vent Location County, Flare or Vent Location Name, and SWR 32 (h)(8). Preserve only labels and controls actually displayed during the attempt.

The official SWR 32 Public Query User Guide states that one or more criteria may be used and that, when multiple criteria are entered or selected, all must be true for an application to display in the results grid. The guide also describes interface formats and status labels. Record those source instructions separately from the values used in the attempt.

Each criterion is a locator or filter, not a conclusion. For every field used, record the displayed label, entry or selection method, controlled value reference, format shown by the source, whether it was submitted, and any visible default, constraint, or warning. Record “unused” for fields not used. Keep actual filing numbers, exception numbers, operator details, property values, locations, and dates out of a reusable public example.

Record only the navigation that occurred

Preserve the path as a sequence:

official directory → About SWR 32 Query context → SWR 32 public query → criteria submitted → query-page state → displayed result, detail, attachment, help, or next route

For each step, record the displayed page or link label, controlled route reference, action taken, access time and timezone, whether the page loaded or changed, and the next step selected. If the session ended, exposed no requested reference, reached a visible constraint, or did not establish the narrow retrieval fact, use not located or unverified without extending that status to an application, property, operator, occurrence, or private interest.

The user guide distinguishes the search criteria area, search and reset actions, results grid, application details, and attachments. Preserve those as separate interface states. A displayed status is a source label. It is not an independent compliance, environmental, operational, or private-property conclusion.

Keep query records and rule text separate

The RRC Current Rules page identifies the official rules as Texas Administrative Code Title 16, Part 1, and provides an informational Chapter 3 rules PDF effective December 8, 2025. The About page points readers to Statewide Rule 32 for the governing rule context.

Do not use this provenance worksheet to interpret the rule, decide whether an exception was required, determine whether an operator complied, or infer environmental impact. If an authorized reviewer needs rule analysis, preserve that as a separate work product with the rule version, author, date, assumptions, and appropriate professional scope.

Likewise, if the query exposes an application detail or attachment, create a separate retrieval step. Record the originating attempt ID, displayed link label, destination route, newly displayed fields, access timestamp, controlled retained-reference location, and located/not located/unverified status. Do not publish actual attachments or property-specific identifiers in the reusable worksheet.

Preserve the source limitation

The Research Queries page states that its online data sets are continually updated, provided for informational purposes, not intended as authoritative public records, and without legal force or effect. It places responsibility on users to evaluate accuracy, completeness, currency, and suitability. Preserve that source limitation with the attempt.

The Flare/Vent Exceptions query has a stated online-system coverage boundary beginning May 2, 2021. A result outside that period may require another official record channel. Not located within this query therefore cannot prove that no application, exception, historical record, operator relationship, property record, or event exists.

Use only bounded retrieval statuses

• Located: the recorded official query exposed an identified result reference.
• Not located: the recorded attempt did not expose the sought result reference.
• Unverified: a route, label, identifier, status, detail, or attachment appeared, but the narrow retrieval fact or relationship was not established.

Located does not mean connected, applicable, complete, accurate, current, approved, compliant, operational, environmentally significant, productive, paid, valuable, or legally effective. Not located does not mean nonexistent. Unverified preserves uncertainty without alleging an error, defect, violation, or omission.

Blank Flare/Vent Exception query provenance worksheet

• Attempt ID: _________
• Purpose: SWR 32 public-query retrieval only
• Official entry routes: _________
• Query-page label: _________
• Access date, time, and timezone: _________
• Source-stated coverage and update context: _________
• Criterion labels and controlled values: _________
• Visible status selections: _________
• Date-range fields and displayed format: _________
• Property, operator, and location criteria used: _________
• Visible instruction or constraint: _________
• Navigation path: _________
• Query-page criteria and state: _________
• Result-grid labels and controlled reference: _________
• Application-detail or attachment route, if opened: _________
• Authorized retained-reference location: _________
• Retrieval status: located / not located / unverified
• Neutral next retrieval question: _________

Use one attempt per worksheet record. If a qualified reviewer later interprets an application, rule, attachment, status, or property relationship, preserve that analysis separately with its own author, date, sources, assumptions, limits, and professional scope.

Turn gaps into neutral next questions

When the route or criteria do not expose a requested reference, ask a bounded retrieval question. Was the correct official query used? Were the displayed format and controlled values copied exactly? Did all selected criteria need to be true? Was a date range completed? Did the page show limits involving coverage, access, or the interface? Is a separate official route needed for a different record class or historical period?

Do not turn a gap into “no record exists,” “no flaring occurred,” “the operator is compliant,” “the property has no risk,” “royalties are unaffected,” or “the mineral interest has a particular value.” Those are not retrieval statuses.

Final quality check

Before closing the worksheet, confirm that the exact official entry routes are named; every submitted criterion retains its source-displayed label and controlled value; source instructions, coverage, and limitations are captured separately; navigation records only steps that occurred; query state, result rows, details, attachments, and rule text remain separate; every status is only located, not located, or unverified; and no row interprets an application, status, result, attachment, rule, operator, property, location, or private-interest relationship.

A strong provenance worksheet is narrow by design. It lets an authorized reviewer understand and repeat one recorded SWR 32 public-query attempt. It does not decide what any result means.

Frequently asked questions

Does a located SWR 32 query result prove that flaring or venting occurred or that an exception applies to my mineral rights?

No. Located means only that the recorded official query exposed an identified reference. It does not establish an occurrence, a private-property connection, ownership, title, lease effect, regulatory standing, compliance, production, royalty impact, value, or a transaction result.

Does not located mean no Form R-32 application or exception record exists?

No. Not located describes one attempt using stated criteria at a stated time. The official query covers applications submitted through the online system on or after May 2, 2021, and a criterion mismatch, interface state, source limitation, update, or separate official record channel may require another bounded retrieval step.

Can I publish a real filing number, exception number, application attachment, operator detail, or result screen in a reusable worksheet example?

No. Keep actual identifiers, attachments, criteria values, and result details in an authorized controlled reference. A reusable example should use blank fields and should not publish property-specific, operational, or sensitive records.

Can this worksheet decide compliance, environmental impact, production, mineral-rights value, royalty payment, offer quality, or transaction action?

No. It records query provenance only. It does not establish a regulatory, environmental, legal, title, land, operational, production, financial, valuation, payment, offer, or transaction conclusion.

Should I combine a query result with the rule text or another RRC query?

No. Record each official route as a separate retrieval step with its own source context, access time, retained reference, and bounded status. A shared identifier, operator, property label, date, district, county, or name does not establish that separate sources have the same scope or private-property connection.

Sources

• Railroad Commission of Texas, Research Queries (accessed 2026-08-24)
• Railroad Commission of Texas, About the Flare/Vent Exceptions SWR 32 Query (accessed 2026-08-24)
• Railroad Commission of Texas, SWR 32 Public Query (accessed 2026-08-24)
• Railroad Commission of Texas, SWR 32 Public Query User Guide (accessed 2026-08-24)
• Railroad Commission of Texas, Current Rules (accessed 2026-08-24)
• Railroad Commission of Texas, Chapter 3 Oil and Gas Division rules PDF effective 2025-12-08 (accessed 2026-08-24)