TEXAS · WELLS · UPTON COUNTY · API 42-461-41677 · DISTRICT 7C

McDaniel '36' #4

N

Upton County  · Vertical

Mcdaniel '36' #4 (API 42-461-41677) is a permitted well in Upton County filed by Atlas Operating LLC; no completion report is on file yet.

The RRC has issued one drilling permit, issued January 29, 2021, permitted to 8,950 ft.

Operator of record

Atlas Operating LLC

Based in
Houston, TX
P-5 status
Active – Hearing (H)
P-5 last filed
Mar 9, 2026
Permits on file
78
Phone
(281) 893-9400

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitAtlas Operating LLCJan 29, 2021
8,950
total depth, ft
1
permits on file
Jan 29, 2021
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.412959, -101.979755

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
867352-99DrillAtlas Operating LLCJan 27, 2021Jan 29, 2021—8,950

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 neighbors can.

Section of the neighbors →

Micah 542-461-42972

1.1 KM · Summit Petroleum LLC · Section with this well →

San Andres4,496-1,747
Clear Fork6,469-3,720
Spraberry7,317-4,568
Spraberry7,891-5,142
Dean8,594-5,845
Wolfcamp8,729-5,980
Yates—
Grayburg—

10 TOPS · FIRST 8

Micah 442-461-42970

1.1 KM · Summit Petroleum LLC · Section with this well →

San Andres4,500-1,751
Clear Fork6,469-3,720
Spraberry7,327-4,578
Spraberry7,891-5,142
Dean8,616-5,867
Wolfcamp8,739-5,990
Grayburg—
Strawn—

12 TOPS · FIRST 8

Micah 342-461-42968

1.1 KM · Summit Petroleum LLC · Section with this well →

San Andres4,510-1,761
Clear Fork6,463-3,714
Spraberry7,307-4,558
Spraberry7,900-5,151
Dean8,617-5,868
Wolfcamp8,741-5,992
Ellenburger—
Yates—

12 TOPS · FIRST 8

Micah 242-461-42969

1.1 KM · Summit Petroleum LLC · Section with this well →

San Andres4,493-1,744
Clear Fork6,467-3,718
Spraberry7,317-4,568
Spraberry7,900-5,151
Dean8,612-5,863
Wolfcamp8,735-5,986
Ellenburger—
Yates—

12 TOPS · FIRST 8

Micah 142-461-42971

1.1 KM · Summit Petroleum LLC · Section with this well →

San Andres4,487-1,738
Clear Fork6,465-3,716
Spraberry7,320-4,571
Wolfcamp8,735-5,986
Devonian—
Yates—
Strawn—
Grayburg—

10 TOPS · FIRST 8

Lilian 5242-461-42162

1.3 KM · Summit Petroleum LLC · Section with this well →

San Andres4,560-1,795
Clear Fork6,505-3,740
Spraberry7,345-4,580
Grayburg—
Fusselman—
Ellenburger—
Yates—
Wolfcamp—

10 TOPS · FIRST 8

Lilian 5342-461-42163

1.3 KM · Summit Petroleum LLC · Section with this well →

San Andres4,560-1,795
Clear Fork6,505-3,740
Spraberry7,345-4,580
Spraberry7,960-5,195
Grayburg—
Strawn—
Wolfcamp—
Yates—

11 TOPS · FIRST 8

Lilian 5442-461-42164

1.3 KM · Summit Petroleum LLC · Section with this well →

San Andres4,545-1,780
Clear Fork6,525-3,760
Spraberry7,350-4,585
Fusselman—
Grayburg—
Strawn—
Yates—
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/46141677, documented in the API reference.