WELL · 42-047-31736 · DISTRICT 4

Chamberlain High #1

Plugged

Brooks County · Ann Mag (7650) field  · Vertical

Chamberlain High #1 (API 42-047-31736) is a plugged well in Brooks County, plugged February 1, 2002, last operated by Maguire Oil Company.

The RRC has issued 3 drilling permits (amended once) between 1996 and 1999, permitted to 9,400 ft.

Completion filings report 5 formation tops, including 7650 Sand, 7800 Sand, 8300 Sand, 8600 Sand.

Operator of record

Maguire Oil Company

Based in
Dallas, TX
P-5 status
Inactive (I)
P-5 last filed
Jul 10, 2006
Permits on file
274
Phone
(214) 741-5137

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsMaguire Oil Companythrough Jul 1999
Latest permitMaguire Oil CompanyJun 14, 1999
9,400
total depth, ft
4
permits on file
Jun 14, 1999
last permit issued
Mar 20, 1998
completed
0
cumulative oil, bbl
95.6K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Dec 1996 THROUGH Jan 2002

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Mar 20, 1998
Shut in
—
Plugged
Feb 1, 2002

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
Chamberlain High G-4-167445Ann Mag (7650)Maguire Oil Company1033.1KMar 1998 – Jan 2002
Chamberlain High G-4-161734Ann Mag (7800)Maguire Oil Company1062.5KDec 1996 – Mar 1998

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. 1Maguire Oil CompanyDec 1996 → Jul 1999

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
485165-99RecompletionMaguire Oil CompanyJun 14, 1999Jun 14, 1999—8,950
474574-99RecompletionMaguire Oil CompanyMar 20, 1998Mar 20, 1998Mar 20, 19988,950
453315-98DrillMaguire Oil CompanyJan 8, 1997Oct 1, 1996Oct 20, 19968,950
453315-99DrillMaguire Oil CompanyOct 1, 1996Oct 1, 1996—9,400

Completions

CompletedLeaseFieldOperatorStatusDepth
Mar 20, 1998Chamberlain High G-4-167445Ann Mag (7650)Maguire Oil CompanyPlugged—
Dec 30, 1996Chamberlain High G-4-161734Ann Mag (7800)Maguire Oil CompanyPlugged—

Formation tops

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

FormationMD ftSubsea
7650 Sand7,661-7,576
7800 Sand7,754-7,669
8300 Sand8,232-8,147
8600 Sand8,438-8,353
9100 Sand8,758-8,673

Perforations

Perforated and open-hole intervals.

FromToType
7,6617,664Perforated
7,7547,761Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
144014—
8.6251,55512.25675 S
5.58,9177.875805 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
00May 19, 1998Mar 27, 1998Yes
00Apr 10, 1998——
00Mar 19, 1997Jan 14, 1997Yes
00Mar 3, 1997——

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