WELL · 42-461-42736 · DISTRICT 7

Hellfire West D #7HA

Y

Upton County · Spraberry (Trend Area) field · Producing  · Horizontal

Hellfire West D #7HA (API 42-461-42736) is a horizontal well in Upton County operated by Apache Corporation, completed February 18, 2025 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued March 13, 2024, permitted to 10,000 ft.

Completion filings report 10 formation tops, including Yates, Grayburg, San Andres, Clear Fork.

Its lease has reported 176K barrels of oil and 232K mcf of gas since July 2024, last reporting in July 2026.

Operator of record

Apache Corporation

Houston, TX · P-5 Y, filed Oct 4, 2025 · 9,754 permits on file · (713) 296-6400

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleApache Corporation
Production reportsApache Corporationthrough Apr 2026
Latest permitApache CorporationMar 13, 2024
10,000
total depth, ft
1
permits on file
Mar 13, 2024
last permit issued
Feb 18, 2025
completed
176K
cumulative oil, bbl
232K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jul 2024 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Feb 18, 2025
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

Surface location

31.316974, -101.801916

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Upton County.

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
Hellfire West D O-9-22936Spraberry (Trend Area)Apache Corporation1176K232KJul 2024 – Jul 2026

Oil, barrels lease total

Last 12 months 144,722 · prior 12 30,989(+367%)

010K20K202420252026

Gas, mcf lease total

Last 12 months 204,601 · prior 12 27,778(+637%)

020K40K202420252026

Chain of custody

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

  1. 1Apache CorporationFeb 2025 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
897950-99DrillApache CorporationMar 5, 2024Mar 13, 2024Jun 2, 202410,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-9-22936————

Formation tops

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

FormationMD ftSubsea
Yates2,121535
Grayburg3,383-727
San AndresSAN ANDRES - SALTWATER FLOW3,667-1,011
Clear ForkCLEARFORK5,815-3,159
Spraberry6,545-3,889
Wolfcamp8,062-5,406
Devonian——
Ellenburger——
Fusselman——
Strawn——

Perforations

Perforated and open-hole intervals.

FromToType
8,62118,449Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37555717.5630 S
9.6257,67512.25635 S
5.518,5118.52,650 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
00Jun 16, 2025May 21, 2025—
00Mar 12, 2025Feb 22, 2025Yes

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) and the University Lands library. then paste it into their search.

Nearby wells and their tops

NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM

Draw a cross-section

This well's tops beside its 5 nearest neighbours, subsea-aligned so they line up regardless of surface terrain.

Open the cross-section →

Hellfire East E42-461-42732

0.0 KM · Apache Corporation · Section with this well →

Yates2,115541
Grayburg3,368-712
San Andres3,662-1,006
Clear Fork5,811-3,155
Spraberry6,539-3,883
Wolfcamp8,060-5,404
Fusselman—
Ellenburger—

10 TOPS · FIRST 8

Hellfire West B42-461-42734

0.0 KM · Apache Corporation · Section with this well →

Yates2,109547
Grayburg3,385-729
San Andres3,676-1,020
Clear Fork5,815-3,159
Spraberry6,545-3,889
Wolfcamp8,068-5,412
Fusselman—
Devonian—

10 TOPS · FIRST 8

Hellfire West C42-461-42735

0.0 KM · Apache Corporation · Section with this well →

Yates2,126531
Grayburg3,389-732
San Andres3,677-1,020
Clear Fork5,820-3,163
Spraberry6,544-3,887
Wolfcamp8,061-5,404
Devonian—
Strawn—

10 TOPS · FIRST 8

Hellfire West A42-461-41994

0.3 KM · Apache Corporation · Section with this well →

Yates2,1071,543
Grayburg3,294356
San Andres3,715-65
Spraberry6,514-2,864
Wolfcamp8,036-4,386
Ellenburger—
Fusselman—
Devonian—

9 TOPS · FIRST 8

Hellfire West B42-461-41995

0.3 KM · Apache Corporation · Section with this well →

Yates2,106543
Grayburg3,285-636
San Andres3,689-1,040
Clear Fork5,809-3,160
Spraberry6,527-3,878
Wolfcamp8,056-5,407
Devonian—
Ellenburger—

10 TOPS · FIRST 8

Warhead 0405 D42-461-41220

0.4 KM · Apache Corporation · Section with this well →

Yates2,153509
Grayburg3,397-735
San Andres3,735-1,073
Clear Fork5,827-3,165
Spraberry6,527-3,865
Wolfcamp8,067-5,405
Devonian—
Fusselman—

10 TOPS · FIRST 8

Hellfire East C42-461-41997

0.4 KM · Apache Corporation · Section with this well →

Yates2,104545
Grayburg3,264-615
San Andres3,666-1,017
Spraberry6,519-3,870
Wolfcamp8,040-5,391
Ellenburger—
Strawn—
Fusselman—

9 TOPS · FIRST 8

Warhead 0405 D42-461-41222

0.4 KM · Apache Corporation · Section with this well →

Yates2,150512
Grayburg3,400-738
San Andres3,751-1,089
Clear Fork5,838-3,176
Spraberry6,523-3,861
Wolfcamp8,042-5,380
Strawn—
Devonian—

10 TOPS · FIRST 8

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