WELL · 42-461-43238 · DISTRICT 10

McElroy, J. T., Cons. #1972A

N

Upton County  · Vertical

Mcelroy, J. T., Cons. #1972A (API 42-461-43238) is a permitted well in Upton County filed by Scout Energy Management LLC; no completion report is on file yet.

The RRC has issued one drilling permit, issued July 3, 2025, permitted to 3,090 ft.

Operator of record

Scout Energy Management LLC

Dallas, TX · P-5 Y, filed Aug 4, 2025 · 483 permits on file · (888) 493-2118

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitScout Energy Management LLCJul 3, 2025
3,090
total depth, ft
1
permits on file
Jul 3, 2025
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.402823, -102.303199

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Upton 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
908996-99DrillScout Energy Management LLCJul 1, 2025Jul 3, 2025Oct 5, 20253,090

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 →

McElroy, J. T., Cons.42-461-43240

0.1 KM · Scout Energy Management LLC · Section with this well →

Rustler9941,609
Yates1,889714
L/Grayburg2,834-231
Fusselman—
Strawn—
Spraberry—
San Andres—
Wolfcamp—

10 TOPS · FIRST 8

Crier-McElroy42-461-43201

0.1 KM · Scout Energy Management LLC · Section with this well →

Rustler1,0031,598
Tansill1,783818
Yates1,888713
Seven Rivers2,093508
Queen2,473128
Grayburg2,55150
Grayburg2,735-134
Grayburg2,833-232

15 TOPS · FIRST 8

McElroy, J. T., Cons.42-461-43244

0.3 KM · Scout Energy Management LLC · Section with this well →

Rustler1,0101,594
T/Tnsl1,787817
San Andres1,888716
Yates1,898706
Seven Rivers2,067537
Queen2,485119
Grayburg2,6004
M/Grayburg2,741-137

10 TOPS · FIRST 8

McElroy Cons. No. 142-461-43200

0.4 KM · Scout Energy Management LLC · Section with this well →

Queen2,52282
Grayburg2,637-33
Grayburg2,782-178
San Andres—
Spraberry—
Strawn—
Wolfcamp—
Fusselman—

10 TOPS · FIRST 8

McElroy, J. T. Cons42-461-33254

0.8 KM · Chevron U. S. A. Inc. · Section with this well →

Santa Rosa6481,961
Rustler9351,674
Yates1,892717
Queen2,302307
McElroy2,626-17
San Andres2,996-387

McElroy, J. T., Cons.42-461-43241

1.3 KM · Scout Energy Management LLC · Section with this well →

Grayburg2,54635
M/Grayburg2,686-105
L/Grayburg2,781-200
T/San Andres2,883-302
San Andres—
Devonian—
Yates—
Wolfcamp—

10 TOPS · FIRST 8

Crier-McElroy42-461-43236

1.5 KM · Scout Energy Management LLC · Section with this well →

Rustler9871,586
Yates1,851722
Grayburg2,53043
Wolfcamp—
Strawn—
Spraberry—
San Andres—
Fusselman—

10 TOPS · FIRST 8

McElroy, J. T., Cons.42-461-43198

1.6 KM · Scout Energy Management LLC · Section with this well →

Yates6681,900
Rustler9801,588
Grayburg2,598-30
San Andres2,923-355
Strawn—
Fusselman—
Ellenburger—
Wolfcamp—

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