WELL · 42-395-30462 · DISTRICT 5
Eylau #1
Robertson County · Wildcat field · Directional
Eylau #1 (API 42-395-30462) is a plugged well in Robertson County, plugged April 19, 1999, last operated by Broughton Operating Corp..
The RRC has issued one drilling permit (amended once), issued May 7, 1996, permitted to 17,000 ft.
It was permitted by Zackson Resources, Inc. and has since transferred to Broughton Operating Corp. on the wellbore schedule.
Completion filings report one formation top, including Cotton Valley.
Operator of record
Permitted by Zackson Resources, Inc.; the EWA schedule now lists a different operator.
Pittsburgh, PA · P-5 Y, filed Mar 1, 2002 · 12 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Broughton Operating Corp. |
| Production reports | none |
| Latest permit | Zackson Resources, Inc.May 7, 1996 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 17,000
- total depth, ft
- 2
- permits on file
- May 7, 1996
- last permit issued
- —
- completed
- 0
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Oct 1996 THROUGH May 1999
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- —
- Shut in
- —
- Plugged
- Apr 19, 1999
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 |
|---|---|---|---|---|---|---|
| Eylau O-5-3571 | Wildcat | Broughton Operating Corp. | 1 | 0 | 0 | Oct 1996 – May 1999 |
No volumes reported on these leases in the last three years.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 447888-98 | Drill | Zackson Resources, Inc. | Jun 11, 1996 | May 7, 1996 | May 13, 1996 | 17,000 |
| 447888-99 | Drill | Zackson Resources, Inc. | May 7, 1996 | May 7, 1996 | — | 17,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-5-3571 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 529 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Cotton ValleyCOTTON VALLEY LIME | 14,126 | -13,597 |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 16 | 109 | — | — |
| 10.75 | 5,732 | 14.75 | 3,862 S |
| 7.625 | 13,646 | 9.875 | 1,300 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 | Jul 8, 2008 | Oct 21, 1996 | Yes |
| 00 | Oct 22, 1997 | — | — |
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-395-30462 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-395-30462 → 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/39530462, documented in the API reference.