WELL · 42-487-30993 · DISTRICT 9

Baker Hazel L. Unit et al #1 #1

Plugged

Wilbarger County · K & L (Ellenburger) field  · Vertical

Baker Hazel L. Unit ET AL #1 #1 (API 42-487-30993) is a plugged well in Wilbarger County, plugged October 25, 2003, last operated by Madison Oil Company.

The RRC has issued 2 drilling permits between 1977 and 1997, permitted to 5,000 ft.

Completion filings report 2 formation tops, including Caddo, Ellenburger.

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

Operator of record

Madison Oil Company

Wichita Falls, TX · P-5 Y, filed Apr 5, 1999 · 39 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleMadison Oil Company
Production reportsDimock Operating Companythrough Jan 2001
Latest permitMadison Oil CompanyMar 31, 1997

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

5,000
total depth, ft
2
permits on file
Mar 31, 1997
last permit issued
Dec 14, 1977
completed
20.3K
cumulative oil, bbl
21
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Mar 2008

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Dec 14, 1977
Shut in
—
Plugged
Oct 25, 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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Hazel Baker Unit O-13-29321K & L (Caddo)Dimock Operating Company114.1K0Apr 1997 – Mar 2008
Baker, Hazel L. Unit et al #1 O-13-18672K & L (Ellenburger)Madison Oil Company16.27K21Jan 1993 – Aug 1997

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. 1Madison Oil CompanyJan 1993 → Dec 1998
  2. 2Dimock Operating CompanyJan 1999 → Jan 2001

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
460498-99RecompletionMadison Oil CompanyMar 31, 1997Mar 31, 1997Jan 31, 19974,720
11606-99DrillTexas Crude, Inc.Nov 8, 1977Nov 8, 1977—5,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-18672————
—— O-13-29321————

Formation tops

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

FormationMD ftSubsea
Caddo4,336-3,084
Ellenburger4,760-3,508

Perforations

Perforated and open-hole intervals.

FromToType
4,3744,385Perforated
—4,768Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
4.54,7637.87590 S
8.625—10.75—

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 28, 1997Apr 2, 1997Yes
00Apr 23, 1997——
00Jan 12, 1984Dec 19, 1977—

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