WELL · 42-353-33739 · DISTRICT 8

SUN05--WTG427 #01

N

Nolan County  · Vertical

Sun05--Wtg427 #01 (API 42-353-33739) is a permitted well in Nolan County filed by Sunoco Pipeline L.P.; no completion report is on file yet.

The RRC has issued one drilling permit, issued April 8, 2022, permitted to 400 ft.

Operator of record

Sunoco Pipeline L.P.

Houston, TX · P-5 Y, filed Aug 4, 2025 · 165 permits on file · (800) 777-6444

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitSunoco Pipeline L.P.Apr 8, 2022
400
total depth, ft
1
permits on file
Apr 8, 2022
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

32.456369, -100.191752

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Nolan 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
878617-99DrillSunoco Pipeline L.P.Mar 30, 2022Apr 8, 2022—400

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). 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 →

Elisa42-353-33398

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

Coleman Junction2,520-473
Coleman Junction2,520-473
Cisco3,170-1,123
Strawn5,119-3,072
Odom5,334-3,287
Cambrian Sand5,492-3,445
Tannehill—
Wichita-Albany—

15 TOPS · FIRST 8

Whitaker, E. G.42-353-33231

2.6 KM · Mid-Con Energy Operating, LLC · Section with this well →

Strawn5,132-3,099
T/Ellenburger5,506-3,473

Heather42-353-33364

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

Strawn5,074-3,055
Strawn5,078-3,059
Caddo5,438-3,419

McElmurray 'D'42-353-33411

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

Strawn5,081-3,058
Odom5,284-3,261
Caddo5,429-3,406

W.W. McElmurray 'A'42-353-33433

3.3 KM · Mid-Con Energy Operating, LLC · Section with this well →

Coleman Junction2,468-454
Wolfcamp—
Elm Creek - Disposal—
Breckenridge - Disposal—
Flippen Lime - Disposal—
Flippen Sand - Disposal—
King Sand - Disposal—
Noodle Creek - Disposal—

10 TOPS · FIRST 8

Tema-Little42-353-33497

3.3 KM · Mid-Con Energy Operating, LLC · Section with this well →

Coleman Junction2,506-495
Elm Creek - Disposal—
Breckenridge - Disposal—
Flippen Lime - Disposal—
Flippen Sand - Disposal—
King Sand - Disposal—
Noodle Creek - Disposal—
Tannehill—

10 TOPS · FIRST 8

Tema-Little42-353-33496

3.4 KM · Mid-Con Energy Operating, LLC · Section with this well →

Coleman Junction2,480-471
Breckenridge - Disposal—
Wolfcamp—
Wichita-Albany—
Tannehill—
Noodle Creek - Disposal—
King Sand - Disposal—
Flippen Sand - Disposal—

10 TOPS · FIRST 8

WW McElmurray 'B'42-353-33597

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

Coleman Junction2,454-1,263
Coleman Junction2,454-1,263
Noodle Creek - Disposal2,777-1,586
B/Noodle Creek Lime2,823-1,632
B/Cisco Lime3,374-2,183
B/Three Finger Shale4,816-3,625
T/Strawn Sd.5,013-3,822
T/Strawn Sand5,013-3,822

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