WELL · 42-131-37711 · DISTRICT 4

Ten Labbe #1

Plugged

Duval County · Labbe (Govt. Wells) field  · Vertical

Ten Labbe #1 (API 42-131-37711) is a plugged well in Duval County, plugged December 7, 2007, last operated by Hmt Pipeline Company Inc..

The RRC has issued one drilling permit (amended once), issued May 12, 1993, permitted to 3,100 ft.

It was permitted by Stinger Oil & Gas Inc. and has since transferred to Hmt Pipeline Company Inc. on the wellbore schedule.

Completion filings report 5 formation tops, including Cole, Hockley, Government, Loma Novia.

Operator of record

HMT Pipeline Company Inc.

Permitted by Stinger Oil & Gas Inc.; the EWA schedule now lists a different operator.

Based in
San Angelo, TX
P-5 status
Inactive (I)
P-5 last filed
Oct 16, 1996
Phone
(325) 949-7798

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHMT Pipeline Company Inc.
Production reportsHMT Pipeline Company, Inc.through Dec 1997
Latest permitStinger Oil & Gas Inc.May 12, 1993

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

3,100
total depth, ft
2
permits on file
May 12, 1993
last permit issued
Jun 10, 1993
completed
0
cumulative oil, bbl
87.1K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 1993 THROUGH Dec 2007

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jun 10, 1993
Shut in
—
Plugged
Dec 7, 2007

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
Ten Labbe G-4-146568Labbe (Govt. Wells)HMT Pipeline Company, Inc.1087.1KJun 1993 – Dec 2007

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. 1Stinger Oil & Gas Inc.Jun 1993 → Jun 1994
  2. 2HMT Pipeline Company, Inc.Sep 1997 → Dec 1997

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
411656-97DrillStinger Oil & Gas Inc.Sep 9, 1993May 12, 1993May 13, 19933,100
411656-99DrillStinger Oil & Gas Inc.May 12, 1993May 12, 1993—3,100

Completions

CompletedLeaseFieldOperatorStatusDepth
Jun 10, 1993Ten Labbe G-4-146568Labbe (Govt. Wells)HMT Pipeline Company Inc.Plugged—

Formation tops

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

FormationMD ftSubsea
Cole2,110-1,431
Hockley2,364-1,685
Government2,714-2,035
Loma Novia2,844-2,165
Mirando3,010-2,331

Perforations

Perforated and open-hole intervals.

FromToType
2,7172,719Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62538812.2555 S
5.53,1107.875—

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
00Nov 12, 1993Jul 8, 1993Yes
00Sep 30, 1993——

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