WELL · 42-383-40510 · DISTRICT 7

Aldwell 0611 E #6HU

Y

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

Aldwell 0611 E #6HU (API 42-383-40510) is a horizontal well in Reagan County operated by Apache Corporation, completed August 14, 2019 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued January 18, 2019, permitted to 10,000 ft.

Completion filings report 8 formation tops, including Queen, Grayburg, San Andres, Clear Fork.

Its lease has reported 1.57M barrels of oil and 8.62M mcf of gas since August 2019, last reporting in July 2026. The lease carries 5 wells, so these are lease totals, not this well alone.

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 CorporationJan 18, 2019
10,000
total depth, ft
1
permits on file
Jan 18, 2019
last permit issued
Aug 14, 2019
completed
1.57M
cumulative oil, bbl
8.62M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Aug 2019 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Aug 14, 2019
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

Surface location

31.429371, -101.675718

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Reagan 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; they carry 5 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Aldwell 0611 E O-9-20496Spraberry (Trend Area)Apache Corporation51.57M8.62MAug 2019 – Jul 2026

Gas, mcf lease total

Last 12 months 591,147 · prior 12 1,084,437(-45%)

050K100K150K202420252026

Oil, barrels lease total

Last 12 months 56,065 · prior 12 95,113(-41%)

05K10K15K202420252026

Chain of custody

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

  1. 1Apache CorporationAug 2019 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
848887-99DrillApache CorporationJan 17, 2019Jan 18, 2019Feb 28, 201910,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-9-20496————

Formation tops

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

FormationMD ftSubsea
Queen2,763-114
Grayburg3,096-447
San AndresSAN ANDRES - SALTWATER FLOW, POS3,641-992
Clear ForkCLEARFORK5,640-2,991
Spraberry6,447-3,798
Ellenburger——
Fusselman——
Strawn——

Perforations

Perforated and open-hole intervals.

FromToType
8,62418,643Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37559317.5550 S
9.6257,80012.25790 S
5.518,7338.53,035 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
00Jan 28, 2020Sep 23, 2019Yes

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 →

Aldwell 0611 E42-383-40511

0.0 KM · Apache Corporation · Section with this well →

Queen2,842-193
Grayburg3,173-524
San Andres3,739-1,090
Clear Fork5,713-3,064
Spraberry6,449-3,800
Ellenburger—
Strawn—
Fusselman—

Aldwell 0611 E42-383-40512

0.0 KM · Apache Corporation · Section with this well →

Queen2,781-132
Grayburg3,122-473
San Andres3,694-1,045
Clear Fork5,649-3,000
Spraberry6,457-3,808
Fusselman—
Strawn—
Ellenburger—

Aldwell 0611 E42-383-40509

0.4 KM · Apache Corporation · Section with this well →

Queen2,725-72
Grayburg3,040-387
San Andres3,595-942
Clear Fork5,638-2,985
Spraberry6,451-3,798
Strawn—
Fusselman—
Ellenburger—

Aldwell 0611 E42-383-40508

0.4 KM · Apache Corporation · Section with this well →

Queen2,734-81
Grayburg3,081-428
San Andres3,624-971
Clear Fork5,628-2,975
Spraberry6,439-3,786
Strawn—
Fusselman—
Ellenburger—

Hellcat West a 1-1242-383-42141

0.8 KM · DE Central Operating, LLC · Section with this well →

Queen2,742-84
Grayburg3,243-585
San Andres3,370-712
Clear Fork5,524-2,866
Spraberry6,430-3,772
Wolfcamp7,985-5,327
Ellenburger—
Strawn—

9 TOPS · FIRST 8

Hellcat West a 1-1242-383-42071

0.8 KM · DE Central Operating, LLC · Section with this well →

Queen2,439219
Grayburg3,239-581
San Andres3,368-710
Clear Fork5,521-2,863
Spraberry6,425-3,767
Wolfcamp7,979-5,321
Fusselman—
Ellenburger—

9 TOPS · FIRST 8

Hellcat West a 1-1242-383-42070

0.8 KM · DE Central Operating, LLC · Section with this well →

Queen2,740-82
Grayburg3,237-579
San Andres3,369-711
Clear Fork5,521-2,863
Spraberry6,425-3,767
Wolfcamp7,980-5,322
Fusselman—
Strawn—

9 TOPS · FIRST 8

Hellcat West C 1-1242-383-42072

0.8 KM · DE Central Operating, LLC · Section with this well →

Queen2,739-81
Grayburg3,238-580
San Andres3,361-703
Clear Fork5,517-2,859
Spraberry6,422-3,764
Wolfcamp7,974-5,316
Ellenburger—
Fusselman—

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