WELL · 42-253-34180 · DISTRICT 7

McSpadden A #1

Plugged

Jones County · I Believe Kelsey (Palo Pinto) field  · Vertical

Mcspadden A #1 (API 42-253-34180) is a plugged well in Jones County, plugged September 11, 2013, last operated by Snyder Drilling Corp..

The RRC has issued one drilling permit (amended once), issued September 13, 1994, permitted to 4,300 ft.

It was permitted by Clear Fork, Incorporated and has since transferred to Snyder Drilling Corp. on the wellbore schedule.

Completion filings report 4 formation tops, including B/Coleman Junction, Cisco, Gunsight, King Sand.

Its lease has reported 231 barrels of oil since October 1994, last reporting in February 2014.

Operator of record

Snyder Drilling Corp.

Permitted by Clear Fork, Incorporated; the EWA schedule now lists a different operator.

Albany, TX · P-5 Y, filed Jul 4, 2026 · 183 permits on file · (325) 762-4217

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSnyder Drilling Corp.
Production reportsClear Fork, Incorporatedthrough Jan 1995
Latest permitClear Fork, IncorporatedSep 13, 1994

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

4,300
total depth, ft
2
permits on file
Sep 13, 1994
last permit issued
Oct 17, 1994
completed
231
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Oct 1994 THROUGH Feb 2014

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Oct 17, 1994
Shut in
—
Plugged
Sep 11, 2013

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 →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
McSpadden "A" O-8-27356I Believe, Kelsey (Palo Pinto)Snyder Drilling Corp.12310Oct 1994 – Feb 2014

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.

  1. 1Clear Fork, IncorporatedOct 1994 → Jan 1995

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
427923-98DrillClear Fork, IncorporatedNov 18, 1994Sep 13, 1994Sep 23, 19944,000
427923-99DrillClear Fork, IncorporatedSep 12, 1994Sep 13, 1994—4,300

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-8-27356————

Formation tops

As filed on W-2/G-1. Subsea from 1,721 ft elevation.Download CSV →

FormationMD ftSubsea
B/Coleman Junction1,744-23
CiscoCISCO REED1,767-46
GunsightGUNSIGHT LIME2,704-983
King Sand2,780-1,059

Perforations

Perforated and open-hole intervals.

FromToType
3,9343,945Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62513312.25100 S
4.53,9737.875760 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 →

SuffixFiledW-2 / G-1 dateLogs referenced
00Dec 15, 1994Nov 15, 1994Yes
00Dec 9, 1994——

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.

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/25334180, documented in the API reference.