OKLAHOMA · WELLS · KAY COUNTY · API 35-071-24352

State of Mind #1-16

PluggedVertical terminated uic well wellOCC status: Plugged and abandoned

County
Kay
Formation
Red Fork

A vertical terminated uic well well in Kay County, Oklahoma, operated by Xanadu Exploration Company. OCC status: plugged and abandoned.

Spudded May 3, 2010 and drilled to 3,436 ft measured depth.

Completed in 2 formations: Mississippi Chat, Red Fork.

It has taken 718,590 bbl of injected water since May 2011.

Wells nearby

Every well with a location on file around this one, in any state, nearest first.

Open the full map →

Reported injection

718,590 bbl of water injected since May 2011. Reported through Dec 2025. The injection record here begins in 2011; injection before then is not shown.

12 months through Dec 2025 0 · prior 12 0

050K100K20122013201420152016201720182019202020212022202320242025

State of Mind #1-16: Injected water by month.

Completions

ONE PER FORMATION THE WELL IS COMPLETED IN

FormationStatusPerforations, ftCompleted
Mississippi ChatPlugged · Mit3,366 to 3,374May 27, 2010
Red ForkPlugged · Mit3,253 to 3,267May 27, 2010

Well record

API number
35-071-24352
Location
N2 SW SW NW-16-28N-03E · 510 FSL, 330 FWL
Ground elevation
1,153 ft
Measured depth
3,436 ft
Perforations
3,253 to 3,374 ft
Intent to drill
Approved Feb 22, 2010
Proposed formation
Cleveland, Layton, Mississippi Chat, Red Fork
Target depth
3,550 ft
Spudded
May 3, 2010

No oil or gas production is available for this well.

About this data

Oklahoma Corporation Commission (OCC), Oil and Gas Conservation Division. The well, its status, and its type are from the Commission's well file, in OCC's own words; the intent to drill, dates, depths, and formations are from the well's own filings. Injection is what the operator filed on form 1012A, by month; twelve-month figures end in Dec 2025, the last month whose filings are in. No oil or gas production is available for Oklahoma. Nothing is estimated.

Developers: this page as JSON is GET /v1/data/wells/3507124352, documented in the API reference.