WELL · 42-405-30224 · DISTRICT 6

Vastar Minerals Gas Unit 4 #5H

Y

San Augustine County · Huxley (6100) field · Producing  · Horizontal

Vastar Minerals Gas Unit 4 #5H (API 42-405-30224) is a horizontal well in San Augustine County operated by Xto Energy Inc., completed August 2, 2008 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued June 2, 2008, permitted to 7,700 ft.

It was permitted by Hunt Petroleum Corporation and has since transferred to Xto Energy Inc. on the wellbore schedule.

Completion filings report 3 formation tops, including Rodessa, Top/Bexar Shale, James Lime.

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

Operator of record

XTO Energy Inc.

Permitted by Hunt Petroleum Corporation; the EWA schedule now lists a different operator.

Spring, TX · P-5 Y, filed Feb 4, 2026 · 16,156 permits on file · (832) 625-1100

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleXTO Energy Inc.
Production reportsXTO Energy Inc.through Apr 2026
Latest permitHunt Petroleum CorporationJun 2, 2008

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

7,700
total depth, ft
1
permits on file
Jun 2, 2008
last permit issued
Aug 2, 2008
completed
0
cumulative oil, bbl
1.57M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Aug 2008 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Aug 2, 2008
Shut in
—
Plugged
—

Operator's P-5 on the schedule: X

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
Vastar Minerals Gas Unit 4 G-6-242321Huxley (6100)XTO Energy Inc.101.57MAug 2008 – Jul 2026

Gas, mcf lease total

Last 12 months 29,287 · prior 12 32,158(-9%)

02K4K202420252026

Chain of custody

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

  1. 1Hunt Petroleum CorporationAug 2008 → Nov 2008
  2. 2XTO Energy Inc.Dec 2008 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
661842-99DrillHunt Petroleum CorporationMay 13, 2008Jun 2, 2008Jun 10, 20087,700

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-6-242321————

Formation tops

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

FormationMD ftSubsea
RodessaTOP RODESSA6,762-6,333
Top/Bexar Shale7,185-6,756
James LimeTOP/JAMES LIME7,332-6,903

Perforations

Perforated and open-hole intervals.

FromToType
7,50012,785Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6252,31012.25870 S
77,5008.75680 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
00Dec 18, 2008Aug 20, 2008Yes
00Nov 24, 2008——

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