WELL · 42-465-30474 · DISTRICT 1

Coe Hazel Whitehead #3

Plugged

Val Verde County · Vinegarone (Strawn) field  · Vertical

Coe Hazel Whitehead #3 (API 42-465-30474) is a plugged well in Val Verde County, plugged January 9, 1998, last operated by Ricks Exploration Inc..

The RRC has issued one drilling permit (amended once), issued July 21, 1989, permitted to 12,500 ft.

It was permitted by Exxon Corp. - Midland and has since transferred to Ricks Exploration Inc. on the wellbore schedule.

Completion filings report one formation top, including Pennsylvanian.

Operator of record

Ricks Exploration Inc.

Permitted by Exxon Corp. - Midland; the EWA schedule now lists a different operator.

Based in
Oklahoma City, OK
P-5 status
Inactive (I)
P-5 last filed
May 27, 2004
Permits on file
190
Phone
(432) 683-7443

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleRicks Exploration Inc.
Production reportsRicks Exploration, Inc.through Mar 1997
Latest permitExxon Corp. - MidlandJul 21, 1989

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

12,500
total depth, ft
2
permits on file
Jul 21, 1989
last permit issued
Dec 21, 1989
completed
0
cumulative oil, bbl
1.12K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jan 1998

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Dec 21, 1989
Shut in
—
Plugged
Jan 9, 1998

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
Coe, Hazel Whitehead G-1-133624Vinegarone (Strawn)Ricks Exploration, Inc.101.12KJan 1993 – Jan 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. 1Ricks Exploration, Inc.Jan 1997 → Mar 1997

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
361701-98DrillExxon Corp. - MidlandOct 20, 1989Jul 21, 1989—12,500
361701-99DrillExxon Corp.Jul 19, 1989Jul 21, 1989Sep 1, 198912,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-1-133624————

Formation tops

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

FormationMD ftSubsea
PennsylvanianPENNSYLVANIAN CANYON SAND7,740-5,724
PennsylvanianPENNSYLVANIAN STRAWN9,565-7,549
PennsylvanianPENNSYLVANIAN LOWER STRAWN11,470-9,454

Perforations

Perforated and open-hole intervals.

FromToType
10,13610,149Perforated
10,15610,173Perforated
10,17410,191Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,64612.25600 S
511,8467.875650 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 4, 1990Feb 20, 1990Yes
00Mar 15, 1990——

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