WELL · 42-269-32975 · DISTRICT 8

Springer #1933

Plugged

King County · Christopher (Lower Tannehill) field  · Vertical

Springer #1933 (API 42-269-32975) is a plugged well in King County, plugged March 21, 2018, last operated by Covenant Operating LLC.

The RRC has issued one drilling permit, issued February 16, 2018, permitted to 4,000 ft.

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

Operator of record

Covenant Operating LLC

Permitted by Covenant Operating, LLC; the EWA schedule now lists a different operator.

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitCovenant Operating, LLCFeb 16, 2018

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

4,000
total depth, ft
1
permits on file
Feb 16, 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 21, 2018

Surface location

33.455389, -100.450111

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
836536-99DrillCovenant Operating, LLCFeb 16, 2018Feb 16, 2018Mar 14, 20184,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 →

Springer 'A'42-269-33014

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

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

Springer '196'42-269-32977

5.4 KM · TDC Engineering, Inc. · Section with this well →

Strawn—
Pennsylvanian—
Des Moines—
Conglomerate—
Coleman Junction—
Cisco—
Caddo—
Bunger—

10 TOPS · FIRST 8

Four Sixes 'B'42-269-32984

7.7 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
Des Moines5,753-3,811
Strawn5,753-3,811

10 TOPS · FIRST 8

Forks South Balt Unit42-269-32992

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

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

11 TOPS · FIRST 8

Pitchfork Yyy42-269-33045

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

Coleman Junction3,228-1,250
Tannehill3,778-1,800
Conglomerate—
Strawn—
Bunger—
Caddo—
Canyon—
Cisco—

10 TOPS · FIRST 8

Pitchfork42-269-33050

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

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

10 TOPS · FIRST 8

Forks South Balt Unit42-269-32394

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

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

Hot Springs42-263-32174

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

Clear Fork1,090899
Wichita-Albany1,300689
Coleman Junction3,150-1,161
Noodle Creek3,748-1,759
Wolfcamp—
Yates—
Canyon—
Fuller—

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