WELL · 42-475-34361 · DISTRICT 8

Sealy -88- #1

Plugged

Ward County · War-Wink (Cherry Canyon) field  · Vertical

Sealy -88- #1 (API 42-475-34361) is a plugged well in Ward County, plugged July 13, 2000, last operated by Prize Operating Company.

The RRC has issued one drilling permit, issued April 9, 1996, permitted to 7,900 ft.

It was permitted by IP Petroleum Company, Inc. and has since transferred to Prize Operating Company on the wellbore schedule.

Completion filings report 4 formation tops, including Delaware, Cherry Canyon, Base Manzanita, Brushy Canyon.

Its lease has reported 499 barrels of oil since May 1997, last reporting in August 2000.

Operator of record

Prize Operating Company

Permitted by IP Petroleum Company, Inc.; the EWA schedule now lists a different operator.

Grapevine, TX · P-5 Y, filed Mar 1, 2002 · 129 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePrize Operating Company
Production reportsIP Petroleum Company, Inc.through Jul 1997
Latest permitIP Petroleum Company, Inc.Apr 9, 1996

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

7,900
total depth, ft
1
permits on file
Apr 9, 1996
last permit issued
Jun 23, 1997
completed
499
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · May 1997 THROUGH Aug 2000

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jun 23, 1997
Shut in
—
Plugged
Jul 13, 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 -88- O-10-35463War-Wink (Cherry Canyon)Prize Operating Company14990May 1997 – Aug 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. 1IP Petroleum Company, Inc.May 1997 → Jul 1997

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
446598-99DrillIP Petroleum Company, Inc.Apr 3, 1996Apr 9, 1996Jul 18, 19967,900

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-35463————

Formation tops

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

FormationMD ftSubsea
Delaware5,032-2,349
Cherry Canyon5,649-2,966
Base Manzanita5,982-3,299
Cherry CanyonLOWER CHERRY CANYON6,612-3,929
Brushy Canyon6,844-4,161

Perforations

Perforated and open-hole intervals.

FromToType
6,3586,382Perforated
6,7906,823Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6252,82812.251,550 S
5.57,7857.875675 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
00Oct 2, 1997Aug 25, 1997Yes
00Sep 29, 1997——

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