WELL · 42-353-32888 · DISTRICT 7

Sneed #1

Y

Nolan County · Hat Top Mountain N. (Fry Sd.) field · Producing  · Vertical

Sneed #1 (API 42-353-32888) is a well in Nolan County operated by Lone Star Operations LLC, completed March 3, 2006 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued November 16, 2005, permitted to 5,600 ft.

It was permitted by Spiller Operating CO., Inc. and has since transferred to Lone Star Operations LLC on the wellbore schedule.

Completion filings report one formation top, including Fry Sand.

Its lease has reported 69K barrels of oil and 69.7K mcf of gas since February 2006, last reporting in July 2026.

Operator of record

Lone Star Operations LLC

Permitted by Spiller Operating Co., Inc.; the EWA schedule now lists a different operator.

Sweetwater, TX · P-5 Y, filed Jul 4, 2026 · (806) 801-2072

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleLone Star Operations LLC
Production reportsLone Star Operations LLCthrough Mar 2026
Latest permitSpiller Operating Co., Inc.Nov 16, 2005

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

5,600
total depth, ft
1
permits on file
Nov 16, 2005
last permit issued
Mar 3, 2006
completed
69K
cumulative oil, bbl
69.7K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 2006 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Mar 3, 2006
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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
Sneed O-8-29691Hat Top Mountain, N. (Fry Sd.)Lone Star Operations LLC169K69.7KFeb 2006 – Jul 2026

Oil, barrels lease total

Last 12 months 126 · prior 12 468(-73%)

050100150202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Spiller Operating Co., Inc.Mar 2006 → Jul 2006
  2. 2Cholla Petroleum, Inc.Aug 2006 → May 2024
  3. 3Lone Star Operations LLCJun 2024 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
609636-99DrillSpiller Operating Co., Inc.Nov 16, 2005Nov 16, 2005Dec 24, 20055,600

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-8-29691————

Formation tops

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

FormationMD ftSubsea
Fry Sand5,055-2,804

Perforations

Perforated and open-hole intervals.

FromToType
5,0555,065Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62541912.25250 S
5.55,3807.875600 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
00Aug 7, 2006Mar 10, 2006Yes
00Mar 30, 2006——

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