TEXAS · WELLS · CULBERSON COUNTY · CAVALCADE 25 UNIT LEASE · API 42-109-32827 · DISTRICT 7B
Cavalcade 25 Unit #1H
Culberson County · Ford West (Wolfcamp) field · Producing · Horizontal
Cavalcade 25 Unit #1H (API 42-109-32827) is a horizontal well in Culberson County operated by Coterra Energy Operating CO., completed June 29, 2015 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit, issued February 12, 2015, permitted to 9,127 ft.
It was permitted by Cimarex Energy CO. and has since transferred to Coterra Energy Operating CO. on the wellbore schedule.
Completion filings report 9 formation tops, including Delaware, Cherry Canyon, Bone Spring, Wolfcamp.
Its lease has reported 1.17M barrels of oil and 14.6M mcf of gas since June 2015, last reporting volume in April 2026.
Operator of record
Permitted by Cimarex Energy Co.; the EWA schedule now lists a different operator.
- Based in
- Midland, TX
- P-5 status
- Active – Extension (X)
- P-5 last filed
- May 20, 2026
- Permits on file
- 184
- Phone
- (432) 571-7800
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Coterra Energy Operating Co. |
| Production reports | Coterra Energy Operating Co.through Apr 2026 |
| Latest permit | Cimarex Energy Co.Feb 12, 2015 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 9,127
- total depth, ft
- 1
- permits on file
- Feb 12, 2015
- last permit issued
- Jun 29, 2015
- completed
- 1.17M
- cumulative oil, bbl
- 14.6M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jun 2015 THROUGH Apr 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Jun 29, 2015
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: Active (A)
Surface location
No coordinates on the permit record yet. The RRC's GIS record usually lands within days of issuance; historical master-file permits never carry one.
Lease production
PDQ LEASE REPORTS · REPORTED THROUGH APR 2026
Texas reports oil by lease, not by well. These are the lease this well is completed on; this well is the only one on it.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Cavalcade 25 Unit G-10-278261 | Ford, West (Wolfcamp) | Coterra Energy Operating Co. | 1 | 1.17M | 14.6M | Jun 2015 – Apr 2026 |
Gas, mcf lease total
Last 12 months 529,052 · prior 12 774,963(-32%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Cimarex Energy Co.Jun 2015 → Oct 2025
- 2Coterra Energy Operating Co.Nov 2025 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 803659-99 | Drill | Cimarex Energy Co. | Feb 10, 2015 | Feb 12, 2015 | Apr 13, 2015 | 9,849 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Jun 29, 2015 | Cavalcade 25 Unit G-10-278261 | Ford West (Wolfcamp) | Coterra Energy Operating Co. | Producing | 9,127 |
Formation tops
As filed on W-2/G-1. Subsea from 3,190 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Delaware | 2,197 | 993 |
| Cherry Canyon | 3,222 | -32 |
| Bone SpringBONE SPRINGS | 5,792 | -2,602 |
| Wolfcamp | 8,751 | -5,561 |
| Atoka | — | — |
| DelawareFORD-DELAWARE | — | — |
| Mississippian | — | — |
| Morrow | — | — |
| Rustler | — | — |
| Strawn | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 9,039 | 19,315 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 9.625 | 2,156 | 12.25 | 1,390 S |
| 7 | 9,142 | 8.75 | 950 S |
Completion filings
W-2 and G-1 reports on record in the RRC wellbore file, newest first. The suffix identifies the wellbore or completion event. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →
| Suffix | RRC record date | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Oct 29, 2015 | Jul 21, 2015 | Yes |
Well logs
1 log loaded from the RRC's log index, the latest received Jul 31, 2017. Resistivity. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.
Open the RRC's log search for this well ↗| Logas described | Files | Intervalft, as filed | Datereceived | SizeMB |
|---|---|---|---|---|
| RESISTIVITYSpans Bone Spring, Wolfcamp | TIFF | 8,516 to 19,371 | Jul 31, 2017run May 3, 2015 | 1.00 |
"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.
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-109-32827 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-109-32827 → scanned completion filings
The logs loaded for this well are under Well logs, with the RRC's log search for it. The University Lands library has no per-well link: then paste it into its search.
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/10932827, documented in the API reference.