WELL · 42-269-32972 · DISTRICT 8

Warren #3

Plugged

King County · Tumbleweed NE. (Tannehill) field  · Vertical

Warren #3 (API 42-269-32972) is a plugged well in King County, plugged December 7, 2017, last operated by Schalk Oil Company Inc..

The RRC has issued one drilling permit, issued October 30, 2017, permitted to 4,400 ft.

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

Operator of record

Schalk Oil Company Inc.

Permitted by Schalk Oil Company, Inc.; the EWA schedule now lists a different operator.

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitSchalk Oil Company, Inc.Oct 30, 2017

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

4,400
total depth, ft
1
permits on file
Oct 30, 2017
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
Dec 7, 2017

Surface location

33.493611, -100.488200

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in King 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
832440-99DrillSchalk Oil Company, Inc.Oct 26, 2017Oct 30, 2017Nov 30, 20174,400

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 →

Pitchfork Yyy42-269-33045

4.3 KM · Medders Oil Company, Inc. · Section with this well →

Coleman Junction3,228-1,250
Tannehill3,778-1,800
Pennsylvanian—
Des Moines—
Conglomerate—
Cisco—
Canyon—
Bunger—

10 TOPS · FIRST 8

Forks South Balt Unit42-269-32992

4.8 KM · Medders Oil Company, Inc. · Section with this well →

Coleman Junction3,115-1,109
Tannehill3,775-1,769
Tannehill3,858-1,852
Strawn—
Bunger—
Caddo—
Canyon—
Cisco—

11 TOPS · FIRST 8

Four Sixes 'B'42-269-32984

5.3 KM · Burnett Oil Co., Inc. · Section with this well →

Coleman Junction3,030-1,088
Pennsylvanian3,030-1,088
Tannehill3,745-1,803
Cisco4,792-2,850
Bunger4,881-2,939
Canyon5,541-3,599
Strawn5,753-3,811
Des Moines5,753-3,811

10 TOPS · FIRST 8

Forks South Balt Unit42-269-32394

6.6 KM · Medders Oil Company, Inc. · Section with this well →

Coleman Junction3,076-1,140
Tannehill3,733-1,797

Springer 'A'42-269-33014

7.1 KM · Sojourner Drilling Corporation · Section with this well →

Coleman Junction3,215-1,283
Tannehill3,708-1,776
Strawn5,589-3,657

Pitchfork Tttt42-269-33051

7.4 KM · Medders Oil Company, Inc. · Section with this well →

Coleman Junction3,238-1,249
Tannehill3,777-1,788
Des Moines—
Conglomerate—
Cisco—
Canyon—
Caddo—
Bunger—

10 TOPS · FIRST 8

Pitchfork42-269-33050

7.7 KM · Burnett Oil Co., Inc. · Section with this well →

Coleman Junction3,084-1,057
Tannehill3,769-1,742
Cisco—
Bunger—
Caddo—
Canyon—
Conglomerate—
Des Moines—

10 TOPS · FIRST 8

Pitchfork Parker42-269-32976

9.0 KM · Cholla Petroleum, Inc. · Section with this well →

Coleman Junction3,188-1,167
Cisco3,680-1,659
Tannehill3,770-1,749
Canyon—
Caddo—
Bunger—
Conglomerate—
Des Moines—

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