PERMITS · OKLAHOMA · NEWEST APPROVAL FIRST
M and V Resources 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.
A full API number opens the well. Anything else filters the list below.
5 intents to drill match
Wellbore
Since approval
5 INTENTS TO DRILL · PAGE 1 OF 1
| Approved | Well | Operator | County | Permit for | Proposed formation | Target depth | Now |
|---|---|---|---|---|---|---|---|
| Aug 23, 2006 | Hill #235-083-21139 | M and V Resources Inc | Logan | Recompletion | Red Fork | 6,215 ft | SpuddedApr 1, 1979 |
| Nov 29, 2000 | Meier (Heg Meier 1) #135-047-24168 | M and V Resources Inc | Garfield | Re-entry | Mississippi Chat | 5,600 ft | SpuddedJun 24, 1994 |
| Nov 3, 1998 | Holly E #33-135-083-23427 | M and V Resources Inc | Logan | New drill | Carmichael, Layton Low, Layton UP, Oswego, Skinner, Viola, Wilcox 2 | 6,500 ft | SpuddedNov 10, 1998 |
| Feb 6, 1997 | Marie #135-083-23356 | M and V Resources Inc | Logan | Recompletion | Avant, Layton, Perry | 5,700 ft | SpuddedSep 23, 1996 |
| Sep 27, 1993 | Eddie Johnson #135-083-23230 | M and V Resources Inc | Logan | New drilllatest filing: Amend | Carmichael, Cleveland, Layton, Oswego | 6,350 ft | SpuddedAug 19, 1993 |
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.