WELL · 42-101-30759 · DISTRICT 8

Shonda #1

Plugged

Cottle County · Wildcat field  · Vertical

Shonda #1 (API 42-101-30759) is a plugged well in Cottle County, plugged November 7, 2021, last operated by Gunn Oil Company.

The RRC has issued one drilling permit, issued August 25, 2021, permitted to 9,000 ft.

It was permitted by Gunn Oil Company and has since transferred to Gunn Oil Company on the wellbore schedule.

Operator of record

Gunn Oil Company

Permitted by Gunn Oil Company; the EWA schedule now lists a different operator.

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitGunn Oil CompanyAug 25, 2021

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

9,000
total depth, ft
1
permits on file
Aug 25, 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
Nov 7, 2021

Surface location

33.841825, -100.092309

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Cottle 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
872121-99DrillGunn Oil CompanyAug 18, 2021Aug 25, 2021Oct 29, 20219,000

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 →

Sallie Lee42-269-33034

9.1 KM · Gunn Oil Company · Section with this well →

Coleman Junction2,492-693
Cisco3,738-1,939
Bunger4,044-2,245
Canyon4,375-2,576
Pennsylvanian—
Caddo—
Des Moines—
Tannehill—

10 TOPS · FIRST 8

Sallie Lee42-269-33059

9.3 KM · Gunn Oil Company · Section with this well →

Coleman Junction2,494-695
Tannehill3,110-1,311
Cisco4,045-2,246
Bunger4,094-2,295
Canyon4,390-2,591
Caddo—
Conglomerate—
Strawn—

10 TOPS · FIRST 8

Masterson 'B'42-269-00057

10.3 KM · P.B. Blue Dot Properties · Section with this well →

Strawn5,356-3,639
Bend5,830-4,113
Mississippian5,854-4,137

Johnson, L. K.42-155-30815

13.4 KM · NWG Operating LLC · Section with this well →

Coleman Junction1,967-347
Tannehill2,457-837
Gunsite3,325-1,705
Cisco3,629-2,009
Canyon3,730-2,110
Palo Pinto—
Bend—
Caddo—

10 TOPS · FIRST 8

Mimsy42-269-33035

14.3 KM · Gunn Oil Company · Section with this well →

Coleman Junction2,499-700
Cisco3,723-1,924
Bunger4,143-2,344
Canyon4,858-3,059
Strawn5,365-3,566
Conglomerate—
Caddo—
Pennsylvanian—

10 TOPS · FIRST 8

LK Johnson42-155-30810

14.4 KM · NWG Operating LLC · Section with this well →

Coleman Junction1,924-315
Gunsite3,233-1,624
Canyon3,564-1,955
Strawn—
Palo Pinto—
Cisco—
Caddo—
Bend—

10 TOPS · FIRST 8

L.K. Johnson42-155-30808

14.7 KM · NWG Operating LLC · Section with this well →

Coleman Junction1,920-296
Tannehill2,440-816
Gunsite3,234-1,610
Cisco3,500-1,876
Canyon3,536-1,912
Caddo—
Palo Pinto—
Raspberry—

10 TOPS · FIRST 8

L.K. Johnson42-101-30755

14.8 KM · NWG Operating LLC · Section with this well →

Gunsight3,300-1,636
Tannehill—
Strawn—
Rasperry—
Palo Pinto—
Cisco—
Coleman Junction—
Canyon—

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