TEXAS · WELLS · MARTIN COUNTY · API 42-317-47079 · DISTRICT 08
Epley-Glasscock E8H #208H
Martin County · Horizontal
- Permitted field
- Spraberry (Trend Area)
Epley-Glasscock E8h #208H (API 42-317-47079) is a permitted horizontal well in Martin County filed by Pioneer Natural Res. USA, Inc.; no completion report is on file yet.
The RRC has issued one drilling permit, issued December 2, 2025, permitted to 10,505 ft.
Operator of record
Pioneer Natural Res. USA, Inc.
- Based in
- Spring, TX
- P-5 status
- Active (A)
- P-5 last filed
- Jul 8, 2026
- Permits on file
- 15,633
- Phone
- (972) 444-4001
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | none |
| Latest permit | Pioneer Natural Res. USA, Inc.Dec 2, 2025 |
- 10,505
- total depth, ft
- 1
- permits on file
- Dec 2, 2025
- 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.247650, -101.882035 NAD27, as filed
32.247768, -101.882448 WGS84
Permit surface location from the RRC GIS record, referenced to NAD27 as the RRC files it; the WGS84 pair is the same point through NOAA's NADCON grid, and the map link uses it, in Martin County.
Wells nearby
Every well with a location on file around this one, in any state, nearest first.
Loading the wells nearby…
Texas locations come from drilling permits, so most older Texas wells have none and are not listed.
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
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 911527-99 | Drill | Pioneer Natural Res. USA, Inc. | Oct 31, 2025 | Dec 2, 2025 | — | 10,505 |
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.
- Wellbore filings for 42-317-47079 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-317-47079 → scanned completion filings
Log images filed since 2004 open from the RRC's log search for this well; none are loaded here for it. The University Lands library has no per-well link: then paste it into its 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 neighbors can.
Section of the neighbors →Epley-Glasscock E8G42-317-47078
0.0 KM · Pioneer Natural Res. USA, Inc. · Section with this well →
| Santa Rosa | 1,468 | 1,387 |
| Yates | 2,550 | 305 |
| Queen | 3,371 | -516 |
| Grayburg | 3,776 | -921 |
| San Andres | 4,039 | -1,184 |
| Clear Fork | 6,176 | -3,321 |
| Spraberry | 7,441 | -4,586 |
| Cisco | — |
10 TOPS · FIRST 8
Epley-Glasscock E8I42-317-47080
0.0 KM · Pioneer Natural Res. USA, Inc. · Section with this well →
| Santa Rosa | 1,468 | 1,387 |
| Yates | 2,551 | 304 |
| Queen | 3,370 | -515 |
| Grayburg | 3,774 | -919 |
| San Andres | 4,034 | -1,179 |
| Clear Fork | 6,167 | -3,312 |
| Spraberry | 7,434 | -4,579 |
| Wolfcamp | — |
10 TOPS · FIRST 8
Epley-Glasscock E8F42-317-47077
0.0 KM · Pioneer Natural Res. USA, Inc. · Section with this well →
| Santa Rosa | 1,469 | 1,386 |
| Yates | 2,545 | 310 |
| Queen | 3,375 | -520 |
| Grayburg | 3,777 | -922 |
| San Andres | 4,042 | -1,187 |
| Clear Fork | 6,172 | -3,317 |
| Spraberry | 7,446 | -4,591 |
| Cisco | — |
10 TOPS · FIRST 8
Epley-Glasscock E8J42-317-47081
0.0 KM · Pioneer Natural Res. USA, Inc. · Section with this well →
| Santa Rosa | 1,467 | 1,388 |
| Yates | 2,552 | 303 |
| Queen | 3,372 | -517 |
| Grayburg | 3,775 | -920 |
| San Andres | 4,037 | -1,182 |
| Clear Fork | 6,185 | -3,330 |
| Spraberry | 7,447 | -4,592 |
| Cisco | — |
10 TOPS · FIRST 8
Epley-Glasscock E8E42-317-47076
0.0 KM · Pioneer Natural Res. USA, Inc. · Section with this well →
| Santa Rosa | 1,471 | 1,384 |
| Yates | 2,546 | 309 |
| Queen | 3,379 | -524 |
| Grayburg | 3,783 | -928 |
| San Andres | 4,049 | -1,194 |
| Clear Fork | 6,200 | -3,345 |
| Spraberry | 7,460 | -4,605 |
| Cisco | — |
10 TOPS · FIRST 8
Epley-Glasscock E8D42-317-47075
0.0 KM · Pioneer Natural Res. USA, Inc. · Section with this well →
| Santa Rosa | 1,471 | 1,384 |
| Yates | 2,549 | 306 |
| Queen | 3,376 | -521 |
| Grayburg | 3,775 | -920 |
| San Andres | 4,041 | -1,186 |
| Clear Fork | 6,183 | -3,328 |
| Spraberry | 7,451 | -4,596 |
| Cisco | — |
10 TOPS · FIRST 8
Epley-Carlile E8K42-317-47043
0.1 KM · Pioneer Natural Res. USA, Inc. · Section with this well →
| Santa Rosa | 1,482 | 1,373 |
| Yates | 2,556 | 299 |
| Queen | 3,375 | -520 |
| Grayburg | 3,775 | -920 |
| San Andres | 4,041 | -1,186 |
| Clear Fork | 6,189 | -3,334 |
| Spraberry | 7,460 | -4,605 |
| Dean | 8,767 | -5,912 |
10 TOPS · FIRST 8
Atchison-Wheeler 8D42-317-43762
0.2 KM · Pioneer Natural Res. USA, Inc. · Section with this well →
| Santa Rosa | 1,284 | 1,573 |
| Yates | 2,565 | 292 |
| Queen | 3,339 | -482 |
| Grayburg | 3,730 | -873 |
| San Andres | 3,977 | -1,120 |
| Spraberry | 7,464 | -4,607 |
| Dean | 8,771 | -5,914 |
| Wolfcamp | 8,997 | -6,140 |
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/31747079, documented in the API reference.