WELL · 42-219-37422 · DISTRICT 8

Spade K #1

Plugged

Hockley County · Wildcat field  · Vertical

Spade K #1 (API 42-219-37422) is a plugged well in Hockley County, plugged November 3, 2017, last operated by Canan Mowrey Operating LLC.

The RRC has issued one drilling permit, issued September 20, 2017, permitted to 12,000 ft.

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

Operator of record

Canan Mowrey Operating LLC

Permitted by Canan Mowrey 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 permitCanan Mowrey Operating, LLCSep 20, 2017

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

12,000
total depth, ft
1
permits on file
Sep 20, 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
Nov 3, 2017

Surface location

33.561563, -102.207831

Google Maps ↗

Permit surface location from the RRC GIS record, in Hockley 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
830979-99DrillCanan Mowrey Operating, LLCSep 14, 2017Sep 20, 2017Oct 11, 201712,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 neighbors can.

Section of the neighbors →

Spade L42-219-37425

1.0 KM · Canan Mowrey Operating, LLC · Section with this well →

Santa Rosa1,1002,297
Yates2,730667
San Andres3,936-539
Clear Fork5,990-2,593
Abo7,458-4,061
Wolfcamp8,227-4,830
Wichita-Albany8,303-4,906
Cisco9,634-6,237

10 TOPS · FIRST 8

Spade M42-219-37442

1.3 KM · Canan Mowrey Operating, LLC · Section with this well →

Santa Rosa1,1002,304
Yates2,742662
San Andres3,945-541
Clear Fork6,006-2,602
Canyon—
Wolfcamp—
Wichita-Albany—
Strawn—

10 TOPS · FIRST 8

Brown42-219-81949

5.7 KM · Texland Petroleum, L.P. · Section with this well →

San Andres5,028-1,633
Glorieta5,472-2,077
Clear Fork6,038-2,643

Brown42-219-33735

5.9 KM · Texland Petroleum, L.P. · Section with this well →

Rustler2,1001,291
Yates2,692699
Seven Rivers2,846545
San Andres3,963-572
Glorieta5,487-2,096
Clear Fork6,066-2,675

Young-Hankins42-219-34444

6.0 KM · Young, Marshall R., Oil Company · Section with this well →

Rustler2,140309
Yates2,755-306
San Andres4,140-1,691
Clear Fork6,040-3,591
Dean7,695-5,246
Strawn10,098-7,649

Newsom 'B'42-219-37492

6.2 KM · Texland Petroleum, L.P. · Section with this well →

Santa Rosa1,4101,973
Yates2,674709
San Andres3,394-11
Clear Fork6,062-2,679
Wolfcamp—
Abo—
Canyon—
Cisco—

10 TOPS · FIRST 8

Covey42-219-37502

7.1 KM · Burk Royalty Co., Ltd. · Section with this well →

Santa Rosa1,4002,016
Yates2,675741
San Andres3,39026
Clear Fork6,100-2,684
Abo—
Strawn—
Wichita-Albany—
Wolfcamp—

10 TOPS · FIRST 8

Pointer42-219-37516

7.1 KM · Burk Royalty Co., Ltd. · Section with this well →

Clear Fork6,367-2,950
Santa Rosa—
San Andres—
Strawn—
Wichita-Albany—
Wolfcamp—
Yates—
Abo—

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