WELL · 42-475-33832 · DISTRICT 8

Sealy #1

Plugged

Ward County · Ward-Estes North field  · Vertical

Sealy #1 (API 42-475-33832) is a plugged well in Ward County, plugged February 20, 2026, last operated by Lee Production CO..

The RRC has issued one drilling permit, issued October 9, 1987, permitted to 3,400 ft.

It was permitted by Sunset Energy Of Texas, Inc. and has since transferred to Lee Production CO. on the wellbore schedule.

Completion filings report one formation top, including Yates.

Its lease has reported 2.3K barrels of oil and 21.3K mcf of gas since January 1993, last reporting in July 2026. The lease carries 3 wells, so these are lease totals, not this well alone.

Operator of record

Lee Production Co.

Permitted by Sunset Energy of Texas, Inc.; the EWA schedule now lists a different operator.

Monahans, TX · P-5 Y, filed Apr 4, 2026 · 1 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleLee Production Co.
Production reportsLee Production Co.through Jun 2007
Latest permitSunset Energy of Texas, Inc.Oct 9, 1987

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

3,400
total depth, ft
1
permits on file
Oct 9, 1987
last permit issued
Jan 17, 1988
completed
2.3K
cumulative oil, bbl
21.3K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jan 17, 1988
Shut in
—
Plugged
Feb 20, 2026

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; they carry 3 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Sealy O-10-31658Ward-Estes, NorthLee Production Co.32.3K21.3KJan 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.

  1. 1Associated Operating & Explor.Jan 1993 → Sep 1993
  2. 2Viola Prod., Inc.Oct 1993 → Jul 1996
  3. 3Red Oak Energy CoApr 2000 → Feb 2002
  4. 4Lee Production Co.Sep 2002 → Jun 2007

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
337131-99DrillSunset Energy of Texas, Inc.Oct 9, 1987Oct 9, 1987—3,400

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-31658————

Formation tops

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

FormationMD ftSubsea
Yates2,522145

Perforations

Perforated and open-hole intervals.

FromToType
2,5242,737Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62550412.25300 S
4.53,4007.875300 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
00Mar 1, 1988Feb 12, 1988Yes
00Feb 25, 1988——

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) and the University Lands library. 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/47533832, documented in the API reference.