WELL · 42-109-32326 · DISTRICT 8
Delaware State 61-T1-12 #1H
Culberson County · Wildcat field · Horizontal
Delaware State 61-T1-12 #1H (API 42-109-32326) is a plugged horizontal well in Culberson County, plugged March 7, 2013, last operated by Encana Oil & Gas(USA) Inc..
The RRC has issued one drilling permit, issued April 19, 2010, permitted to 11,000 ft.
Completion filings report 3 formation tops, including Brushy Canyon, Bone Spring, Lower Bspg Shale.
Operator of record
- Based in
- Denver, CO
- P-5 status
- Inactive (I)
- P-5 last filed
- Dec 19, 2019
- Permits on file
- 3,078
- Phone
- (303) 623-2300
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Encana Oil & Gas(usa) Inc. |
| Production reports | none |
| Latest permit | Encana Oil & Gas(usa) Inc.Apr 19, 2010 |
- 11,000
- total depth, ft
- 1
- permits on file
- Apr 19, 2010
- last permit issued
- Jun 22, 2010
- completed
- 0
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Aug 2011 THROUGH Mar 2013
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Jun 22, 2010
- Shut in
- —
- Plugged
- Mar 7, 2013
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 |
|---|---|---|---|---|---|---|
| Delaware State 61-T1-12 G-10-269487 | Wildcat | Encana Oil & Gas(usa) Inc. | 1 | 0 | 0 | Aug 2011 – Mar 2013 |
No volumes reported on these leases in the last three years.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 694527-99 | Drill | Encana Oil & Gas(usa) Inc. | Apr 15, 2010 | Apr 19, 2010 | May 11, 2010 | 11,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-10-269487 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 3,575 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Brushy Canyon | 4,026 | -451 |
| Bone SpringBONE SPRINGS LIMESTONE | 4,973 | -1,398 |
| Lower Bspg Shale | 5,539 | -1,964 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 9,980 | 9,983 | Perforated |
| 10,030 | 10,033 | Perforated |
| 10,080 | 10,083 | Perforated |
| 10,130 | 10,133 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 9.625 | 285 | 12.75 | 170 S |
| 5.5 | 1,030 | 8.75 | 1,400 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. About these reports →
| Suffix | Filed | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Aug 29, 2013 | Dec 20, 2012 | Yes |
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-32326 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-109-32326 → scanned completion filings
Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward) and the University Lands library. then paste it into their 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/10932326, documented in the API reference.