WELL · 42-125-31368 · DISTRICT 8
Cloud #1
Dickens County · Soldier Mound (Tannehill) field · Vertical
Cloud #1 (API 42-125-31368) is a plugged well in Dickens County, plugged September 21, 2017, last operated by VX Operating LLC.
The RRC has issued one drilling permit, issued July 7, 2017, permitted to 6,300 ft.
It was permitted by VX Operating, LLC and has since transferred to VX Operating LLC on the wellbore schedule.
Operator of record
VX Operating LLC
Permitted by VX Operating, LLC; the EWA schedule now lists a different operator.
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | none |
| Latest permit | VX Operating, LLCJul 7, 2017 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 6,300
- total depth, ft
- 1
- permits on file
- Jul 7, 2017
- last permit issued
- —
- completed
- —
- cumulative oil, bbl
- —
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- —
- Shut in
- —
- Plugged
- Sep 21, 2017
Surface location
33.539128, -100.853766
OpenStreetMap → · Google Maps →
Permit surface location from the RRC GIS record, in Dickens County.
Only the permit record exists for this well so far, here and in the RRC's wellbore query. Completion reports, formation tops, lease production, and the scanned filings appear once the operator files a completion report, typically months after drilling. Petrora refreshes the wellbore file weekly, so a filing from the last few days may reach the RRC before it shows here. How long each source takes →
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 828576-99 | Drill | VX Operating, LLC | Jul 7, 2017 | Jul 7, 2017 | Sep 8, 2017 | 6,300 |
The source documents
Petrora holds the structured record. The scanned filings live at the RRC; these links open its search already filled in for this API.
- Wellbore filings for 42-125-31368 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-125-31368 → scanned completion filings
Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward). then paste it into their search.
Nearby wells and their tops
NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM
Draw a cross-section
This well has no tops filed, so it cannot anchor a section; its neighbours can.
Condron42-125-31386
3.4 KM · Cypress Production, Inc. · Section with this well →
| Coleman Junction | 4,235 | -1,917 |
| Tannehill | 4,808 | -2,490 |
| Atkins | — | |
| Canyon | — |
Barron42-125-31376
4.9 KM · Carroll Operating, LLC · Section with this well →
| Coleman Junction | 4,284 | -2,004 |
| Tannehill | 4,898 | -2,618 |
| Atkins | — | |
| Canyon | — |
Neaves42-125-31369
5.2 KM · Halliburton Operating Company · Section with this well →
| Coleman Junction | 2,800 | |
| Tannehill | 4,812 | |
| Atkins | — | |
| Canyon | — |
Holly42-125-31409
6.7 KM · Halliburton Operating Company · Section with this well →
| Coleman Junction | 1,740 | 547 |
| Tannehill | 4,678 | -2,391 |
| Canyon | — | |
| Atkins | — |
Sjwf42-125-31399
10.6 KM · Halliburton Operating Company · Section with this well →
| Coleman Junction | 1,360 | 936 |
| Tannehill | 4,636 | -2,340 |
| Canyon | — | |
| Atkins | — |
Sjwf42-125-31405
10.7 KM · Halliburton Operating Company · Section with this well →
| Coleman Junction | 4,000 | -1,712 |
| Tannehill | 4,634 | -2,346 |
| Atkins | — | |
| Canyon | — |
Maben42-125-31373
14.9 KM · Chisholm Operating, Inc. · Section with this well →
| Tannehill | 4,300 | -1,989 |
| Coleman Junction | 4,405 | -2,094 |
| Woods Lime | 5,334 | -3,023 |
| Atkins | — | |
| Canyon | — |
Spring Fecta42-125-31371
15.2 KM · Canan Mowrey Operating, LLC · Section with this well →
| Coleman Junction | 4,436 | -2,113 |
| Tannehill | 5,129 | -2,806 |
| Canyon | — | |
| Atkins | — |
About this data
Permits from the RRC OGA049M master and daily daf420 files; wellbore and operator of record from the EWA schedule, weekly; completions, formation tops, casing, and perforations from the dbf900 wellbore file; production from PDQ lease reports, which lag two to three months; injection from UIC permits, H-10 reports, and TexNet daily volumes; earthquakes from the TexNet catalog.
New to these records? How to read a well page · API numbers · completion reports and tops · why production is by lease
Developers: this page as JSON is GET /v1/data/wells/12531368, documented in the API reference.