Texas RRC Injection-Storage Test Report Retrieval Provenance Worksheet

Direct answer for mineral owners

Give one authorized manual profileId 7 attempt a neutral ID. Record the official route, source-displayed profile identity and scope, timestamp, controlled criteria, access and result states, evidence, and only located, not located, or unverified. Treat HTTP 403 and every incomplete attempt as unverified. Do not log in, pay, file, interpret H-5 material, or infer injection, storage, compliance, engineering, environmental, property, production, value, offer, legal, tax, or transaction facts.

Key takeaways for mineral owners

• Keep profileId 7 separate from UIC permits, EDMS H-1/H-1A/W-14 documents, H-10 monitoring, and H-5 filing.
• Preserve May 2021 through current date only as source-described profile scope, not proof of completeness or a particular report.
• Treat HTTP 403, access blocks, errors, timeouts, validation failures, CAPTCHAs, unavailable viewers, and incomplete attempts as unverified.
• Use not located only after a completed empty result attributable to accepted recorded criteria.
• Stop before interpreting a test report or drawing compliance, engineering, environmental, property, production, valuation, legal, or transaction conclusions.

Public retrieval boundary. This article records one authorized manual attempt through the Texas Railroad Commission’s Imaged Records Injection-Storage Test Reports profile. It does not interpret Form H-5 material or determine injection or storage activity, mechanical integrity, permit status, compliance, engineering, environmental conditions, facility or well facts, property connection, production, ownership, title, lease, royalty, value, offer quality, legal effect, tax, or transaction outcome. It does not provide legal, title, land, regulatory, environmental, geological, engineering, tax, accounting, appraisal, investment, or financial advice. MRX provides educational information and resources only and does not buy mineral rights.

A Texas RRC injection-storage test report retrieval worksheet preserves how one manual source attempt occurred. It identifies the official route and profile, timestamps the attempt, records source-described scope, points to controlled criteria, keeps access and result states separate, retains evidence, and assigns one bounded outcome.

Use only located, not located, or unverified. Those labels describe one retrieval event. They do not turn a profile label, coverage statement, report row, image, chart, viewer, or empty state into a substantive conclusion.

Start with the official Imaged Records route

The official Research Queries directory points to Imaged Records. The current Imaged Records Query Menu identifies Injection-Storage Test Reports as profileId=7.

The menu states Form H-5 online filing and describes the profile’s dates as May 2021 through current date. Preserve that wording with the page URL and access date. It is source-described route scope, not proof that the collection is complete, that a particular report exists, or that any displayed item applies to a property.

This worksheet covers one authorized manual attempt. Do not scrape, poll, retrieve in volume, repeat queries, bypass access controls, automate CAPTCHA handling, log in, pay, or work around validation, timeout, session, or viewer behavior.

Preserve the current HTTP 403 attempt

During article preparation, the direct official profile route at profileId=7 returned HTTP 403. No profile page was captured, no criteria controls were verified, no values were entered, and no query completed. The present outcome is unverified.

HTTP 403 is an access response, not an empty result. A blocked page, login requirement, error, timeout, validation failure, default screen, interrupted session, CAPTCHA, unavailable viewer, or incomplete attempt does not show that a report is absent. Record the route, timestamp, response state, stop point, and evidence reference without attempting a bypass.

Build the attempt header before using controls

Assign a neutral attempt ID that does not disclose a well, operator, property, owner, pressure reading, test result, or private transaction value. Preserve:

• the official directory, Imaged Records, menu, and profile URLs;
• the displayed Injection-Storage Test Reports label and profileId=7;
• the access date, clock time, and explicit timezone;
• the source-described scope statement with its access date;
• the authorized manual access method;
• exact source-displayed criteria labels, if the profile loads;
• a restricted reference to entered or selected values;
• the displayed submission, access, result, download, and viewer states;
• the retained evidence location and integrity reference; and
• the outcome, limitations, unresolved questions, and authorized handoff.

Do not publish identifiers, wells, operators, facilities, dates, pressure values, results, properties, owners, or private-party values merely because a source accepts or displays them. Keep necessary values in an authorized controlled location.

Keep adjacent RRC routes separate

The official Injection-Storage Resources page distinguishes online applications, permit queries, monitoring reports, and test-report sources. Those links are a route map. They do not authorize a login, filing, request, payment, or substitute query in this worksheet.

The UIC permit query is a permit-data route. The H-10 query concerns annual disposal or injection monitoring reports. EDMS provides H-1, H-1A, and W-14 application materials and, according to the official EDMS overview, separate older H-5 image coverage. None is interchangeable with the one profileId 7 attempt.

Record profile context, attempt state, document state, and adjacent-route context separately. Do not use one route to fill a gap in another. This article does not explain how to file Form H-5, conduct or evaluate a test, interpret a report, or determine what any result means.

Apply fail-closed outcomes

Use located only when a completed, attributable manual profileId 7 attempt displays responsive material. Located means the source displayed something; it does not mean the item is complete, current, correct, applicable, or legally sufficient.

Use not located only when the official profile loaded, displayed criteria were recorded, controlled criteria were accepted, manual submission completed, and the source displayed an empty result attributable to those criteria without any block, login, error, timeout, validation, session, CAPTCHA, viewer, or interpretation problem.

Use unverified for every other state. The current HTTP 403 attempt is unverified. Do not change criteria, log in, pay, use another source, or repeat searches merely to obtain a different label.

Blank provenance template

Field	What to preserve
Attempt ID	Neutral internal identifier
Official route	Directory, Imaged Records, menu, and profile URLs
Profile identity	Displayed label and profileId=7
Attempted at	Date, clock time, and explicit timezone
Source-described scope	Exact wording, page URL, and access date
Criteria schema	Exact source-displayed labels, if accessible
Controlled criteria ref	Restricted reference to entered or selected values
Access/result state	Exact response, displayed state, error, timeout, or empty-result wording
Document/viewer state	Row, link, image, download, viewer state, or none displayed
Evidence reference	Restricted capture with timestamp and integrity reference
Outcome	Located, not located, or unverified
Limitations	Missing steps, route boundaries, access blocks, and prohibited inference
Handoff	Authorized next step and responsible party

Keep the template blank until an actual authorized attempt supplies a field. Never insert example identifiers or findings that could be mistaken for a real report, well, operator, property, pressure value, test result, or compliance conclusion.

Handoff without expanding the claim

A later reviewer should be able to reproduce what happened from the route, profile identity, timestamp, criteria reference, exact displayed state, evidence location, outcome rule, and limitations. A located item still requires a separately authorized interpretation task. A not-located label applies only to the recorded criteria and completed attempt. An unverified record preserves uncertainty without converting it into absence.

The useful output is narrow: one profile, one controlled criteria set, one manual attempt, one evidence chain, and one bounded outcome. That provenance can support later work without becoming a permit, injection, storage, compliance, engineering, environmental, property, production, valuation, legal, or transaction conclusion.

Sources reviewed for this article

• Texas RRC, Research Queries
• Texas RRC, Imaged Records
• Texas RRC, Imaged Records Query Menu
• Texas RRC, Injection-Storage Resources
• Texas RRC, Electronic Document Management System

Frequently asked questions

Does a located report prove an injection, storage, or compliance fact?

No. Located means only that one recorded manual profile attempt displayed responsive material. It does not establish completeness, interpretation, property connection, injection or storage conditions, engineering, environmental status, compliance, production, ownership, value, or legal effect.

Can an HTTP 403 response be labeled not located?

No. HTTP 403 is an access state, not an empty result. Record it as unverified.

Can I substitute the UIC permit query, EDMS, H-10 query, or RRC Online filing route?

No. Those are separate routes with different records, criteria, access, and evidence states. Preserve each separately.

Does the source-described date range prove the profile is complete?

No. Preserve the range and access date as source-described collection scope without inferring completeness or the existence of a particular report.

Can this retrieval be automated or repeated in bulk?

No. This worksheet authorizes one manual attempt only and does not authorize scraping, automation, repeated queries, bypasses, CAPTCHA handling, login, payment, or workarounds.

Sources reviewed for this article

• Texas RRC, Research Queries (accessed 2026-08-25)
• Texas RRC, Imaged Records (accessed 2026-08-25)
• Texas RRC, Imaged Records Query Menu (accessed 2026-08-25)
• Texas RRC, Injection-Storage Resources (accessed 2026-08-25)
• Texas RRC, Electronic Document Management System (accessed 2026-08-25)