WELL · 42-475-34505 · DISTRICT 8

Sealy 87 #1

Plugged

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

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

The RRC has issued one drilling permit, issued August 7, 1997, permitted to 7,800 ft.

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

Completion filings report 5 formation tops, including Delaware, Cherry Canyon, Base Manzanita, Lwr. Cherry Canyon.

Its lease has reported 602 barrels of oil and 125 mcf of gas since November 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 Dec 1997
Latest permitIP Petroleum Company, Inc.Aug 7, 1997

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

7,800
total depth, ft
1
permits on file
Aug 7, 1997
last permit issued
Nov 12, 1997
completed
602
cumulative oil, bbl
125
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Nov 1997 THROUGH Aug 2000

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Nov 12, 1997
Shut in
—
Plugged
Jul 7, 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 87 O-10-35586War-Wink (Brushy Canyon)Prize Operating Company1602125Nov 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.Nov 1997 → Dec 1997

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
465789-99DrillIP Petroleum Company, Inc.Aug 4, 1997Aug 7, 1997Sep 3, 19977,800

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-35586————

Formation tops

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

FormationMD ftSubsea
Delaware4,777-2,095
Cherry Canyon5,582-2,900
Base Manzanita5,906-3,224
Lwr. Cherry Canyon6,527-3,845
Brushy Canyon6,826-4,144

Perforations

Perforated and open-hole intervals.

FromToType
6,9126,940Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6252,80012.251,350 S
74,42511300 S
4.57,7756.125260 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
00Feb 2, 1998Dec 19, 1997Yes
00Jan 20, 1998——

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