WELL · 42-417-35815 · DISTRICT 7
Spencer #1
Shackelford County · Shackelford County Regular field · Vertical
Spencer #1 (API 42-417-35815) is a plugged well in Shackelford County, plugged August 24, 2009, last operated by F & S Production.
The RRC has issued one drilling permit, issued May 25, 1984, permitted to 1,600 ft.
It was permitted by Parrott, L. S. and has since transferred to F & S Production on the wellbore schedule.
Completion filings report one formation top, including Tannehill.
Its lease has reported 290 barrels of oil and 9 mcf of gas since January 1993, last reporting in July 2026.
Operator of record
Permitted by Parrott, L. S.; the EWA schedule now lists a different operator.
Albany, TX · P-5 Y, filed May 2, 2014 · 2 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | F & S Production |
| Production reports | F & S Productionthrough Jul 2001 |
| Latest permit | Parrott, L. S.May 25, 1984 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 1,600
- total depth, ft
- 1
- permits on file
- May 25, 1984
- last permit issued
- Jul 14, 1984
- completed
- 290
- cumulative oil, bbl
- 9
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Jul 14, 1984
- Shut in
- —
- Plugged
- Aug 24, 2009
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 |
|---|---|---|---|---|---|---|
| Spencer O-8-22690 | Shackelford County Regular | F & S Production | 1 | 290 | 9 | 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.
- 1F & S ProductionNov 1993 → Jul 2001
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 240236-99 | Drill | Parrott, L. S. | May 24, 1984 | May 25, 1984 | — | 1,600 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-8-22690 | — | — | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 1,139 | 1,216 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 4.5 | 1,325 | 6.25 | 260 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 31, 1985 | Jul 5, 1985 | — |
| 00 | Jul 18, 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-417-35815 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-417-35815 → 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/41735815, documented in the API reference.