WELL · 42-235-32726 · DISTRICT 7

Brooks H #1

Plugged

Irion County · Brooks (Canyon K) field  · Vertical

Brooks H #1 (API 42-235-32726) is a plugged well in Irion County, plugged November 20, 2003, last operated by Brothers Production Company Inc..

The RRC has issued one drilling permit, issued January 2, 1986, permitted to 6,900 ft.

It was permitted by Txo Production Corp. and has since transferred to Brothers Production Company Inc. on the wellbore schedule.

Completion filings report 4 formation tops, including Clear Fork, Limestone, Cisco, Canyon.

Its lease has reported 11.2K barrels of oil and 76.5K mcf of gas since January 1993, last reporting in June 2005.

Operator of record

Brothers Production Company Inc.

Permitted by TXO Production Corp.; the EWA schedule now lists a different operator.

Midland, TX · P-5 Y, filed Apr 4, 2026 · 45 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBrothers Production Company Inc.
Production reportsBrothers Production Company Inc.through Sep 2001
Latest permitTXO Production Corp.Jan 2, 1986

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

6,900
total depth, ft
1
permits on file
Jan 2, 1986
last permit issued
Feb 21, 1986
completed
11.2K
cumulative oil, bbl
76.5K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jun 2005

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Feb 21, 1986
Shut in
—
Plugged
Nov 20, 2003

Surface location

No coordinates on the permit record yet. The RRC's GIS record usually lands within days of issuance; historical master-file permits never carry one.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Texas reports oil by lease, not by well. These are the lease this well is completed on; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Brooks "H" O-9-11817Brooks (Canyon K)Brothers Production Company Inc.111.2K76.5KJan 1993 – Jun 2005

No volumes reported on these leases in the last three years.

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Marathon Oil CompanyJan 1993 → Sep 1999
  2. 2Brothers Production Company Inc.Dec 1999 → Sep 2001

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
294159-99DrillTXO Production Corp.Jan 2, 1986Jan 2, 1986Jan 21, 19866,900

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-9-11817————

Formation tops

As filed on W-2/G-1. Subsea from 2,299 ft elevation.Download CSV →

FormationMD ftSubsea
Clear ForkCLEARFORK2,738-439
Limestone4,980-2,681
Cisco5,653-3,354
Canyon5,810-3,511

Perforations

Perforated and open-hole intervals.

FromToType
5,8206,591Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62588812.25600 S
4.56,6807.875600 S

Completion filings

W-2 and G-1 reports on record in the RRC wellbore file, newest first. The suffix identifies the wellbore or completion event. About these reports →

SuffixFiledW-2 / G-1 dateLogs referenced
00Mar 11, 1986Mar 4, 1986Yes
00Mar 8, 1986——

The source documents

Petrora holds the structured record. The scanned filings live at the RRC; these links open its search already filled in for this API.

Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward) and the University Lands library. then paste it into their search.

About this data

Permits from the RRC OGA049M master and daily daf420 files; wellbore and operator of record from the EWA schedule, weekly; completions, formation tops, casing, and perforations from the dbf900 wellbore file; production from PDQ lease reports, which lag two to three months; injection from UIC permits, H-10 reports, and TexNet daily volumes; earthquakes from the TexNet catalog.

New to these records? How to read a well page · API numbers · completion reports and tops · why production is by lease

Developers: this page as JSON is GET /v1/data/wells/23532726, documented in the API reference.