WELL · 42-485-46289 · DISTRICT 9

PBR #P 3

Plugged

Wichita County · Wildcat field  · Vertical

Pbr #P 3 (API 42-485-46289) is a plugged well in Wichita County, plugged May 12, 2021, last operated by Kelsey Operating Inc..

The RRC has issued one drilling permit, issued April 13, 2021, permitted to 7,500 ft.

It was permitted by Kelsey Operating, Inc. and has since transferred to Kelsey Operating Inc. on the wellbore schedule.

Operator of record

Kelsey Operating Inc.

Permitted by Kelsey Operating, Inc.; the EWA schedule now lists a different operator.

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitKelsey Operating, Inc.Apr 13, 2021

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

7,500
total depth, ft
1
permits on file
Apr 13, 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
May 12, 2021

Surface location

34.054433, -98.825034

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
869045-99DrillKelsey Operating, Inc.Apr 9, 2021Apr 13, 2021Apr 21, 20217,500

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 →

Gillis, Bruce42-485-46365

0.9 KM · Bonfire Operating LLC · Section with this well →

Tannehill950188
Cisco1,200-62
Thomas Sand1,370-232
Gunsight1,550-412
Gunsight1,560-422
Canyon1,570-432
Bluff Creek Sand1,600-462
Strawn1,890-752

10 TOPS · FIRST 8

Hill -A-42-485-46279

1.6 KM · S&G Oil LLC · Section with this well →

Tannehill435
Cisco1,130
Thomas Sand1,446
Gunsight1,884
Gunsight1,918
Strawn—
Vogstberger—
KMA—

10 TOPS · FIRST 8

Hill42-485-46240

1.7 KM · S&G Oil LLC · Section with this well →

Tannehill450
Cisco950
Thomas Sand1,660
Gunsight1,920
Gunsight1,930
Vogstberger—
Strawn—
KMA—

11 TOPS · FIRST 8

Parrish42-485-46298

1.7 KM · S&G Oil LLC · Section with this well →

Tannehill440
Cisco1,120
Thomas Sand1,524
Gunsight1,868
Gunsight1,890
Vogstberger—
Bluff Creek Sand—
Canyon—

10 TOPS · FIRST 8

Parrish42-485-46251

1.7 KM · S&G Oil LLC · Section with this well →

Tannehill420
Cisco1,200
Thomas Sand1,550
Gunsight1,880
Gunsight1,890
Bluff Creek Sand—
KMA—
Strawn—

10 TOPS · FIRST 8

Parrish42-485-46314

1.8 KM · S&G Oil LLC · Section with this well →

Cisco672
Thomas Sand1,546
Bluff Creek Sand—
Caddo—
Canyon—
Gunsight—
Gunsight—
KMA—

10 TOPS · FIRST 8

Parrish42-485-46299

1.8 KM · S&G Oil LLC · Section with this well →

Tannehill450
Cisco1,130
Thomas Sand1,530
Gunsight1,874
Gunsight1,900
Vogstberger—
Canyon—
Bluff Creek Sand—

10 TOPS · FIRST 8

Parrish42-485-46278

1.8 KM · S&G Oil LLC · Section with this well →

Tannehill440
Cisco820
Thomas Sand1,540
Gunsight1,886
Gunsight1,910
Strawn—
Canyon—
Vogstberger—

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