TEXAS · WELLS · KARNES COUNTY · API 42-255-36702 · DISTRICT 02
Dickson-Allen Unit #25H
Karnes County · Sugarkane (Austin Chalk) field · Horizontal
Dickson-Allen Unit #25H (API 42-255-36702) is a plugged horizontal well in Karnes County, plugged February 24, 2020, last operated by Encana Oil & Gas(USA) Inc..
The RRC has issued one drilling permit, issued November 21, 2019, permitted to 12,000 ft.
It was permitted by Encana Oil & Gas(USA) Inc. and has since transferred to Encana Oil & Gas(USA) Inc. on the wellbore schedule.
Operator of record
Encana Oil & Gas(usa) Inc.
Permitted by Encana Oil & Gas(usa) Inc.; 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 | Encana Oil & Gas(usa) Inc.Nov 21, 2019 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 12,000
- total depth, ft
- 1
- permits on file
- Nov 21, 2019
- 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
- Feb 24, 2020
Surface location
28.892131, -98.067247 NAD27, as filed
28.892385, -98.067530 WGS84
Permit surface location from the RRC GIS record, referenced to NAD27 as the RRC files it; the WGS84 pair is the same point through NOAA's NADCON grid, and the map link uses it, in Karnes County.
Wells nearby
Every well with a location on file around this well, in any state, nearest first.
Texas locations come from drilling permits, so most older Texas wells have none and are not listed.
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 |
|---|---|---|---|---|---|---|
| 859125-99 | Drill | Encana Oil & Gas(usa) Inc. | Nov 14, 2019 | Nov 21, 2019 | Dec 10, 2019 | 12,000 |
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-255-36702 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-255-36702 → scanned completion filings
Log images filed since 2004 open from the RRC's log search for this well; none are loaded here for it.
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 neighbors can.
Section of the neighbors →Dickson-Allen Unit42-255-36701
0.0 KM · Encana Oil & Gas(usa) Inc. · Section with this well →
| Yegua | 1,052 | -666 |
| Queen City | 3,033 | -2,647 |
| Reklaw | 3,418 | -3,032 |
| Carrizo | 3,971 | -3,585 |
| Wilcox | 5,684 | -5,298 |
| Austin Chalk | 10,415 | -10,029 |
| Eagle Ford | — | |
| Sligo | — |
10 TOPS · FIRST 8
Dickson-Allen Unit42-255-36797
0.0 KM · Encana Oil & Gas(usa) Inc. · Section with this well →
| Yegua | 1,082 | -696 |
| Queen City | 3,063 | -2,677 |
| Reklaw | 3,448 | -3,062 |
| Carrizo | 4,001 | -3,615 |
| Wilcox | 5,714 | -5,328 |
| Austin Chalk | 10,460 | -10,074 |
| Frio | — | |
| Sligo | — |
10 TOPS · FIRST 8
Dickson-Allen Unit42-255-36705
0.5 KM · Encana Oil & Gas(usa) Inc. · Section with this well →
| Yegua | 1,082 | -694 |
| Queen City | 3,063 | -2,675 |
| Reklaw | 3,448 | -3,060 |
| Carrizo | 4,001 | -3,613 |
| Wilcox | 5,714 | -5,326 |
| Austin Chalk | 10,526 | -10,138 |
| Edwards | — | |
| Frio | — |
10 TOPS · FIRST 8
Dickson-Allen Unit42-255-36704
0.5 KM · Encana Oil & Gas(usa) Inc. · Section with this well →
| Yegua | 1,083 | -694 |
| Queen City | 3,064 | -2,675 |
| Reklaw | 3,449 | -3,060 |
| Carrizo | 4,002 | -3,613 |
| Wilcox | 5,715 | -5,326 |
| Austin Chalk | 10,555 | -10,166 |
| Edwards | — | |
| Eagle Ford | — |
10 TOPS · FIRST 8
Dickson-Allen Unit42-255-36703
0.5 KM · Ovintiv USA Inc. · Section with this well →
| Yegua | 1,083 | -694 |
| Queen City | 3,064 | -2,675 |
| Reklaw | 3,449 | -3,060 |
| Carrizo | 3,974 | -3,585 |
| Wilcox | 5,715 | -5,326 |
| Austin Chalk | 10,574 | -10,185 |
| Eagle Ford | 10,714 | -10,325 |
| Edwards | — |
10 TOPS · FIRST 8
Blaze Unit42-255-35869
0.7 KM · EOG Resources, Inc. · Section with this well →
| Yegua | 1,015 | -614 |
| Queen City | 2,675 | -2,274 |
| Reklaw | 3,279 | -2,878 |
| Carrizo | 3,450 | -3,049 |
| Wilcox | 3,758 | -3,357 |
| Eagle Ford | 10,841 | -10,440 |
| Austin Chalk | — | |
| Sligo | — |
10 TOPS · FIRST 8
Patsy-Clark Unit42-255-37346
2.1 KM · Validus NRG Aquilas Assetco LLC · Section with this well →
| Yegua | 1,050 | -666 |
| Queen City | 3,099 | -2,715 |
| Reklaw | 3,369 | -2,985 |
| Carrizo | 3,981 | -3,597 |
| Wilcox | 4,278 | -3,894 |
| Austin Chalk | 10,512 | -10,128 |
| Edwards | — | |
| Eagle Ford | — |
10 TOPS · FIRST 8
Franklin Unit42-255-37347
2.1 KM · Validus NRG Aquilas Assetco LLC · Section with this well →
| Yegua | 1,088 | -704 |
| Queen City | 3,122 | -2,738 |
| Reklaw | 3,406 | -3,022 |
| Carrizo | 4,008 | -3,624 |
| Wilcox | 4,307 | -3,923 |
| Austin Chalk | 10,448 | -10,064 |
| Frio | — | |
| Edwards | — |
10 TOPS · FIRST 8
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/25536702, documented in the API reference.