WELL · 42-003-43237 · DISTRICT 8

Mabee 32 SWD #1

WaterN

Andrews County  · Vertical

Mabee 32 Swd #1 (API 42-003-43237) is a former disposal or injection well in Andrews County, last operated by High Lonesome Midstream, LLC; its UIC permits are no longer active.

The RRC has issued 2 drilling permits between 2011 and 2022, permitted to 7,000 ft.

Completion filings report one formation top, including San Andres.

Operator of record

High Lonesome Midstream, LLC

Midland, TX · P-5 Y, filed Nov 4, 2025 · 7 permits on file · (432) 695-6255

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitHigh Lonesome Midstream, LLCJun 15, 2022
7,000
total depth, ft
2
permits on file
Jun 15, 2022
last permit issued
—
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 2012 THROUGH Mar 2020

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
—

Surface location

32.313451, -102.245363

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Andrews 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; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Mabee O-10-41848Spraberry (Trend Area)Wasser Operating, LLC100Feb 2012 – Mar 2020

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

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
881033-99ReenterHigh Lonesome Midstream, LLCJun 9, 2022Jun 15, 2022—7,000
721233-99DrillMTN Energy IncJul 28, 2011Aug 4, 2011Nov 30, 20116,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-41848————

Formation tops

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

FormationMD ftSubsea
San Andres4,700-1,726

Perforations

Perforated and open-hole intervals.

FromToType
4,7945,296Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,82512.25650 S
75,9688.75450 S
7—8.75500 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 5, 2012Mar 27, 2012Yes

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 →

Pepe Paisano 3242-003-48747

0.5 KM · Birch Operations, Inc. · Section with this well →

Yates3,127-151
Seven Rivers3,324-348
Queen3,991-1,015
Grayburg4,674-1,698
San Andres5,031-2,055
Glorieta6,454-3,478
Clear Fork6,867-3,891
Holt—

10 TOPS · FIRST 8

Pepe Paisano 3242-003-48746

0.5 KM · Birch Operations, Inc. · Section with this well →

Yates3,132-156
Seven Rivers3,324-348
Queen3,992-1,016
Grayburg4,698-1,722
San Andres5,032-2,056
Glorieta6,445-3,469
Clear Fork6,887-3,911
Tubb—

10 TOPS · FIRST 8

Pepe Paisano 3242-003-48745

0.5 KM · Birch Operations, Inc. · Section with this well →

Yates3,126-150
Seven Rivers3,325-349
Queen3,992-1,016
Grayburg4,664-1,688
San Andres5,019-2,043
Glorieta6,451-3,475
Clear Fork6,878-3,902
Permian (undifferentiated)—

10 TOPS · FIRST 8

Pepe Paisano 3242-003-48744

0.5 KM · Birch Operations, Inc. · Section with this well →

Yates3,128-152
Seven Rivers3,326-350
Queen3,991-1,015
Grayburg4,681-1,705
San Andres5,018-2,042
Glorieta6,448-3,472
Clear Fork6,852-3,876
Tubb—

10 TOPS · FIRST 8

Pepe Paisano 3242-003-48743

0.5 KM · Birch Operations, Inc. · Section with this well →

Yates3,127-151
Seven Rivers3,328-352
Queen3,992-1,016
Grayburg4,666-1,690
San Andres5,030-2,054
Glorieta6,478-3,502
Clear Fork6,871-3,895
Tubb—

10 TOPS · FIRST 8

Pepe Paisano 3242-003-48742

0.5 KM · Birch Operations, Inc. · Section with this well →

Yates3,120-144
Glorieta6,483-3,507
Clear Fork6,876-3,900
Spraberry8,449-5,473
Holt—
Dean—
Permian (undifferentiated)—
Wichita-Albany—

10 TOPS · FIRST 8

Putnam the Pio 3242-003-48748

0.5 KM · Birch Operations, Inc. · Section with this well →

Yates3,107-134
Seven Rivers3,308-335
Queen3,969-996
Grayburg4,641-1,668
San Andres4,994-2,021
Glorieta6,409-3,436
Clear Fork6,831-3,858
Holt—

10 TOPS · FIRST 8

Putnam the Pio 3242-003-48749

0.5 KM · Birch Operations, Inc. · Section with this well →

Yates3,108-134
Seven Rivers3,309-335
Queen3,971-997
Grayburg4,632-1,658
San Andres4,997-2,023
Glorieta6,405-3,431
Clear Fork6,833-3,859
Holt—

10 TOPS · FIRST 8

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

0
bbl, last 12 reported months
9.6M
bbl, all reported
Jan 2026
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000104256W-14 DisposalPlugged Sep 12, 201915,0002,3504,700–5,300
000125576W-14 DisposalCanceled Oct 27, 202520,0002,2804,560–6,850

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

Last 12 months 0 · prior 12 0

0120252026

TexNet catalog via USGS

Seismicity near this well

4
M2+ events within 10 km, last 2 years
M2.4
largest

A proximity count, not an attribution. How to read it →

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