WELL · 42-203-34917 · DISTRICT 6

Jobe Shale Unit #1 H

Y

Harrison County · Carthage (Haynesville Shale) field · Producing  · Horizontal

Jobe Shale Unit #1 H (API 42-203-34917) is a horizontal well in Harrison County operated by Exco Operating Company LP, completed April 7, 2010 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended twice), issued January 7, 2010, permitted to 10,739 ft.

Completion filings report 4 formation tops, including Glen Rose, Travis Peak, Cotton Valley, 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, LPJan 7, 2010
10,739
total depth, ft
3
permits on file
Jan 7, 2010
last permit issued
Apr 7, 2010
completed
0
cumulative oil, bbl
3.91M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2010 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Apr 7, 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
Jobe Shale Unit G-6-259566Carthage (Haynesville Shale)Exco Operating Company, LP103.91MApr 2010 – Jul 2026

Gas, mcf lease total

Last 12 months 56,267 · prior 12 83,885(-33%)

05K10K202420252026

Chain of custody

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

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

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
689211-97DrillExco Operating Company, LPFeb 23, 2011Jan 7, 2010Jan 26, 201012,000
689211-98DrillExco Operating Company, LPOct 4, 2010Jan 7, 2010Jan 26, 201012,000
689211-99DrillExco Operating Company, LPDec 30, 2009Jan 7, 2010Jan 26, 201012,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Apr 7, 2010Jobe Shale Unit G-6-259566Carthage (Haynesville Shale)Exco Operating Company LPProducing10,739

Formation tops

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

FormationMD ftSubsea
Glen Rose3,104-2,834
Travis Peak5,997-5,727
Cotton Valley7,900-7,630
Bossier9,585-9,315

Perforations

Perforated and open-hole intervals.

FromToType
11,07515,097Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.751,84613.5910 S
5.59,6696.75926 S
7.6259,8639.8752,180 S
4.515,2166.75926 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 19, 2011Oct 14, 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/20334917, documented in the API reference.