PERMITS · OKLAHOMA · NEWEST APPROVAL FIRST

KCS Resources LLC intents to drill

In Oklahoma a drilling permit is an intent to drill, approved by OCC. A well can hold several: the first, its amendments, a recompletion. This is one row per well under its newest approved intent, with what has happened since. For intents approved since mid-2025 the wellbore type and target formation are not in the data yet, so the newest rows show a depth and a dash for the rest.

8 INTENTS TO DRILL · PAGE 1 OF 1

ApprovedWellOperatorCountyPermit forProposed formationTarget depthNow
Jan 16, 2004Reed #24-1 35-079-21587KCS Resources LLCLe FloreNew drillAmendJackfork Low, Jackfork UP8,150Spudded Feb 7, 2004
Aug 4, 2003Buckner #30-1 35-121-22997KCS Resources LLCPittsburgNew drillAmendAtoka UP6,500Spudded Sep 10, 2003
Feb 15, 2002Scott #1 35-127-20052KCS Resources LLCPushmatahaNew drillJackfork Series RPTD1 Subthrst6,000Spudded Feb 22, 2002
Jun 14, 2001Angel #1 35-077-21277KCS Resources LLCLatimerNew drillAmendBullard (Atoka Low)11,000Spudded Aug 8, 2001
Apr 2, 1998Farris #1-3 35-149-20822KCS Resources LLCWashitaNew drillAmendPennsylvanian Granite Wash10,300Spudded Apr 7, 1998
Apr 21, 1997Alspaugh #27-1 35-137-25356KCS Resources LLCStephensRecompletionNiles, Permian, Rowe /Cement Chickasha/3,300Spudded Dec 23, 1996
Feb 13, 1997Sue Ellen #29-1 35-045-21919KCS Resources LLCEllisNew drillChester LM, Morrow SD8,950Spudded Feb 13, 1997
Nov 20, 1996Bette Anne #26-1 35-137-25344KCS Resources LLCStephensRe-entryDeese, Dornick Hills UP, Hoxbar8,800Spudded Oct 6, 1996

About this data

Oklahoma Corporation Commission: the latest intent to drill on each well record, with its approval date, the formation and depth the operator proposed, and the well's spud date where one is on file. A well whose intent to drill was re-approved appears once, under its latest approval. What the intent to drill is for is OCC's application type, in shared words with OCC's own beside them. Nothing is estimated.

Developers: this page as JSON is GET /v1/data/permits?state=ok, documented in the API reference.