WELL · 42-049-35754 · DISTRICT 7
Ezzell #2
Brown County · Brown County Regular field · Vertical
Ezzell #2 (API 42-049-35754) is a plugged well in Brown County, plugged September 24, 2003, last operated by Interstate Explorations LLC.
The RRC has issued one drilling permit, issued January 28, 1999, permitted to 2,000 ft.
Completion filings report one formation top, including Cross Cut Sand.
Its lease has reported 228 barrels of oil since January 2000, last reporting in March 2011. The lease carries 2 wells, so these are lease totals, not this well alone.
Operator of record
Houston, TX · P-5 Y, filed Feb 4, 2026 · 129 permits on file · (254) 442-1057
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Interstate Explorations LLC |
| Production reports | Interstate Explorations LLCthrough Mar 2000 |
| Latest permit | Interstate Explorations LLCJan 28, 1999 |
- 2,000
- total depth, ft
- 1
- permits on file
- Jan 28, 1999
- last permit issued
- Jan 20, 2000
- completed
- 228
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 2000 THROUGH Mar 2011
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Jan 20, 2000
- Shut in
- —
- Plugged
- Sep 24, 2003
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; they carry 2 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Ezzell O-8-28733 | Brown County Regular | Interstate Explorations LLC | 2 | 228 | 0 | Jan 2000 – Mar 2011 |
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.
- 1Interstate Explorations LLCJan 2000 → Mar 2000
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 482325-99 | Drill | Interstate Explorations LLC | Jan 28, 1999 | Jan 28, 1999 | Feb 5, 1999 | 2,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-8-28733 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 1,690 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Cross Cut Sand | 1,132 | 558 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 1,132 | 1,134 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 4.5 | 1,255 | 6.75 | 200 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 | Apr 10, 2000 | Feb 2, 2000 | Yes |
| 00 | Mar 7, 2000 | — | — |
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-049-35754 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-049-35754 → 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/04935754, documented in the API reference.