WELL · 42-089-32305 · DISTRICT 3

Hughes #1

Plugged

Colorado County · Wharco Shilling (Frio 3900) field  · Vertical

Hughes #1 (API 42-089-32305) is a plugged well in Colorado County, plugged October 1, 2004, last operated by American Energy Partners Inc..

The RRC has issued 2 drilling permits between 2001 and 2004, permitted to 4,710 ft.

It was permitted by Wagner Oil Company and has since transferred to American Energy Partners Inc. on the wellbore schedule.

Completion filings report 2 formation tops, including Catahoula, Frio.

Operator of record

American Energy Partners Inc.

Permitted by Wagner Oil Company; the EWA schedule now lists a different operator.

Boerne, TX · P-5 Y, filed Oct 7, 2011 · 52 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleAmerican Energy Partners Inc.
Production reportsWagner Oil Companythrough Nov 2003
Latest permitWagner Oil CompanyJan 16, 2004

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

4,710
total depth, ft
2
permits on file
Jan 16, 2004
last permit issued
Oct 23, 2001
completed
0
cumulative oil, bbl
116K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Oct 2001 THROUGH Sep 2004

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Oct 23, 2001
Shut in
—
Plugged
Oct 1, 2004

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
Hughes G-3-186984Wharco Shilling (Frio 3900)American Energy Partners, Inc.10116KOct 2001 – Sep 2004
Hughes G-3-199315WildcatWagner Oil Company100Dec 2003 – Sep 2004

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. 1Wagner Oil CompanyNov 2001 → Nov 2003

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
540788-99RecompletionWagner Oil CompanyJan 15, 2004Jan 16, 2004Dec 21, 20034,710
512449-99DrillWagner Oil CompanyAug 10, 2001Aug 13, 2001Oct 3, 20014,700

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-3-186984————
—— G-3-199315————

Formation tops

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

FormationMD ftSubsea
Catahoula2,895-2,762
Frio3,071-2,938
FrioFRIO O4,495-4,362
FrioFRIO P4,643-4,510

Perforations

Perforated and open-hole intervals.

FromToType
3,0363,040Perforated
3,9133,916Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62548612.25320 S
8.62548612.5320 S
2.8754,6827.875865 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 19, 2004Jan 30, 2004Yes
00Feb 26, 2004——
00Mar 13, 2002Dec 5, 2001Yes
00Feb 26, 2002——

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