WELL · 42-497-33090 · DISTRICT 9
Busey G. U. #3
Wise County · Vertical
Busey G. U. #3 (API 42-497-33090) is a permitted well in Wise County filed by Waggoner-Baldridge Energy CO.; no completion report is on file yet.
The RRC has issued 2 drilling permits between 1985 and 1986, permitted to 6,800 ft.
Completion filings report 3 formation tops, including Caddo, Atoka, Big Saline.
Operator of record
Dallas, TX · P-5 Y, filed Oct 9, 1991 · 30 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | Waggoner-Baldridge Oper. Co, Incthrough Jan 1996 |
| Latest permit | Waggoner-Baldridge Energy Co.May 12, 1986 |
- 6,800
- total depth, ft
- 2
- permits on file
- May 12, 1986
- last permit issued
- —
- completed
- 0
- cumulative oil, bbl
- 30.9K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jun 1996
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; this well is the only one on it.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Busey Gas Unit G-13-121504 | Boonsville (Bend Congl., Gas) | Republic Energy Inc. | 1 | 0 | 30.9K | Jan 1993 – Jun 1996 |
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.
- 1Waggoner-Baldridge Oper. Co, IncJan 1993 → Jan 1996
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 302877-99 | Drill | Waggoner-Baldridge Energy Co. | Mar 25, 1986 | May 12, 1986 | — | 6,800 |
| 285138-99 | Drill | Waggoner-Baldridge Energy Co. | Sep 18, 1985 | Sep 18, 1985 | — | 6,800 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-13-121504 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 807 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Caddo | 4,913 | -4,106 |
| Atoka | 5,342 | -4,535 |
| Big Saline | 5,478 | -4,671 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 5,553 | 5,558 | Perforated |
| 5,596 | 5,604 | Perforated |
| 5,936 | 5,942 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 325 | 12.25 | 225 S |
| 4.5 | 6,065 | 7.875 | 325 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 9, 1986 | Jun 9, 1986 | Yes |
| 00 | Jul 2, 1986 | — | — |
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-33090 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-497-33090 → 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/49733090, documented in the API reference.