WELL · 42-291-31983 · DISTRICT 3
Quinn B. E. #1
Liberty County · Pelican East (Wilcox 8900) field · Vertical
Quinn B. E. #1 (API 42-291-31983) is a plugged well in Liberty County, plugged January 13, 2017, last operated by D.C. Energy.
The RRC has issued one drilling permit, issued May 5, 1986, permitted to 8,950 ft.
It was permitted by Famcor Oil, Inc and has since transferred to D.C. Energy on the wellbore schedule.
Completion filings report 2 formation tops, including Wilcox, Top Kirby Sand.
Operator of record
Permitted by Famcor Oil, Inc; the EWA schedule now lists a different operator.
Hallettsville, TX · P-5 Y, filed Aug 4, 2025
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | D.C. Energy |
| Production reports | none |
| Latest permit | Famcor Oil, IncMay 5, 1986 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 8,950
- total depth, ft
- 1
- permits on file
- May 5, 1986
- last permit issued
- Jun 10, 1986
- completed
- 0
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jan 2017
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Jun 10, 1986
- Shut in
- —
- Plugged
- Jan 13, 2017
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 |
|---|---|---|---|---|---|---|
| Quinn, B. E. G-3-122378 | Pelican, East (Wilcox 8900) | D.C. Energy | 1 | 0 | 0 | Jan 1993 – Jan 2017 |
No volumes reported on these leases in the last three years.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 301805-99 | Drill | Famcor Oil, Inc | May 1, 1986 | May 5, 1986 | Aug 17, 1986 | 8,950 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-3-122378 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 154 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| WilcoxTOP WILCOX | 8,825 | -8,671 |
| Top Kirby Sand | 8,904 | -8,750 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 8,898 | 8,914 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 14 | 99 | — | — |
| 8.625 | 1,973 | 12.25 | 845 S |
| 4.5 | 8,898 | 7.875 | 250 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 14, 1986 | Jul 17, 1986 | Yes |
| 00 | Nov 1, 1986 | — | Yes |
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-291-31983 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-291-31983 → 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/29131983, documented in the API reference.