WELL · 42-399-33584 · DISTRICT 7
Busenlehner #2
Runnels County · Jim Burt E. (Gardner) field · Vertical
Busenlehner #2 (API 42-399-33584) is a plugged well in Runnels County, plugged January 26, 2000, last operated by Leclair Operating CO. Inc..
The RRC has issued one drilling permit, issued August 20, 1985, permitted to 4,027 ft.
Completion filings report 3 formation tops, including Palo Pinto, Capps, Gardner.
Its lease has reported 7.15K barrels of oil and 68.2K mcf of gas since January 1993, last reporting in April 2000. The lease carries 2 wells, so these are lease totals, not this well alone.
Operator of record
- Based in
- Abilene, TX
- P-5 status
- Inactive (I)
- P-5 last filed
- Jun 5, 2013
- Permits on file
- 351
- Phone
- (325) 698-5100
SOURCE · RRC EWA WELLBORE SCHEDULE
- 4,027
- total depth, ft
- 1
- permits on file
- Aug 20, 1985
- last permit issued
- Sep 9, 1985
- completed
- 7.15K
- cumulative oil, bbl
- 68.2K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Apr 2000
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Sep 9, 1985
- Shut in
- —
- Plugged
- Jan 26, 2000
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 2 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Busenlehner O-9-11551 | Jim Burt, E. (Gardner) | Leclair Operating Co., Inc. | 2 | 7.15K | 68.2K | Jan 1993 – Apr 2000 |
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.
- 1Leclair Operating Co., Inc.Jan 1993 → Nov 1999
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 282928-99 | Drill | Leclair Operating Co., Inc. | Sep 16, 1985 | Aug 20, 1985 | — | 4,027 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-9-11551 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 1,725 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Palo Pinto | 3,280 | -1,555 |
| Capps | 3,540 | -1,815 |
| Gardner | 4,020 | -2,295 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 4,020 | 4,026 | Open hole |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 168 | 12.25 | 105 S |
| 5.5 | 4,004 | 7.875 | 425 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 | Sep 16, 1985 | Yes |
| 00 | Oct 1, 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-399-33584 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-399-33584 → 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/39933584, documented in the API reference.