WELL · 42-399-34444 · DISTRICT 7

Hughes #2

Plugged

Runnels County · Triton (Canyon Sand) field  · Vertical

Hughes #2 (API 42-399-34444) is a plugged well in Runnels County, plugged March 12, 2014, last operated by Southcoast Resources LLC.

The RRC has issued one drilling permit (amended once), issued April 25, 1996, permitted to 4,800 ft.

It was permitted by Edco Petroleum, Inc. and has since transferred to Southcoast Resources LLC on the wellbore schedule.

Completion filings report 3 formation tops, including Palo Pinto, Upper Capps, Goen Reef.

Its lease has reported 39.3K barrels of oil and 55 mcf of gas since June 1996, last reporting in August 2014.

Operator of record

Southcoast Resources LLC

Permitted by Edco Petroleum, Inc.; the EWA schedule now lists a different operator.

Fort Worth, TX · P-5 Y, filed Apr 8, 2016 · 5 permits on file · (512) 484-3221

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSouthcoast Resources LLC
Production reports3-D Oil & Gasthrough Oct 2010
Latest permitEdco Petroleum, Inc.Apr 25, 1996

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

4,800
total depth, ft
2
permits on file
Apr 25, 1996
last permit issued
Jun 9, 1996
completed
39.3K
cumulative oil, bbl
55
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 1996 THROUGH Aug 2014

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jun 9, 1996
Shut in
—
Plugged
Mar 12, 2014

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
Hughes O-9-14416Triton (Canyon Sand)Southcoast Resources, LLC139.3K55Jun 1996 – Aug 2014

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. 1Edco Petroleum, Inc.Jun 1996 → Jul 2004
  2. 2Deltex Minerals Inc.Aug 2004 → Oct 2009
  3. 33-D Oil & GasNov 2009 → Oct 2010

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
447331-98DrillEdco Petroleum, Inc.Jul 19, 1996Apr 25, 1996Apr 25, 19964,800
447331-99DrillEdco Petroleum, Inc.Apr 22, 1996Apr 25, 1996—4,800

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-9-14416————

Formation tops

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

FormationMD ftSubsea
Palo Pinto4,000-2,092
Upper Capps4,310-2,402
Goen Reef4,550-2,642

Perforations

Perforated and open-hole intervals.

FromToType
3,6323,634Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62523612.25155 S
4.53,7977.875200 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
00Aug 22, 1996Jul 22, 1996Yes
00Aug 7, 1996——

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