TEXAS · WELLS · WINKLER COUNTY · SEALY & SMITH 10 LEASE · API 42-495-31029 · DISTRICT 7B

Sealy & Smith 10 #1

Plugged

Winkler County · Arenoso (Strawn Detritus) field  · Vertical

Sealy & Smith 10 #1 (API 42-495-31029) is a plugged well in Winkler County, plugged March 31, 2000, last operated by Sage Energy Company.

The RRC has issued one drilling permit, issued January 10, 1979, permitted to 9,000 ft.

It was permitted by Rial Oil CO. and has since transferred to Sage Energy Company on the wellbore schedule.

Its lease has reported 7.6K barrels of oil and 46.5K mcf of gas since January 1993, with no volume in the three years through April 2026.

Operator of record

Sage Energy Company

Permitted by Rial Oil Co.; the EWA schedule now lists a different operator.

Based in
San Antonio, TX
P-5 status
Active (A)
P-5 last filed
Oct 10, 2025
Permits on file
1,060
Phone
(210) 404-2828

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSage Energy Company
Production reportsSage Energy Companythrough Mar 2000
Latest permitRial Oil Co.Jan 10, 1979

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

9,000
total depth, ft
1
permits on file
Jan 10, 1979
last permit issued
Feb 25, 1979
completed
7.6K
cumulative oil, bbl
46.5K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Mar 2000

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Feb 25, 1979
Shut in
—
Plugged
Mar 31, 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; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Sealy & Smith 10 O-10-25328Arenoso (Strawn Detritus)Sage Energy Company17.6K46.5KJan 1993 – Mar 2000

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. 1Sage Energy CompanyJan 1993 → Feb 2000

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
40573-99DrillRial Oil Co.Jan 10, 1979Jan 10, 1979—9,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Feb 25, 1979Sealy & Smith 10 O-10-25328Arenoso (Strawn Detritus)Sage Energy CompanyPlugged—

Perforations

Perforated and open-hole intervals.

FromToType
8,5318,537Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62594512.25400 S
2.3758,513——
4.58,9147.875350 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Jan 12, 1984Mar 2, 1979—

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 filed since 2004 open from the RRC's log search for this well; none are loaded here for it. The University Lands library has no per-well link: then paste it into its search.

Find logs withinmiles of this well:List →Map →

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