WELL · 42-103-37820 · DISTRICT 10

Lea, P.J. et AL #4023MH

N

Crane County  · Horizontal

Lea, P.J. ET AL #4023MH (API 42-103-37820) is a permitted horizontal well in Crane County filed by Ring Energy, Inc.; no completion report is on file yet.

The RRC has issued one drilling permit (amended once), issued June 24, 2026, permitted to 4,000 ft.

Operator of record

Ring Energy, Inc.

Midland, TX · P-5 Y, filed Nov 4, 2025 · 997 permits on file · (855) 214-5188

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitRing Energy, Inc.Jun 24, 2026
4,000
total depth, ft
2
permits on file
Jun 24, 2026
last permit issued
—
completed
—
cumulative oil, bbl
—
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
—

Surface location

31.417821, -102.568066

OpenStreetMap → ·  Google Maps →

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

Only the permit record exists for this well so far, here and in the RRC's wellbore query. Completion reports, formation tops, lease production, and the scanned filings appear once the operator files a completion report, typically months after drilling. Petrora refreshes the wellbore file weekly, so a filing from the last few days may reach the RRC before it shows here. How long each source takes →

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
916593-98DrillRing Energy, Inc.Jul 16, 2026Jun 24, 2026Jul 8, 20264,000
916593-99DrillRing Energy, Inc.Jun 19, 2026Jun 24, 2026—4,000

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 has no tops filed, so it cannot anchor a section; its neighbours can.

Section of the neighbours →

Lea, P.J. Etal42-103-37028

0.6 KM · Stronghold Energy II Oper, LLC · Section with this well →

Devonian6,060-3,559
Fusselman6,839-4,338
Waddell7,980-5,479
Ellenburger8,346-5,845
Montoya—
Strawn—
Permian (undifferentiated)—
Pennsylvanian—

10 TOPS · FIRST 8

Lea, P.J. Etal42-103-00235

1.0 KM · Stronghold Energy II Oper, LLC · Section with this well →

San Andres3,083-587
San Angelo3,750-1,254
Clear Fork4,157-1,661
Lea (Clear Fork)4,330-1,834
Lea (Tubb)4,445-1,949
Tubb4,451-1,955
Connell8,163-5,667

Lea, P.J. Etal42-103-37213

1.4 KM · Ring Energy, Inc. · Section with this well →

San Andres2,962-466
San Angelo3,806-1,310
Clear Fork4,116-1,620
Yates—
Rustler—
Permian (undifferentiated)—
Grayburg—
Glorieta—

10 TOPS · FIRST 8

Lea, P.J. Etal42-103-00215

1.5 KM · Stronghold Energy II Oper, LLC · Section with this well →

San Andres3,070-582
San Angelo3,713-1,225
Clear Fork4,114-1,626
Tubb4,403-1,915

Lea, P.J. Etal42-103-36930

1.5 KM · Stronghold Energy II Oper, LLC · Section with this well →

San Andres3,184-685
San Angelo3,727-1,228
Clear Fork4,120-1,621
Yates—
Seven Rivers—
Rustler—
Queen—
Permian (undifferentiated)—

10 TOPS · FIRST 8

Ring Barnsley A42-103-37401

1.6 KM · Ring Energy, Inc. · Section with this well →

San Andres2,983-485
San Angelo3,838-1,340
Clear Fork4,134-1,636
Tubb4,462-1,964
Glorieta—
Seven Rivers—
Queen—
Yates—

10 TOPS · FIRST 8

Lea, P.J. Etal42-103-00242

1.6 KM · Stronghold Energy II Oper, LLC · Section with this well →

San Andres2,900-402
San Angelo3,730-1,232
Clear Fork4,240-1,742

Lea, P.J. Etal42-103-37212

1.6 KM · Ring Energy, Inc. · Section with this well →

San Andres2,955-466
San Angelo3,819-1,330
Clear Fork4,099-1,610
Yates—
Seven Rivers—
Grayburg—
Permian (undifferentiated)—
Queen—

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