WELL · 42-297-32411 · DISTRICT 2

Brooks Hodges #1

Plugged

Live Oak County · Houdman (Pettus C) field  · Vertical

Brooks Hodges #1 (API 42-297-32411) is a plugged well in Live Oak County, plugged May 17, 2016, last operated by Bright North Explorations Ltd..

The RRC has issued 2 drilling permits between 1980 and 1996, permitted to 3,500 ft.

Completion filings report 2 formation tops, including Hockley, Pettus.

Its 2 leases have reported 1.85K barrels of oil and 452 mcf of gas since January 1993, last reporting in July 2026. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Bright North Explorations Ltd.

Canada · P-5 Y, filed Dec 4, 2015 · 1 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBright North Explorations Ltd.
Production reportsBright North Explorations Ltd.through Jun 1997
Latest permitBright North Explorations Ltd.Feb 14, 1996
3,500
total depth, ft
2
permits on file
Feb 14, 1996
last permit issued
Aug 16, 1981
completed
1.85K
cumulative oil, bbl
452
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Aug 16, 1981
Shut in
—
Plugged
May 17, 2016

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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Brooks Hodges Unit O-2-8138Houdman (Hockley)Bright North Explorations Ltd.19810Sep 1995 – Jul 2026
Brooks Hodges O-2-6369Houdman (Pettus C)Bright North Explorations Ltd.1871452Jan 1993 – Mar 1996

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. 1Clay Exploration, Inc.Jan 1993 → Aug 1994
  2. 2Anderson Petro-Equipment, Inc.Sep 1994 → Jan 1995
  3. 3Bright North Explorations Ltd.Sep 1995 → Jun 1997

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
444799-99RecompletionBright North Explorations Ltd.Feb 14, 1996Feb 14, 1996Aug 28, 19953,150
84763-99DrillForney, Bill, Inc.Jun 2, 1980Jun 2, 1980—3,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-2-6369————
—— O-2-8138————

Formation tops

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

FormationMD ftSubsea
Hockley2,328-2,003
Pettus3,136-2,811

Perforations

Perforated and open-hole intervals.

FromToType
2,3512,355Perforated
3,1683,177Perforated
—3,177Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62583312.25440 S
2.3753,094——
4.53,3867.875745 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
00Apr 17, 1996Feb 21, 1996Yes
00Mar 1, 1996Jan 9, 1981—
00Jan 12, 1984Jan 9, 1981—
00Jan 12, 1984——

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). 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/29732411, documented in the API reference.