WELL · 42-285-33445 · DISTRICT 2
Evans Gas Unit #1
Lavaca County · Hallettsville (9500) field · Vertical
Evans Gas Unit #1 (API 42-285-33445) is a plugged well in Lavaca County, plugged April 2, 2009, last operated by Cox & Perkins Exploration Inc..
The RRC has issued one drilling permit (amended once), issued December 8, 2007, permitted to 10,400 ft.
Completion filings report 3 formation tops, including Frio, Yegua, Wilcox.
Operator of record
Cox & Perkins Exploration Inc.
Houston, TX · P-5 Y, filed Nov 2, 2012 · 306 permits on file · (713) 783-7880
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Cox & Perkins Exploration Inc. |
| Production reports | Cox & Perkins Exploration, Inc.through Jan 2009 |
| Latest permit | Cox & Perkins Exploration, Inc.Dec 8, 2007 |
- 10,400
- total depth, ft
- 2
- permits on file
- Dec 8, 2007
- last permit issued
- Apr 2, 2008
- completed
- 0
- cumulative oil, bbl
- 26.4K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Apr 2008 THROUGH Apr 2009
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Apr 2, 2008
- Shut in
- —
- Plugged
- Apr 2, 2009
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 |
|---|---|---|---|---|---|---|
| Evans Gas Unit G-2-240789 | Hallettsville (9500) | Cox & Perkins Exploration, Inc. | 1 | 0 | 26.4K | Apr 2008 – Apr 2009 |
No volumes reported on these leases in the last three years.
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Cox & Perkins Exploration, Inc.Apr 2008 → Jan 2009
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 650484-98 | Drill | Cox & Perkins Exploration, Inc. | May 16, 2008 | Dec 8, 2007 | Jan 19, 2008 | 9,491 |
| 650484-99 | Drill | Cox & Perkins Exploration, Inc. | Nov 30, 2007 | Dec 8, 2007 | Jan 19, 2008 | 10,400 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-2-240789 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 228 ft elevation.Download CSV →
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 9,240 | 9,250 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 9.625 | 1,749 | 12.25 | 572 S |
| 4.5 | 9,490 | 8.75 | 1,090 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 | Nov 8, 2008 | May 22, 2008 | Yes |
| 00 | Oct 21, 2008 | — | — |
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-285-33445 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-285-33445 → 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.
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/28533445, documented in the API reference.