PERMITS · OKLAHOMA · NEWEST APPROVAL FIRST
Thunder Petroleum 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.
Wellbore
Since approval
6 INTENTS TO DRILL · PAGE 1 OF 1
| Approved | Well | Operator | County | Permit for | Proposed formation | Target depth | Now |
|---|---|---|---|---|---|---|---|
| Nov 8, 2013 | Harjo Ralston #2635-143-24278 | Thunder Petroleum LLC | Tulsa | New drill | Bartlesville | 1,600 ft | No evidence of a well |
| Nov 8, 2013 | Harjo Ralston #2535-143-24279 | Thunder Petroleum LLC | Tulsa | New drill | Bartlesville | 1,600 ft | No evidence of a well |
| Nov 8, 2013 | Harjo Ralston #2435-143-24280 | Thunder Petroleum LLC | Tulsa | New drill | Bartlesville | 1,600 ft | No evidence of a well |
| Oct 9, 2013 | Harjo Ralston #2135-143-24263 | Thunder Petroleum LLC | Tulsa | New drill | Glenn | 1,600 ft | Shut in by final order |
| Dec 12, 2012 | Whiskey Tango 2 #a35-143-24258 | Thunder Petroleum LLC | Tulsa | New drill | Bartlesville, Burgess, Red Fork, Tucker | 1,500 ft | Shut in by final order |
| Jul 23, 2012 | Eddingfield #1A35-143-24249 | Thunder Petroleum LLC | Tulsa | New drilllatest filing: Amend | Bartlesville, Burgess, Tucker | 1,500 ft | SpuddedJul 25, 2012 |
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.