TEXAS · WELLS · SAN AUGUSTINE COUNTY · HALEY SHALE UNIT LEASE · API 42-405-30352 · DISTRICT 06

Haley Shale Unit #1 H

Y

San Augustine County · Carthage (Haynesville Shale) field · Producing  · Horizontal

Haley Shale Unit #1 H (API 42-405-30352) is a horizontal well in San Augustine County operated by Exco Operating Company LP, completed November 28, 2010 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued June 2, 2010, permitted to 13,132 ft.

Completion filings report 4 formation tops, including Massive Anhydrite (marker), James Lime, Travis Peak, Bossier.

No lease production has been reported under this well’s leases.

Operator of record

Exco Operating Company LP

Based in
Dallas, TX
P-5 status
Active (A)
P-5 last filed
Aug 22, 2025
Permits on file
515
Phone
(214) 368-2084

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleExco Operating Company LP
Production reportsExco Operating Company, LPthrough Apr 2026
Latest permitExco Operating Company, LPJun 2, 2010
13,132
total depth, ft
1
permits on file
Jun 2, 2010
last permit issued
Nov 28, 2010
completed
0
cumulative oil, bbl
2.87M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Aug 2010 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Nov 28, 2010
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active (A)

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
Haley Shale Unit G-6-258163Carthage (Haynesville Shale)Exco Operating Company, LP102.87MAug 2010 – Jul 2026

Gas, mcf lease total

Last 12 months 16,471 · prior 12 17,664(-7%)

02K4K202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Exco Operating Company, LPNov 2010 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
696820-99DrillExco Operating Company, LPJun 1, 2010Jun 2, 2010Jun 9, 201013,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Nov 28, 2010Haley Shale Unit G-6-258163Carthage (Haynesville Shale)Exco Operating Company LPProducing13,132

Formation tops

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

FormationMD ftSubsea
Massive Anhydrite (marker)MASSIVE ANHYDRITE6,730-6,383
James Lime7,393-7,046
Travis Peak8,520-8,173
Bossier11,642-11,295

Perforations

Perforated and open-hole intervals.

FromToType
13,58817,540Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3752,34017.51,985 S
5.511,8316.75910 S
7.62511,9209.8752,405 S
4.517,9836.75910 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
00Apr 9, 2012Nov 22, 2011—
00Sep 21, 2011Jan 17, 2011Yes
00Dec 6, 2010Aug 31, 2010Yes

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