WELL · 42-479-39124 · DISTRICT 4

Hubberd #80

Plugged

Webb County · Hubberd (Lobo) field  · Vertical

Hubberd #80 (API 42-479-39124) is a plugged well in Webb County, plugged December 5, 2013, last operated by Columbus Energy LLC.

The RRC has issued one drilling permit, issued May 19, 2005, permitted to 10,900 ft.

It was permitted by Houston Exploration Company, The and has since transferred to Columbus Energy LLC on the wellbore schedule.

Completion filings report 3 formation tops, including 8100 Sd, Lobo 1, Lobo 6.

Operator of record

Columbus Energy LLC

Permitted by Houston Exploration Company, The; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed Apr 4, 2026 · 51 permits on file · (956) 722-5238

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleColumbus Energy LLC
Production reportsColumbus Energy, LLCthrough Aug 2012
Latest permitHouston Exploration Company, TheMay 19, 2005

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

10,900
total depth, ft
1
permits on file
May 19, 2005
last permit issued
Aug 11, 2005
completed
0
cumulative oil, bbl
220K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Aug 2005 THROUGH Dec 2013

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Aug 11, 2005
Shut in
—
Plugged
Dec 5, 2013

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
Hubberd G-4-212861Hubberd (Lobo)Columbus Energy, LLC10220KAug 2005 – Dec 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. 1Houston Exploration Company, TheAug 2005 → Jun 2007
  2. 2Forest Oil CorporationJul 2007 → Jun 2010
  3. 3Columbus Energy, LLCJul 2010 → Aug 2012

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
600917-99DrillHouston Exploration Company, TheMay 19, 2005May 19, 2005Jul 13, 200510,900

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-212861————

Formation tops

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

FormationMD ftSubsea
8100 SD8,850-8,385
Lobo 19,550-9,085
Lobo 610,060-9,595

Perforations

Perforated and open-hole intervals.

FromToType
9,4359,439Perforated
9,4439,446Perforated
9,5639,569Perforated
9,6839,687Perforated
9,6989,706Perforated
10,09010,100Perforated
10,11410,130Perforated
10,14310,151Perforated
10,16210,165Perforated
10,17510,177Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,38012.25530 S
76,9808.75400 S
3.510,3876.25500 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 13, 2006Sep 20, 2005Yes
00Dec 27, 2005——

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