WELL · 42-059-37165 · DISTRICT 8

Nctagpd #01

N

Callahan County  · Vertical

Nctagpd #01 (API 42-059-37165) is a permitted well in Callahan County filed by Sunoco Pipeline L.P.; no completion report is on file yet.

The RRC has issued one drilling permit, issued August 25, 2020, permitted to 425 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.Aug 25, 2020
425
total depth, ft
1
permits on file
Aug 25, 2020
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.449479, -99.205724

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Callahan 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
864769-99DrillSunoco Pipeline L.P.Aug 19, 2020Aug 25, 2020—425

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 →

Ames, R.C. -A-42-059-37164

4.0 KM · Clausen, A. G. · Section with this well →

Tannehill2771,143
Gray - Disposal—
Cook Sand - Disposal—
Bunger - Disposal—
Coleman Junction—
Unidentified-County Regular - DI—
Cisco—
Caddo—

10 TOPS · FIRST 8

Wylie A42-059-37200

5.4 KM · Haskit, Kendall · Section with this well →

Coleman Junction101,365
Unidentified-County Regular - DI2611,114
Cisco—
Caddo—
Bunger - Disposal—
Lake Sand - Disposal—
King - Disposal—
Gunsight—

10 TOPS · FIRST 8

Wylie 'Ed'42-059-37178

5.7 KM · Haskit, Kendall · Section with this well →

Coleman Junction2401,216
Gray - Disposal—
Unidentified-County Regular - DI—
Lake Sand - Disposal—
King - Disposal—
Gunsight—
Cook Sand - Disposal—
Cisco—

10 TOPS · FIRST 8

Wylie 'C'42-059-37160

6.0 KM · Haskit, Kendall · Section with this well →

Coleman Junction2901,175
Unidentified-County Regular - DI—
Bunger - Disposal—
Caddo—
Cisco—
Cook Sand - Disposal—
Ellenburger—
Gray - Disposal—

11 TOPS · FIRST 8

Wylie 'C'42-059-37150

6.0 KM · Haskit, Kendall · Section with this well →

Coleman Junction2751,090
Bunger - Disposal—
Unidentified-County Regular - DI—
Lake Sand - Disposal—
King - Disposal—
Gunsight—
Gray - Disposal—
Cook Sand - Disposal—

10 TOPS · FIRST 8

Wylie 'C'42-059-37151

6.1 KM · Haskit, Kendall · Section with this well →

Coleman Junction2801,082
Lake Sand - Disposal—
King - Disposal—
Gunsight—
Gray - Disposal—
Cook Sand - Disposal—
Bunger - Disposal—
Unidentified-County Regular - DI—

10 TOPS · FIRST 8

Wylie 'C'42-059-37159

6.3 KM · Haskit, Kendall · Section with this well →

Coleman Junction2901,175
Caddo—
Cisco—
Cook Sand - Disposal—
Gray - Disposal—
Gunsight—
King - Disposal—
Lake Sand - Disposal—

10 TOPS · FIRST 8

Mask42-059-37029

8.0 KM · Sandstone Services, LLC · Section with this well →

Unidentified-County Regular - DI—
King - Disposal—
Gunsight—
Gray - Disposal—
Ellenburger—
Coleman Junction—
Cisco—
Caddo—

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