WELL · 42-317-37653 · DISTRICT 8

Martin County Brine Station #1

Plugged

Martin County · Spraberry (Trend Area) field  · Vertical

Martin County Brine Station #1 (API 42-317-37653) is a plugged well in Martin County, plugged October 27, 2023, last operated by High Lonesome Midstream LLC.

The RRC has issued one drilling permit, issued March 22, 2012, permitted to 2,900 ft.

It was permitted by Mesquite Swd Inc and has since transferred to High Lonesome Midstream LLC on the wellbore schedule.

Completion filings report one formation top, including Salado.

Operator of record

High Lonesome Midstream LLC

Permitted by Mesquite SWD Inc; the EWA schedule now lists a different operator.

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 scheduleHigh Lonesome Midstream LLC
Production reportsnone
Latest permitMesquite SWD IncMar 22, 2012

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

2,900
total depth, ft
1
permits on file
Mar 22, 2012
last permit issued
Mar 26, 2012
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 2013 THROUGH Nov 2023

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Mar 26, 2012
Shut in
—
Plugged
Oct 27, 2023

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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Martin County Brine Station O-10-45351Spraberry (Trend Area)High Lonesome Midstream, LLC100Sep 2013 – Nov 2023
Martin County Brine Station O-10-45571Spraberry (Trend Area)Mesquite SWD Inc100Jan 2013 – Apr 2015

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

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
736549-99DrillMesquite SWD IncMar 21, 2012Mar 22, 2012Mar 24, 20122,900

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-45351————
—— O-10-45571————

Formation tops

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

FormationMD ftSubsea
Salado1,8001,043

Perforations

Perforated and open-hole intervals.

FromToType
2,2002,400Open hole

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62542012.25220 S
72,2008.75450 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 21, 2021Oct 7, 2020—
00Jan 7, 2015Oct 15, 2013—
00Nov 12, 2014Sep 28, 2012—

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.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

0
bbl, last 12 reported months
0
bbl, all reported
—
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000105087UIC PermitPlugged Nov 10, 20231,0007002,200–2,400

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