WELL · 42-227-39666 · DISTRICT 10

29.5 #01

N

Howard County  · Vertical

29.5 #01 (API 42-227-39666) is a permitted well in Howard County filed by Magellan Pipeline Company, L.P.; no completion report is on file yet.

The RRC has issued one drilling permit, issued June 8, 2018, permitted to 500 ft.

Operator of record

Magellan Pipeline Company, L.P.

Tulsa, OK · P-5 Y, filed Apr 4, 2026 · 82 permits on file · (800) 666-9041

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitMagellan Pipeline Company, L.P.Jun 8, 2018
500
total depth, ft
1
permits on file
Jun 8, 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.170415, -101.567989

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Howard 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
839975-99DrillMagellan Pipeline Company, L.P.May 11, 2018Jun 8, 2018—500

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.

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 →

Hot Springs 2486CP42-227-42314

0.7 KM · OXY USA Inc. · Section with this well →

Rustler1,1551,334
Yates1,754735
Seven Rivers2,018471
San Andres3,255-766
Clear Fork4,938-2,449
Spraberry6,080-3,591
Leonard6,992-4,503
Dean7,289-4,800

10 TOPS · FIRST 8

Hot Springs 2446DP42-227-42313

0.7 KM · OXY USA Inc. · Section with this well →

Rustler1,1581,331
Yates1,748741
Seven Rivers2,013476
San Andres3,254-765
Clear Fork4,939-2,450
Spraberry6,111-3,622
Leonard7,002-4,513
Dean7,288-4,799

10 TOPS · FIRST 8

Hot Springs 2444DP42-227-42310

1.0 KM · OXY USA Inc. · Section with this well →

Rustler1,1531,340
Yates1,752741
Seven Rivers2,012481
San Andres3,274-781
Clear Fork4,959-2,466
Spraberry6,138-3,645
Leonard7,028-4,535
Dean7,328-4,835

10 TOPS · FIRST 8

Hot Springs 2484CP42-227-42309

1.0 KM · OXY USA Inc. · Section with this well →

Rustler1,1621,332
Yates1,744750
Seven Rivers2,013481
San Andres3,271-777
Clear Fork4,961-2,467
Spraberry6,148-3,654
Leonard7,028-4,534
Dean7,309-4,815

10 TOPS · FIRST 8

Waymore 18-19-B42-227-40110

1.6 KM · Parsley Energy Operations, LLC · Section with this well →

San Andres3,071-524
Clear Fork4,896-2,349
Spraberry5,977-3,430
Dean7,367-4,820
Wolfcamp7,443-4,896
Seven Rivers—
Coleman Junction—
Yates—

10 TOPS · FIRST 8

Waymore 18-19-D42-227-40111

1.6 KM · Parsley Energy Operations, LLC · Section with this well →

San Andres3,069-522
Clear Fork4,986-2,439
Spraberry5,916-3,369
Dean7,410-4,863
Wolfcamp7,464-4,917
Coleman Junction—
Leonard—
Seven Rivers—

10 TOPS · FIRST 8

Hot Springs 2442DP42-227-42312

1.6 KM · OXY USA Inc. · Section with this well →

Rustler1,1571,336
Yates1,752741
Seven Rivers2,012481
San Andres3,293-800
Clear Fork4,998-2,505
Spraberry6,158-3,665
Leonard7,010-4,517
Dean7,317-4,824

10 TOPS · FIRST 8

Hot Springs 2482CP42-227-42311

1.6 KM · OXY USA Inc. · Section with this well →

Rustler1,1111,383
Yates1,749745
Seven Rivers2,015479
San Andres3,320-826
Clear Fork4,994-2,500
Spraberry6,155-3,661
Leonard7,000-4,506
Dean7,316-4,822

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