WELL · 42-185-30882 · DISTRICT 3

Sealy #1H

Plugged

Grimes County · Fort Trinidad East (Buda) field  · Horizontal

Sealy #1H (API 42-185-30882) is a plugged horizontal well in Grimes County, plugged October 14, 2017, last operated by Etx Energy LLC.

The RRC has issued one drilling permit, issued June 27, 2017, permitted to 11,500 ft.

It was permitted by Etx Energy, LLC and has since transferred to Etx Energy LLC on the wellbore schedule.

Operator of record

Etx Energy LLC

Permitted by Etx Energy, LLC; the EWA schedule now lists a different operator.

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitEtx Energy, LLCJun 27, 2017

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

11,500
total depth, ft
1
permits on file
Jun 27, 2017
last permit issued
—
completed
—
cumulative oil, bbl
—
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
Oct 14, 2017

Surface location

30.773238, -95.894942

OpenStreetMap → ·  Google Maps →

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

Only the permit record exists for this well so far, here and in the RRC's wellbore query. Completion reports, formation tops, lease production, and the scanned filings appear once the operator files a completion report, typically months after drilling. Petrora refreshes the wellbore file weekly, so a filing from the last few days may reach the RRC before it shows here. How long each source takes →

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
827571-99DrillEtx Energy, LLCJun 7, 2017Jun 27, 2017Oct 6, 201711,500

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). 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 has no tops filed, so it cannot anchor a section; its neighbours can.

Section of the neighbours →

Sealy42-185-30885

0.0 KM · Etx Energy, LLC · Section with this well →

Woodbine1,156-870
Wilcox3,300-3,014
Austin Chalk9,809-9,523
Sub-Clarksville10,065-9,779
Woodbine10,125-9,839
Jackson—
Cook Mountain—

Evelyn42-185-30886

9.3 KM · Etx Energy, LLC · Section with this well →

Wilcox4,500-4,274
Sub-Clarksville9,139-8,913
Woodbine9,233-9,007
Buda10,026-9,800
Jackson—
Austin Chalk—
Cook Mountain—
Woodbine—

Colburn Unit42-471-30374

10.3 KM · EOG Resources, Inc. · Section with this well →

Wilcox2,485-2,240
Austin Chalk9,366-9,121
Woodbine9,770-9,525
Eagle Ford10,390-10,145
Buda10,635-10,390
Glen Rose11,612-11,367

Colburn42-471-30351

10.5 KM · EOG Resources, Inc. · Section with this well →

Buda10,764-10,493
Georgetown11,023-10,752
Kiamichi11,229-10,958
Edwards11,571-11,300

Iron Duke (Allocation)42-313-31342

11.1 KM · Etx Energy, LLC · Section with this well →

Wilcox4,535-4,319
Sub-Clarksville9,356-9,140
Buda9,365-9,149
Eagle Ford9,918-9,702
Woodbine10,134-9,918
Georgetown—
Dex-Buda—
Frio—

10 TOPS · FIRST 8

Lewis42-185-30900

11.4 KM · Pride Energy Company · Section with this well →

Wilcox2,518-2,185
Jackson—
Sub-Clarksville—
Woodbine—
Woodbine—
Cook Mountain—
Austin Chalk—

Carter Knox42-185-30891

12.0 KM · Apache Corporation · Section with this well →

Jackson1,137
Cook Mountain1,743
Wilcox2,506
Sub-Clarksville—
Woodbine—
Woodbine—
Austin Chalk—

Iron Duke SWD42-313-31333

14.2 KM · Etx Energy, LLC · Section with this well →

Wilcox3,799-3,569
Sub-Clarksville9,224-8,994
Woodbine9,272-9,042
Buda—
Frio—
Dex-Buda—
Lewisville - Disposal—
Rodessa—

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