PERMITS · OKLAHOMA · NEWEST APPROVAL FIRST

Mark L Shidler Inc 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.

7 INTENTS TO DRILL · PAGE 1 OF 1

ApprovedWellOperatorCountyPermit forProposed formationTarget depthNow
Sep 14, 2004Claudine #1-5HZ35-121-23274Mark L Shidler IncPittsburgNew drillHartshorne7,445 ftSpuddedSep 25, 2004
Nov 24, 2003Earl #1-4HZ35-121-23059Mark L Shidler IncPittsburgNew drilllatest filing: AmendHartshorne5,007 ftSpuddedDec 8, 2003
May 5, 2003Ainsworth #1-3335-121-29931Mark L Shidler IncPittsburgNew drillCromwell, Spiro, Wapanucka5,400 ftSpuddedMay 15, 2003
Feb 15, 2001Forman #23 #1HHZ35-073-24431Mark L Shidler IncKingfisherNew drillHunton, Mississippi LM, Oswego, Prue10,042 ftSpuddedFeb 22, 2001
Dec 8, 2000Cryer #16 #135-049-24249Mark L Shidler IncGarvinNew drilllatest filing: AmendArbuckle, Bromide, Cisco, Hunton, McLish, Oil Creek, Springer, Sycamore, Viola, Woodford12,500 ftSpuddedJan 10, 2001
May 30, 1997Forest Baird #16-435-151-22190Mark L Shidler IncWoodsNew drillChester, Meramec, Osage7,300 ftSpuddedJun 6, 1997
Sep 21, 1995Hayworth #9-135-011-22625Mark L Shidler IncBlaineNew drillBig Lime, Chester Unconf, Manning, Oswego, Red Fork8,000 ftSpuddedSep 24, 1995

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.