WELL · 42-497-30994 · DISTRICT 9
Dunaway Effie #1
Wise County · Boonsville (Bend Congl. Gas) field · Producing · Vertical
Dunaway Effie #1 (API 42-497-30994) is a well in Wise County operated by General Operating Company, completed April 17, 1978 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit, issued July 27, 1977, permitted to 7,000 ft.
It was permitted by Teal Petroleum Company and has since transferred to General Operating Company on the wellbore schedule.
No lease production has been reported under this well’s leases.
Operator of record
Permitted by Teal Petroleum Company; the EWA schedule now lists a different operator.
Wichita Falls, TX · P-5 Y, filed Feb 4, 2026 · 21 permits on file · (940) 704-5048
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | General Operating Company |
| Production reports | General Operating Companythrough Apr 2026 |
| Latest permit | Teal Petroleum CompanyJul 27, 1977 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 7,000
- total depth, ft
- 1
- permits on file
- Jul 27, 1977
- last permit issued
- Apr 17, 1978
- completed
- 0
- cumulative oil, bbl
- 280K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Apr 17, 1978
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: Active
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 |
|---|---|---|---|---|---|---|
| Dunaway, Effie G-13-76267 | Boonsville (Bend Congl., Gas) | General Operating Company | 1 | 0 | 280K | Jan 1993 – Jul 2026 |
Gas, mcf lease total
Last 12 months 3,920 · prior 12 3,950(-1%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1General Operating CompanyJan 1993 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 4072-99 | Drill | Teal Petroleum Company | Jul 27, 1977 | Jul 27, 1977 | Dec 23, 1977 | 7,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-13-76267 | — | — | — | — |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 278 | 12.25 | 210 S |
| 2.875 | 6,360 | 7.875 | 450 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 | Jan 12, 1984 | May 8, 1978 | — |
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-497-30994 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-497-30994 → 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/49730994, documented in the API reference.