WELL · 42-485-46265 · DISTRICT 13

KD-23 #1

N

Wichita County  · Vertical

KD-23 #1 (API 42-485-46265) is a permitted well in Wichita County filed by Texoma Copc, LLC; no completion report is on file yet.

The RRC has issued one drilling permit, issued August 24, 2020, permitted to 320 ft.

Operator of record

Texoma Copc, LLC

Denver, CO · P-5 Y, filed Jul 4, 2026 · 6 permits on file · (360) 768-2015

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitTexoma Copc, LLCAug 24, 2020
320
total depth, ft
1
permits on file
Aug 24, 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

34.122282, -98.642605

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Wichita 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
864530-99DrillTexoma Copc, LLCAug 3, 2020Aug 24, 2020—320

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 →

SKR Trust42-485-46252

3.1 KM · Felty Drilling Co. Inc · Section with this well →

Gunsight1,650-574
Vogstberger—
Thomas Sand—
Tannehill—
Strawn—
KMA—
Canyon—
Bluff Creek Sand—

10 TOPS · FIRST 8

SKR Trust42-485-46253

3.1 KM · Felty Drilling Co. Inc · Section with this well →

Gunsight1,640-564
Canyon—
Bluff Creek Sand—
Cisco—
Gunsight—
KMA—
Strawn—
Tannehill—

10 TOPS · FIRST 8

Holcomb, D.E.42-485-46268

6.9 KM · Canyon Ridge Energy LLC · Section with this well →

Gunsight840248
Cisco1,200-112
KMA—
Strawn—
Tannehill—
Thomas Sand—
Vogstberger—
Canyon—

10 TOPS · FIRST 8

Holcomb, D.E.42-485-46267

7.0 KM · Canyon Ridge Energy LLC · Section with this well →

Cisco1,200-114
Gunsight1,520-434
Canyon—
Bluff Creek Sand—
Vogstberger—
Thomas Sand—
Tannehill—
Strawn—

10 TOPS · FIRST 8

SLC Ramming42-485-46413

7.3 KM · Stone, Gregory W. · Section with this well →

Thomas Sand520
Gunsight1,750
Vogstberger—
Bluff Creek Sand—
Canyon—
Cisco—
Gunsight—
KMA—

10 TOPS · FIRST 8

Stone Ramming42-485-44588

7.4 KM · Stone, Gregory W. · Section with this well →

Thomas Sand520
Gunsight1,750
Vogstberger—
Tannehill—
KMA—
Gunsight—
Bluff Creek Sand—
Cisco—

10 TOPS · FIRST 8

SLC Ramming42-485-46384

7.6 KM · Stone, Gregory W. · Section with this well →

Tannehill1,012
Thomas Sand1,510
Gunsight1,750
Cisco1,881
Vogstberger—
Bluff Creek Sand—
Canyon—
Gunsight—

10 TOPS · FIRST 8

Preston B42-485-46064

8.4 KM · Newport Operating, LLC · Section with this well →

Cisco200
Tannehill300
Canyon—
Vogstberger—
Thomas Sand—
Strawn—
KMA—
Gunsight—

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