WELL · 42-029-35586 · DISTRICT 1
Wondra, Melvin #1
Bexar County · Vertical
Wondra, Melvin #1 (API 42-029-35586) is a permitted well in Bexar County filed by Mcguire, Joe Inc.; no completion report is on file yet.
The RRC has issued 2 drilling permits in 1984, permitted to 1,300 ft.
Completion filings report one formation top, including Anacacho.
Its lease has reported 169 barrels of oil and 19 mcf of gas since January 1993, last reporting in July 2026. The lease carries 4 wells, so these are lease totals, not this well alone.
Operator of record
Keensburg, IL · P-5 Y, filed Apr 8, 2011 · 36 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | Ginco Operating Co.through Oct 1995 |
| Latest permit | McGuire, Joe Inc.Oct 1, 1984 |
- 1,300
- total depth, ft
- 2
- permits on file
- Oct 1, 1984
- last permit issued
- —
- completed
- 169
- cumulative oil, bbl
- 19
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- —
- Shut in
- —
- Plugged
- —
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 4 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Wondra, Melvin O-1-10584 | Fairfield | Great Plains Resources, Inc. | 4 | 169 | 19 | Jan 1993 – Jul 2026 |
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.
- 1Genie Oil CompanyJan 1993 → Jan 1995
- 2Ginco Operating Co.Aug 1995 → Oct 1995
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 253068-99 | Drill | McGuire, Joe Inc. | Sep 28, 1984 | Oct 1, 1984 | — | 1,300 |
| 244900-99 | Drill | Hereford, J. A. Industries, Inc. | Jul 11, 1984 | Jul 11, 1984 | — | 1,300 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-1-10584 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 723 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Anacacho | 1,146 | -423 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 1,146 | 1,186 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 4.5 | 1,216 | 6.75 | 63 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 | Oct 8, 1985 | Aug 13, 1985 | — |
| 00 | Oct 3, 1985 | — | — |
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-029-35586 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-029-35586 → 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/02935586, documented in the API reference.