WELL · 42-103-37399 · DISTRICT 8

Lea P.J. et AL #3913M

Y

Crane County · Lea (Consolidated) field · Producing  · Vertical

Lea P.J. ET AL #3913M (API 42-103-37399) is a well in Crane County operated by Ring Energy Inc., completed August 30, 2025 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued December 7, 2023, permitted to 6,000 ft.

Completion filings report 10 formation tops, including Clear Fork, Tubb, Bend, Cisco.

Its lease has reported 923K barrels of oil and 2.48M mcf of gas since December 2023, last reporting in July 2026. The lease carries 138 wells, so these are lease totals, not this well alone.

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 scheduleRing Energy Inc.
Production reportsRing Energy, Inc.through Apr 2026
Latest permitRing Energy, Inc.Dec 7, 2023
6,000
total depth, ft
1
permits on file
Dec 7, 2023
last permit issued
Aug 30, 2025
completed
923K
cumulative oil, bbl
2.48M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Dec 2023 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Aug 30, 2025
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

Surface location

31.412946, -102.534077

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Crane 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 138 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Lea, P.J. et AL O-10-60004Lea (Consolidated)Ring Energy, Inc.138923K2.48MDec 2023 – Jul 2026

Oil, barrels lease total

Last 12 months 358,442 · prior 12 390,723(-8%)

020K40K60K202420252026

Gas, mcf lease total

Last 12 months 1,017,369 · prior 12 1,064,026(-4%)

050K100K150K202420252026

Chain of custody

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

  1. 1Ring Energy, Inc.Dec 2023 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
895748-99DrillRing Energy, Inc.Dec 6, 2023Dec 7, 2023Aug 15, 20256,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-60004————

Formation tops

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

FormationMD ftSubsea
Clear ForkCLEARFORK4,098-1,616
Tubb4,424-1,942
Bend——
Cisco——
DevonianDEVONIAN - ACTIVE CO2 FLOOD——
Pennsylvanian——
Permian (undifferentiated)PERMIAN GENERAL——
Strawn——
Wichita-AlbanyWICHITA ALBANY——
Wolfcamp——

Perforations

Perforated and open-hole intervals.

FromToType
3,5274,812Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62581712.25410 S
5.55,3657.875691 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
00Nov 21, 2025Nov 3, 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 →

Lea, P.J. et AL42-103-32476

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

Rustler6721,815
Yates1,723764
McElroy2,584-97
San Andres2,899-412
Glorieta3,697-1,210
San Angelo3,719-1,232
Clear Fork4,109-1,622
Clear Fork4,109-1,622

9 TOPS · FIRST 8

Lea, P.J. Etal42-103-33506

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

Salado7571,723
Yates1,762718
McElroy2,604-124
San Andres2,718-238
San Angelo3,728-1,248
Clear Fork4,160-1,680
Clear Fork4,241-1,761
Tubb4,522-2,042

Lea, P.J. Etal42-103-37400

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

San Andres2,977-502
San Angelo3,838-1,363
Clear Fork4,096-1,621
Yates—
Glorieta—
Grayburg—
Permian (undifferentiated)—
Queen—

10 TOPS · FIRST 8

Lea, P.J. Etal A42-103-00209

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

San Andres3,079-597
San Angelo3,704-1,222
Clear Fork4,101-1,619
Clear Fork4,108-1,626
Tubb4,402-1,920

Lea, P.J. Etal42-103-36881

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

San Andres3,182-695
San Angelo3,705-1,218
Clear Fork4,108-1,621
Rustler—
Seven Rivers—
Yates—
Glorieta—
Grayburg—

10 TOPS · FIRST 8

Lea, P.J. Etal A42-103-33508

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

Rustler6671,810
Yates1,717760
McElroy2,592-115
San Andres2,896-419
San Angelo3,694-1,217
Clear Fork4,123-1,646
Clear Fork4,218-1,741
Tubb4,495-2,018

Lea, P.J. Etal -A-42-103-37029

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

San Andres2,899-418
San Angelo3,690-1,209
Clear Fork4,095-1,614
Rustler—
Queen—
Permian (undifferentiated)—
Grayburg—
Glorieta—

10 TOPS · FIRST 8

Lea, P.J. Etal42-103-37243

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

San Andres2,975-490
San Angelo3,828-1,343
Clear Fork4,069-1,584
Queen—
Rustler—
Seven Rivers—
Glorieta—
Yates—

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