WELL · 42-485-46092 · DISTRICT 9

Dunn J. Z. #41S

Plugged

Wichita County · Wichita County Gunsight field  · Vertical

Dunn J. Z. #41S (API 42-485-46092) is a plugged well in Wichita County, plugged March 13, 2018, last operated by Rog Enterprises Inc..

The RRC has issued one drilling permit, issued February 14, 2018, permitted to 2,000 ft.

It was permitted by Rog Enterprises, LLC and has since transferred to Rog Enterprises Inc. on the wellbore schedule.

Operator of record

Rog Enterprises Inc.

Permitted by Rog Enterprises, LLC; the EWA schedule now lists a different operator.

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitRog Enterprises, LLCFeb 14, 2018

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

2,000
total depth, ft
1
permits on file
Feb 14, 2018
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
Mar 13, 2018

Surface location

34.051817, -98.512568

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
836328-99DrillRog Enterprises, LLCFeb 13, 2018Feb 14, 2018Mar 12, 20182,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 →

Dunn, J. Z.42-485-46029

0.1 KM · Rog Enterprises, LLC · Section with this well →

Tannehill660
Vogstberger—
Thomas Sand—
Bluff Creek Sand—
Canyon—
Strawn—
KMA—
Gunsight—

10 TOPS · FIRST 8

Dunn, J. Z.42-485-46093

0.2 KM · Rog Enterprises, LLC · Section with this well →

Cisco930
Canyon—
Vogstberger—
Thomas Sand—
Tannehill—
Strawn—
KMA—
Gunsight—

10 TOPS · FIRST 8

Dunn, J. Z.42-485-46027

0.3 KM · Rog Enterprises, LLC · Section with this well →

Gunsight1,310
Bluff Creek Sand—
Canyon—
Vogstberger—
Thomas Sand—
Tannehill—
Strawn—
KMA—

10 TOPS · FIRST 8

Dunn, J. Z.42-485-46099

0.4 KM · Rog Enterprises, LLC · Section with this well →

Cisco940
Bluff Creek Sand—
Canyon—
Gunsight—
Gunsight—
KMA—
Strawn—
Tannehill—

10 TOPS · FIRST 8

Dunn, J. Z.42-485-46032

0.4 KM · Rog Enterprises, LLC · Section with this well →

Gunsight1,310
Gunsight1,400
Tannehill—
Strawn—
KMA—
Thomas Sand—
Vogstberger—
Canyon—

10 TOPS · FIRST 8

Crackerbox42-485-46190

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

Cisco868139
Thomas Sand1,218-211
Gunsight1,314-307
Bluff Creek Sand—
Gunsight—
Canyon—
Vogstberger—
Tannehill—

10 TOPS · FIRST 8

Crackerbox42-485-46191

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

Cisco822181
Thomas Sand1,052-49
Gunsight1,283-280
Gunsight1,372-369
Tannehill—
KMA—
Strawn—
Vogstberger—

10 TOPS · FIRST 8

Roller Estate42-485-46041

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

Cisco200
Tannehill300
Thomas Sand1,150
Gunsight1,306
Gunsight1,436
Vogstberger—
Bluff Creek Sand—
KMA—

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