WELL · 42-215-32712 · DISTRICT 4

Coates Energy Trust GU 1 #1

Plugged

Hidalgo County · Jeffress (Vicksburg T) field  · Vertical

Coates Energy Trust GU 1 #1 (API 42-215-32712) is a plugged well in Hidalgo County, plugged July 16, 2012, last operated by Hughes Dan A. Company L.P..

The RRC has issued one drilling permit, issued November 16, 1999, permitted to 12,000 ft.

It was permitted by Bexco Operating, Inc. and has since transferred to Hughes Dan A. Company L.P. on the wellbore schedule.

Completion filings report one formation top, including Vicksburg.

Operator of record

Hughes Dan A. Company L.P.

Permitted by Bexco Operating, Inc.; the EWA schedule now lists a different operator.

Beeville, TX · P-5 Y, filed Nov 4, 2025 · 207 permits on file · (361) 358-3752

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHughes Dan A. Company L.P.
Production reportsCoates Energy Trustthrough Aug 2008
Latest permitBexco Operating, Inc.Nov 16, 1999

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

12,000
total depth, ft
1
permits on file
Nov 16, 1999
last permit issued
Feb 3, 2000
completed
0
cumulative oil, bbl
1.4M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 2000 THROUGH Feb 2013

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Feb 3, 2000
Shut in
—
Plugged
Jul 16, 2012

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
Coates Energy Trust GU 1 G-4-176035Jeffress (Vicksburg T)Hughes, Dan A. Company, L.P.101.4MFeb 2000 – Feb 2013

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. 1Bexco Operating, Inc.Feb 2000 → Oct 2004
  2. 2Coates Energy TrustNov 2004 → Aug 2008

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
489563-99DrillBexco Operating, Inc.Nov 16, 1999Nov 16, 1999Nov 30, 199912,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-176035————

Formation tops

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

FormationMD ftSubsea
VicksburgVICKSBURG A4,890-4,590
VicksburgVICKSBURG G5,900-5,600
VicksburgVICKSBURG J-16,750-6,450
VicksburgVICKSBURG K7,350-7,050
VicksburgVICKSBURG K-17,820-7,520
VicksburgVICKSBURG T9,940-9,640

Perforations

Perforated and open-hole intervals.

FromToType
9,9809,986Perforated
10,01110,071Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3751,13017.5775 S
9.6257,27012.25960 S
5.510,9988.5780 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 31, 2000Feb 28, 2000Yes
00Mar 13, 2000——

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