PERMITS · OKLAHOMA · NEWEST APPROVAL FIRST
Westend Operating 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 |
|---|---|---|---|---|---|---|---|
| Feb 22, 2006 | Payne Fee Wft(payne Fee WFT HP2) #P7HZ35-131-25098 | Westend Operating LLC | Rogers | New drill | Bartlesville | 976 ft | SpuddedOct 7, 2006 |
| Feb 22, 2006 | Payne Fee WFT #hp-3HZ35-131-25099 | Westend Operating LLC | Rogers | New drill | Bartlesville | 976 ft | SpuddedJul 4, 2006 |
| Feb 22, 2006 | Payne Fee Wft(payne Fee WFT HP4) #P14HZ35-131-25110 | Westend Operating LLC | Rogers | New drill | Bartlesville | 976 ft | SpuddedOct 6, 2006 |
| Feb 22, 2006 | Payne Fee WFT #hp-5HZ35-131-25111 | Westend Operating LLC | Rogers | New drill | Bartlesville | 976 ft | SpuddedJul 8, 2006 |
| Feb 22, 2006 | Payne Fee Wft(payne Fee WFT HP6) #P3HZ35-131-25112 | Westend Operating LLC | Rogers | New drill | Bartlesville | 976 ft | SpuddedOct 6, 2006 |
| Feb 17, 2006 | Payne Fee WFT #hp-1HZ35-131-25095 | Westend Operating LLC | Rogers | New drill | Bartlesville | 976 ft | SpuddedJul 1, 2006 |
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.