WELL · 42-317-41225 · DISTRICT 10

UL Mustang 13 #9

N

Martin County  · Horizontal

UL Mustang 13 #9 (API 42-317-41225) is a permitted horizontal well in Martin County filed by Exl Petroleum Operating Inc.; no completion report is on file yet.

The RRC has issued one drilling permit, issued January 30, 2018, permitted to 12,000 ft.

Operator of record

EXL Petroleum Operating Inc.

Midland, TX · P-5 Y, filed Sep 4, 2020 · 87 permits on file · (432) 686-8080

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitEXL Petroleum Operating Inc.Jan 30, 2018
12,000
total depth, ft
1
permits on file
Jan 30, 2018
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
—

Surface location

32.427637, -102.199211

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Martin 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
835440-99DrillEXL Petroleum Operating Inc.Jan 22, 2018Jan 30, 2018—12,000

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

Section of the neighbours →

UL 0312 E142-317-41947

1.7 KM · QEP Energy Company · Section with this well →

Santa Rosa1,4181,504
Yates2,980-58
Queen3,930-1,008
Grayburg4,468-1,546
San Andres4,629-1,707
Spraberry8,282-5,360
Dean—
Cisco—

10 TOPS · FIRST 8

UL 0312 E242-317-41948

1.7 KM · QEP Energy Company · Section with this well →

Santa Rosa1,4141,508
Yates2,983-61
Queen3,934-1,012
Grayburg4,469-1,547
San Andres4,631-1,709
Spraberry8,288-5,366
Strawn—
Cisco—

11 TOPS · FIRST 8

UL 0312 E342-317-41949

1.8 KM · QEP Energy Company · Section with this well →

Santa Rosa1,4181,504
Yates2,980-58
Queen3,933-1,011
Grayburg4,469-1,547
San Andres4,634-1,712
Spraberry8,292-5,370
Dean9,545-6,623
Wolfcamp9,725-6,803

10 TOPS · FIRST 8

UL 0312 E442-317-41950

1.8 KM · QEP Energy Company · Section with this well →

Santa Rosa1,4211,502
Yates2,983-60
Queen3,938-1,015
Grayburg4,474-1,551
San Andres4,637-1,714
Spraberry8,286-5,363
Dean—
Cisco—

14 TOPS · FIRST 8

UL 0312 E542-317-41951

1.8 KM · QEP Energy Company · Section with this well →

Santa Rosa1,4311,506
Yates2,998-61
Queen3,948-1,011
Grayburg4,484-1,547
San Andres4,650-1,713
Spraberry8,305-5,368
Cisco—
Pennsylvanian—

10 TOPS · FIRST 8

UL 0312 E642-317-41952

1.8 KM · QEP Energy Company · Section with this well →

Santa Rosa1,4361,501
Yates2,996-59
Queen3,950-1,013
Grayburg4,489-1,552
San Andres4,656-1,719
Spraberry8,304-5,367
Cisco—
Pennsylvanian—

10 TOPS · FIRST 8

UL 0312 E742-317-41953

1.8 KM · QEP Energy Company · Section with this well →

Santa Rosa1,4321,505
Yates3,003-66
Queen3,958-1,021
Grayburg4,497-1,560
San Andres4,662-1,725
Spraberry8,313-5,376
Cisco—
Dean—

10 TOPS · FIRST 8

UL 0312 E942-317-41955

1.8 KM · QEP Energy Company · Section with this well →

Santa Rosa1,4261,512
Yates3,002-64
Queen3,957-1,019
Grayburg4,487-1,549
San Andres4,661-1,723
Spraberry8,298-5,360
Cisco—
Pennsylvanian—

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