WELL · 42-317-41072 · DISTRICT 8

Mims 32H #3317AH

Y

Martin County · Spraberry (Trend Area) field · Shut IN  · Horizontal

Mims 32h #3317AH (API 42-317-41072) is a horizontal well in Martin County operated by Xto Energy Inc., completed February 23, 2018 and listed as shut in on the RRC schedule.

The RRC has issued one drilling permit, issued November 7, 2017, permitted to 8,800 ft.

Completion filings report 10 formation tops, including Santa Rosa, Yates, Queen, Grayburg.

Its lease has reported 3.08M barrels of oil and 7.5M mcf of gas since December 2017, last reporting in July 2026. The lease carries 10 wells, so these are lease totals, not this well alone.

Operator of record

XTO Energy Inc.

Spring, TX · P-5 Y, filed Feb 4, 2026 · 16,156 permits on file · (832) 625-1100

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleXTO Energy Inc.
Production reportsXTO Energy Inc.through Apr 2026
Latest permitXTO Energy Inc.Nov 7, 2017
8,800
total depth, ft
1
permits on file
Nov 7, 2017
last permit issued
Feb 23, 2018
completed
3.08M
cumulative oil, bbl
7.5M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Dec 2017 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Feb 23, 2018
Shut in
—
Plugged
—

Operator's P-5 on the schedule: X

Surface location

32.319954, -101.814147

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Martin 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 10 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Mims 32H O-10-50345Spraberry (Trend Area)XTO Energy Inc.103.08M7.5MDec 2017 – Jul 2026

Oil, barrels lease total

Last 12 months 82,478 · prior 12 70,456(+17%)

05K10K15K202420252026

Gas, mcf lease total

Last 12 months 332,899 · prior 12 589,269(-44%)

050K100K202420252026

Chain of custody

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

  1. 1XTO Energy Inc.Aug 2018 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
832357-99DrillXTO Energy Inc.Oct 24, 2017Nov 7, 2017Jan 30, 20188,800

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-50345————

Formation tops

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

FormationMD ftSubsea
Santa Rosa1,0201,615
Yates2,272363
Queen3,368-733
Grayburg3,750-1,115
San AndresSAN ANDRES - ACTIVE CO2 FLOOD; H3,872-1,237
Spraberry7,064-4,429
Dean8,394-5,759
Wolfcamp8,593-5,958
Cisco——
Pennsylvanian——

Perforations

Perforated and open-hole intervals.

FromToType
9,30319,494Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3751,30017.51,080 S
9.6258,04212.252,320 S
5.519,6278.52,330 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
00Dec 19, 2018Oct 30, 2018Yes
00Oct 26, 2018Aug 3, 2018Yes

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 →

Mims 32H42-317-41093

0.0 KM · XTO Energy Inc. · Section with this well →

Santa Rosa1,0201,615
Yates2,270365
Queen3,366-731
Grayburg3,750-1,115
San Andres3,872-1,237
Spraberry7,069-4,434
Pennsylvanian—
Wolfcamp—

10 TOPS · FIRST 8

Mims 32H42-317-41073

0.2 KM · XTO Energy Inc. · Section with this well →

Santa Rosa1,0181,614
Yates2,266366
Queen3,361-729
Grayburg3,749-1,117
San Andres3,872-1,240
Spraberry7,071-4,439
Cisco—
Wolfcamp—

10 TOPS · FIRST 8

Mims 32H42-317-41078

0.2 KM · XTO Energy Inc. · Section with this well →

Santa Rosa1,0131,619
Yates2,259373
Queen3,353-721
Grayburg3,744-1,112
San Andres3,865-1,233
Spraberry7,061-4,429
Wolfcamp—
Cisco—

10 TOPS · FIRST 8

Mims 32H42-317-41089

0.2 KM · XTO Energy Inc. · Section with this well →

Santa Rosa1,0181,621
Yates2,279360
Queen3,375-736
Grayburg3,759-1,120
San Andres3,884-1,245
Spraberry7,091-4,452
Dean—
Wolfcamp—

10 TOPS · FIRST 8

Mims 32H42-317-41074

0.2 KM · XTO Energy Inc. · Section with this well →

Santa Rosa1,0201,612
Yates2,266366
Queen3,361-729
Grayburg3,753-1,121
San Andres3,870-1,238
Spraberry7,069-4,437
Dean8,396-5,764
Wolfcamp8,591-5,959

10 TOPS · FIRST 8

Mims 32H42-317-41090

0.2 KM · XTO Energy Inc. · Section with this well →

Santa Rosa1,0161,624
Yates2,275365
Queen3,374-734
Grayburg3,760-1,120
San Andres3,883-1,243
Spraberry7,089-4,449
Cisco—
Dean—

10 TOPS · FIRST 8

Mims 32H42-317-41075

0.2 KM · XTO Energy Inc. · Section with this well →

Santa Rosa1,0061,626
Yates2,258374
Queen3,354-722
Grayburg3,741-1,109
San Andres3,859-1,227
Spraberry7,061-4,429
Dean8,387-5,755
Wolfcamp8,588-5,956

10 TOPS · FIRST 8

Mims 32H42-317-41092

0.2 KM · XTO Energy Inc. · Section with this well →

Santa Rosa1,0261,613
Yates2,280359
Queen3,374-735
Grayburg3,764-1,125
San Andres3,887-1,248
Spraberry7,079-4,440
Dean8,403-5,764
Wolfcamp8,607-5,968

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