WELL · 42-475-37456 · DISTRICT 8

Sealy Ranch #7203H

N

Ward County  · Horizontal

Sealy Ranch #7203H (API 42-475-37456) is a permitted horizontal well in Ward County filed by Halcon Operating CO., Inc.; no completion report is on file yet.

The RRC has issued 2 drilling permits (amended twice) between 2018 and 2023, permitted to 13,000 ft.

Completion filings report 10 formation tops, including Rustler, Yates, Capitan, Delaware.

Its lease has reported 6.33M barrels of oil and 17.5M mcf of gas since May 2017, last reporting in July 2026. The lease carries 41 wells, so these are lease totals, not this well alone.

Operator of record

Halcon Operating Co., Inc.

Houston, TX · P-5 Y, filed Feb 4, 2026 · 573 permits on file · (713) 345-1060

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsHalcon Operating Co., Inc.through Mar 2026
Latest permitHalcon Operating Co., Inc.Aug 21, 2023
13,000
total depth, ft
4
permits on file
Aug 21, 2023
last permit issued
—
completed
6.33M
cumulative oil, bbl
17.5M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · May 2017 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
—

Surface location

31.650364, -103.132778

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Ward County.

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 41 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Sealy Ranch O-10-50245Phantom (Wolfcamp)Halcon Operating Co., Inc.416.33M17.5MMay 2017 – Jul 2026

Oil, barrels lease total

Last 12 months 1,044,026 · prior 12 998,091(+5%)

050K100K150K202420252026

Gas, mcf lease total

Last 12 months 4,497,234 · prior 12 3,002,898(+50%)

0200K400K600K202420252026

Chain of custody

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

  1. 1Halcon Operating Co., Inc.Dec 2017 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
892774-97DrillHalcon Operating Co., Inc.Jul 3, 2025Aug 21, 2023Feb 8, 202513,000
892774-98DrillHalcon Operating Co., Inc.Dec 3, 2024Aug 21, 2023Feb 8, 202513,000
892774-99DrillHalcon Operating Co., Inc.Aug 9, 2023Aug 21, 2023Feb 8, 202513,000
836313-99DrillHalcon Operating Co., Inc.Feb 13, 2018Feb 14, 2018—13,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-50245————

Formation tops

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

FormationMD ftSubsea
Rustler1,859831
Yates3,062-372
CapitanCAPITAN REEF - HIGH FLOWS3,880-1,190
Delaware5,004-2,314
Clear ForkCLEARFORK——
Glorieta——
Holt——
Queen——
San AndresSAN ANDRES - HIGH FLOWS, H2S, CO——
Seven Rivers——

Perforations

Perforated and open-hole intervals.

FromToType
11,11921,247Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3751,04617.5867 S
9.6255,12712.251,540 S
7.62510,5728.75572 S
5.521,3456.751,695 S
521,3456.751,695 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
00Jul 29, 2025Jun 24, 2025Yes

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.

Nearby wells and their tops

NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM

Draw a cross-section

This well's tops beside its 5 nearest neighbours, subsea-aligned so they line up regardless of surface terrain.

Open the cross-section →

Sealy Ranch42-475-37455

0.0 KM · Halcon Operating Co., Inc. · Section with this well →

Rustler1,854835
Yates3,040-351
Capitan3,877-1,188
Delaware5,040-2,351
Queen—
Holt—
Glorieta—
Clear Fork—

11 TOPS · FIRST 8

Slaughter Ranch 8842-475-37547

0.6 KM · Halcon Operating Co., Inc. · Section with this well →

Rustler1,835855
Delaware5,026-2,336
Holt—
Queen—
San Andres—
Seven Rivers—
Tubb—
Clear Fork—

10 TOPS · FIRST 8

Sealy Ranch42-495-34074

0.8 KM · Halcon Operating Co., Inc. · Section with this well →

Rustler2,007691
Yates3,071-373
Capitan3,501-803
Delaware5,109-2,411
Colby-Queen—
Glorieta—
Holt—
Queen—

10 TOPS · FIRST 8

Sealy Ranch42-495-34073

0.8 KM · Halcon Operating Co., Inc. · Section with this well →

Rustler2,007691
Yates3,071-373
Capitan3,501-803
Delaware5,089-2,391
San Andres—
Holt—
Glorieta—
Clear Fork—

10 TOPS · FIRST 8

Sealy Ranch42-495-33877

1.6 KM · Halcon Operating Co., Inc. · Section with this well →

Clear Fork—
Colby-Queen—
Yates—
Wichita-Albany—
San Andres—
Rustler—
Queen—
Holt—

10 TOPS · FIRST 8

Sealy Ranch42-475-37353

1.6 KM · Halcon Operating Co., Inc. · Section with this well →

Rustler1,6401,050
Delaware4,930-2,240
Glorieta—
Holt—
Queen—
San Andres—
Yates—
Clear Fork—

10 TOPS · FIRST 8

Sealy Ranch42-475-38026

1.6 KM · Halcon Operating Co., Inc. · Section with this well →

Rustler1,834857
Delaware5,078-2,387
Glorieta—
Yates—
Tubb—
Seven Rivers—
San Andres—
Queen—

10 TOPS · FIRST 8

Sealy Ranch42-475-38027

1.7 KM · Halcon Operating Co., Inc. · Section with this well →

Rustler1,834857
Delaware5,078-2,387
Holt—
Queen—
Tubb—
San Andres—
Clear Fork—
Seven Rivers—

10 TOPS · FIRST 8

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