WELL · 42-227-34293 · DISTRICT 8

East Vealmoor Disposal Unit NO.2 #2

Plugged

Howard County  · Vertical

East Vealmoor Disposal Unit NO.2 #2 (API 42-227-34293) is a plugged well in Howard County, plugged May 7, 1988, last operated by Exxon Corp..

The RRC has issued 2 drilling permits between 1988 and 1997, permitted to 9,300 ft.

Completion filings report 6 formation tops, including Glorieta, Clear Fork, Spraberry, Dean.

It holds an active disposal or injection permit, with 666K barrels injected in the 12 months reported through December 2025.

Operator of record

Exxon Corp.

Houston, TX · P-5 Y, filed Jan 3, 2003 · 19,549 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitExxon Corp.Sep 30, 1997
9,300
total depth, ft
2
permits on file
Sep 30, 1997
last permit issued
—
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1999 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
May 7, 1988

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
East Vealmoor Disposal Unit NO.2 O-10-35967Vealmoor, EastSurge Operating, LLC200Jan 1999 – Jul 2026

No volumes reported on these leases in the last three years.

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
467915-99ReenterExxon Corp.Sep 22, 1997Sep 30, 1997Mar 5, 19989,300
343471-99DrillGeneral Atlantic Energy Corp.Mar 4, 1988Mar 8, 1988—7,900

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-35967————

Formation tops

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

FormationMD ftSubsea
Glorieta3,930-1,232
GlorietaGLORIETTA3,930-1,232
Clear ForkCLEARFORK4,504-1,806
Spraberry5,755-3,057
SpraberrySPRAYBERRY5,755-3,057
Dean7,002-4,304
Wolfcamp7,205-4,507
CP Reef7,872-5,174

Perforations

Perforated and open-hole intervals.

FromToType
7,8459,070Perforated
7,8459,070Open hole

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37540317.5400 S
8.6253,105111,349 S
5.57,8457.875600 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
00Sep 11, 2025Sep 4, 2025—
00May 24, 2019Mar 20, 2019—
00Aug 5, 2011May 18, 2011—
00Jun 22, 2000Sep 9, 1999—
00Apr 8, 1999Jan 26, 1999Yes
00Mar 27, 1999——

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.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

666K
bbl, last 12 reported months
30.7M
bbl, all reported
Dec 2025
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000087571H-1 InjectionActive15,0003,9007,800–9,200

MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS

Last 12 months 665,806 · prior 12 489,518(+36%)

0100K200K20242025

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