WELL · 42-485-39652 · DISTRICT 9
Bailey Osa F. #8A
Wichita County · Wichita County Regular field · Vertical
Bailey Osa F. #8A (API 42-485-39652) is a plugged well in Wichita County, plugged July 20, 2000, last operated by Vanwinkle R. L..
The RRC has issued one drilling permit, issued November 22, 1983, permitted to 1,350 ft.
It was permitted by Tillman, Jack Equipment CO. and has since transferred to Vanwinkle R. L. on the wellbore schedule.
Completion filings report 2 formation tops, including Cisco, Thomas Sand.
Operator of record
Permitted by Tillman, Jack Equipment Co.; the EWA schedule now lists a different operator.
Wichita Falls, TX · P-5 Y, filed May 6, 2011 · 3 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Vanwinkle R. L. |
| Production reports | none |
| Latest permit | Tillman, Jack Equipment Co.Nov 22, 1983 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 1,350
- total depth, ft
- 1
- permits on file
- Nov 22, 1983
- last permit issued
- Feb 15, 1984
- completed
- 0
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Aug 2003
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Feb 15, 1984
- Shut in
- —
- Plugged
- Jul 20, 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 7 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Bailey, Osa F. O-13-5621 | Wichita County Regular | Vanwinkle, R. L. | 7 | 0 | 0 | Jan 1993 – Aug 2003 |
No volumes reported on these leases in the last three years.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 221499-99 | Drill | Tillman, Jack Equipment Co. | Nov 16, 1983 | Nov 22, 1983 | — | 1,350 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-13-5621 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Download CSV →
| Formation | MD ft |
|---|---|
| CiscoCISCO SAND | 375 |
| CiscoCISCO SAND | 575 |
| Thomas SandTHOMAS | 1,322 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 1,320 | 1,330 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 5.5 | 1,341 | 7.875 | 170 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 | Apr 9, 1984 | Mar 23, 1984 | — |
| 00 | Mar 30, 1984 | Mar 23, 1984 | — |
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-485-39652 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-485-39652 → 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/48539652, documented in the API reference.