WELL · 42-355-34187 · DISTRICT 4

Cathodic Protection #2505MS

N

Nueces County  · Vertical

Cathodic Protection #2505MS (API 42-355-34187) is a permitted well in Nueces County filed by Kinder Morgan Tejas Pipeline LLC; no completion report is on file yet.

The RRC has issued one drilling permit, issued August 13, 2020, permitted to 600 ft.

Operator of record

Kinder Morgan Tejas Pipeline LLC

Houston, TX · P-5 Y, filed Mar 4, 2026 · 20 permits on file · (800) 568-7512

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitKinder Morgan Tejas Pipeline LLCAug 13, 2020
600
total depth, ft
1
permits on file
Aug 13, 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

27.753465, -97.791525

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Nueces 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
864558-99DrillKinder Morgan Tejas Pipeline LLCAug 4, 2020Aug 13, 2020—600

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 →

Kittoe42-355-34230

2.4 KM · Pangea's Edge Operating Co LLC · Section with this well →

Miocene (undifferentiated)2,403-2,321
Catahoula2,908-2,826
Catahoula3,887-3,805
Vicksburg7,726-7,644

Roddy Ripple G.U.42-355-34216

3.6 KM · Suemaur Expl. & Prod., LLC · Section with this well →

Miocene (undifferentiated)2,500-2,419
Catahoula4,010-3,929
Catahoula4,700-4,619
Vicksburg8,300-8,219

Scarborough42-355-34208

3.6 KM · Suemaur Expl. & Prod., LLC · Section with this well →

Miocene (undifferentiated)2,500-2,426
Catahoula3,950-3,876
Catahoula4,700-4,626
Vicksburg8,300-8,226

Crane42-355-34215

4.8 KM · Cimarron Engineering, LLC · Section with this well →

Miocene (undifferentiated)1,772-1,695
Catahoula2,122-2,045
Catahoula3,950-3,873
Vicksburg—

Liska-Norris42-355-34182

4.9 KM · Rincon Petroleum Corporation · Section with this well →

Miocene (undifferentiated)1,000-926
Catahoula3,020-2,946
Catahoula4,070-3,996
Vicksburg—

Driscoll Foundation42-355-34228

5.2 KM · Paloma Operating, LLC · Section with this well →

Miocene (undifferentiated)2,450-2,375
Catahoula3,998-3,923
Catahoula4,568-4,493
Vicksburg—

Ingram, J.C.42-355-04732

5.7 KM · Urban Oil & Gas Group, LLC · Section with this well →

Austin Chalk6,912-6,808

Dugger, L.M.42-355-33936

5.9 KM · Sue-Ann Operating, L.C. · Section with this well →

Miocene (undifferentiated)2,600-2,531
Catahoula3,970-3,901
Catahoula4,350-4,281
Frio5,610-5,541
Greta7,271-7,202
Vicksburg—

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