WELL · 42-133-33589 · DISTRICT 7
Dyer 464 #2
Eastland County · Lee Ray (Lake) field · Vertical
Dyer 464 #2 (API 42-133-33589) is a plugged well in Eastland County, plugged May 30, 2007, last operated by Jones CO..
The RRC has issued 2 drilling permits between 1981 and 1985, permitted to 4,500 ft.
Completion filings report 3 formation tops, including Caddo, Marble Falls, Bond Sd.
Operator of record
- Based in
- Albany, TX
- P-5 status
- Inactive (I)
- P-5 last filed
- Apr 26, 1990
- Permits on file
- 779
- Phone
- (325) 762-3353
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Jones Co. |
| Production reports | Van Operating, Ltd.through Sep 2003 |
| Latest permit | Jones Co.Feb 8, 1985 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 4,500
- total depth, ft
- 2
- permits on file
- Feb 8, 1985
- last permit issued
- Jan 21, 1982
- completed
- 0
- cumulative oil, bbl
- 60.9K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH May 2007
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Jan 21, 1982
- Shut in
- —
- Plugged
- May 30, 2007
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 |
|---|---|---|---|---|---|---|
| Dyer "464" G-8-115327 | Lee Ray (Conglomerate) | Van Operating, Ltd. | 1 | 0 | 60.9K | Jan 1993 – May 2007 |
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.
- 1Jones Company, Ltd.Apr 1993 → Jul 1995
- 2Van Operating, Ltd.Aug 1995 → Sep 2003
Permits
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-8-115327 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 1,533 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Caddo | 3,428 | -1,895 |
| Marble Falls | 3,530 | -1,997 |
| Bond SD | 3,608 | -2,075 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 3,530 | 3,538 | Perforated |
| 3,611 | 3,632 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 102 | 12.25 | 80 S |
| 2.375 | 3,500 | — | — |
| 4.5 | 4,089 | 7.875 | 170 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 | Mar 21, 1985 | Jan 31, 1985 | — |
| 00 | Mar 20, 1985 | Jan 21, 1985 | — |
| 00 | Jan 12, 1984 | Feb 5, 1982 | — |
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-133-33589 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-133-33589 → 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/13333589, documented in the API reference.