WELL · 42-389-37688 · DISTRICT 8

Navajo #601H

Y

Reeves County · Sandbar (Bone Spring) field · Temp Abandoned  · Horizontal

Navajo #601H (API 42-389-37688) is a horizontal well in Reeves County operated by Apache Corporation, completed January 8, 2019 and listed as temp abandoned on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued October 16, 2018, permitted to 16,000 ft.

Completion filings report 8 formation tops, including Cherry Canyon, Bell Canyon, Delaware, Bone Spring.

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

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 Jan 2020
Latest permitApache CorporationOct 16, 2018
16,000
total depth, ft
2
permits on file
Oct 16, 2018
last permit issued
Jan 8, 2019
completed
0
cumulative oil, bbl
13.4K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 2019 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jan 8, 2019
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

Surface location

31.233201, -103.723805

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Reeves 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
Navajo G-10-287285Sandbar (Bone Spring)Apache Corporation1013.4KJan 2019 – Jul 2026

No volumes reported on these leases in the last three years.

Chain of custody

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

  1. 1Apache CorporationJan 2019 → Jan 2020

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
845761-98DrillApache CorporationDec 11, 2018Oct 16, 2018Nov 1, 201816,000
845761-99DrillApache CorporationOct 16, 2018Oct 16, 2018Oct 31, 201816,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-10-287285————

Formation tops

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

FormationMD ftSubsea
Cherry Canyon5,197-2,301
Bell Canyon5,200-2,304
Delaware5,200-2,304
Bone SpringBONE SPRINGS7,187-4,291
CastileCASTILLE——
DelawareDELAWARE CONSOLIDATED GAS——
DelawareFORD-DELAWARE——
Pennsylvanian——
Permian (undifferentiated)PERMIAN——
Wolfcamp——

Perforations

Perforated and open-hole intervals.

FromToType
8,71513,095Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6252,46312.25935 S
5.513,2998.751,940 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
00Oct 22, 2019Jul 8, 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 →

Navajo42-389-37016

0.0 KM · Apache Corporation · Section with this well →

Bell Canyon4,279-1,383
Cherry Canyon5,208-2,312
Bone Spring7,193-4,297
Wolfcamp9,769-6,873
Castile—
Permian (undifferentiated)—
Pennsylvanian—
Delaware—

10 TOPS · FIRST 8

Navajo42-389-36473

0.0 KM · Apache Corporation · Section with this well →

Bell Canyon4,279-1,384
Cherry Canyon5,208-2,313
Delaware6,179-3,284
Bone Spring7,193-4,298
Wolfcamp9,769-6,874
Delaware—
Permian (undifferentiated)—
Castile—

10 TOPS · FIRST 8

Tea Time State West42-389-39480

3.0 KM · Upcurve Energy, LLC · Section with this well →

Bell Canyon4,191-1,311
Delaware4,191-1,311
Cherry Canyon5,111-2,231
Bone Spring6,947-4,067
Bone Spring7,966-5,086
Bone Spring8,304-5,424
Bone Spring8,752-5,872
Delaware—

10 TOPS · FIRST 8

Tea Time State East42-389-39479

3.0 KM · Upcurve Energy, LLC · Section with this well →

Bell Canyon4,200-1,320
Delaware4,200-1,320
Cherry Canyon5,120-2,240
Bone Spring6,963-4,083
Wolfcamp9,640-6,760
Delaware—
Castile—
Delaware—

10 TOPS · FIRST 8

Pinto 2 Unit42-389-40597

3.9 KM · Vital Energy, Inc. · Section with this well →

Bell Canyon4,316-1,500
Cherry Canyon5,187-2,371
Bone Spring7,094-4,278
Bone Spring8,323-5,507
Wolfcamp9,803-6,987
Wolfcamp9,803-6,987
Castile—
Permian (undifferentiated)—

12 TOPS · FIRST 8

Pinto 2 Unit42-389-40596

3.9 KM · Tall City Operations III LLC · Section with this well →

Wolfcamp—
Bell Canyon—
Bone Spring—
Castile—
Cherry Canyon—
Delaware—
Delaware—
Delaware—

10 TOPS · FIRST 8

Pinto 2 Unit42-389-40595

3.9 KM · Tall City Operations III LLC · Section with this well →

Pennsylvanian—
Wolfcamp—
Permian (undifferentiated)—
Bell Canyon—
Bone Spring—
Castile—
Cherry Canyon—
Delaware—

10 TOPS · FIRST 8

Pinto 2 Unit42-389-40594

3.9 KM · Vital Energy, Inc. · Section with this well →

Bell Canyon4,332-1,516
Cherry Canyon5,206-2,390
Bone Spring7,127-4,311
Bone Spring7,473-4,657
Bone Spring8,345-5,529
Bone Spring8,825-6,009
Wolfcamp10,083-7,267
Delaware—

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