WELL · 42-497-80968 · DISTRICT 9
Spain Mosley #1
Wise County · Alvord South (Atoka) field · Vertical
Spain Mosley #1 (API 42-497-80968) is a plugged well in Wise County, plugged April 9, 2010, last operated by Aruba Petroleum Inc..
The RRC has issued one drilling permit, issued January 20, 1982, permitted to 6,200 ft.
It was permitted by Waymar Oil & Gas Company and has since transferred to Aruba Petroleum Inc. on the wellbore schedule.
Operator of record
Permitted by Waymar Oil & Gas Company; the EWA schedule now lists a different operator.
Dallas, TX · P-5 Y, filed Jul 8, 2022 · 427 permits on file · (940) 390-5604
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Aruba Petroleum Inc. |
| Production reports | Aruba Petroleum, Inc.through Feb 2008 |
| Latest permit | Waymar Oil & Gas CompanyJan 20, 1982 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 6,200
- total depth, ft
- 1
- permits on file
- Jan 20, 1982
- last permit issued
- Aug 25, 1983
- completed
- 0
- cumulative oil, bbl
- 74.5K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jun 2010
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Aug 25, 1983
- Shut in
- —
- Plugged
- Apr 9, 2010
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 |
|---|---|---|---|---|---|---|
| Spain, Mosley G-13-107169 | Alvord, South (Atoka) | Aruba Petroleum, Inc. | 1 | 0 | 74.5K | Jan 1993 – Jun 2010 |
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.
- 1Waymar Oil & Gas CompanyJan 1993 → Dec 2006
- 2Aruba Petroleum, Inc.Jan 2007 → Feb 2008
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 149169-99 | Other | Waymar Oil & Gas Company | Jan 20, 1982 | Jan 20, 1982 | — | 6,200 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-13-107169 | — | — | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 5,812 | 5,824 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 621 | 12.25 | 400 S |
| 2.375 | 5,800 | — | — |
| 4.5 | 6,007 | 7.5 | 150 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 | Sep 15, 1983 | — |
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-80968 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-497-80968 → 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/49780968, documented in the API reference.