TEXAS · WELLS · REEVES COUNTY · API 42-389-41560 · DISTRICT 7B
Enterprise State 56-2-32-29 E #14H
Reeves County · Phantom (Wolfcamp) field · Horizontal
Enterprise State 56-2-32-29 E #14H (API 42-389-41560) is a plugged horizontal well in Reeves County, plugged August 25, 2025, last operated by Anadarko E&P Onshore LLC.
The RRC has issued one drilling permit, issued January 14, 2025, permitted to 13,000 ft.
It was permitted by Anadarko E&P Onshore LLC and has since transferred to Anadarko E&P Onshore LLC on the wellbore schedule.
Operator of record
Anadarko E&P Onshore LLC
Permitted by Anadarko E&P Onshore LLC; the EWA schedule now lists a different operator.
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | none |
| Latest permit | Anadarko E&P Onshore LLCJan 14, 2025 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 13,000
- total depth, ft
- 1
- permits on file
- Jan 14, 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
- Aug 25, 2025
Surface location
31.798956, -103.881614
Permit surface location from the RRC GIS record, in Reeves 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
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 905085-99 | Drill | Anadarko E&P Onshore LLC | Jan 9, 2025 | Jan 14, 2025 | Feb 16, 2025 | 13,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.
- Wellbore filings for 42-389-41560 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-389-41560 → scanned completion filings
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 neighbors can.
Enterprise State 56-2-32-29 E42-389-41685
0.0 KM · Anadarko E&P Onshore LLC · Section with this well →
| Delaware | 3,127 | -285 |
| Bell Canyon | 3,127 | -285 |
| Delaware | 3,154 | -312 |
| Delaware | 3,321 | -479 |
| Cherry Canyon | 4,104 | -1,262 |
| Bone Spring | 7,018 | -4,176 |
| Bone Spring | 8,259 | -5,417 |
| Bone Spring | 9,062 | -6,220 |
10 TOPS · FIRST 8
Enterprise State 56-2-32-29 F42-389-41559
0.0 KM · Anadarko E&P Onshore LLC · Section with this well →
| Bell Canyon | 3,129 | -288 |
| Delaware | 3,129 | -288 |
| Delaware | 3,159 | -318 |
| Delaware | 3,334 | -493 |
| Cherry Canyon | 4,097 | -1,256 |
| Bone Spring | 7,031 | -4,190 |
| Bone Spring | 8,270 | -5,429 |
| Bone Spring | 9,087 | -6,246 |
10 TOPS · FIRST 8
Enterprise State 56-2-32-29 G42-389-41558
0.0 KM · Anadarko E&P Onshore LLC · Section with this well →
| Castile | 2,208 | 633 |
| Bell Canyon | 3,128 | -287 |
| Delaware | 3,128 | -287 |
| Delaware | 3,151 | -310 |
| Delaware | 3,333 | -492 |
| Cherry Canyon | 4,102 | -1,261 |
| Bone Spring | 7,031 | -4,190 |
| Bone Spring | 8,279 | -5,438 |
10 TOPS · FIRST 8
Enterprise State 56-2-32-29 H42-389-41557
0.0 KM · Anadarko E&P Onshore LLC · Section with this well →
| Castile | 2,199 | 641 |
| Delaware | 3,128 | -288 |
| Bell Canyon | 3,128 | -288 |
| Delaware | 3,152 | -312 |
| Delaware | 3,333 | -493 |
| Cherry Canyon | 4,104 | -1,264 |
| Bone Spring | 7,062 | -4,222 |
| Bone Spring | 8,314 | -5,474 |
10 TOPS · FIRST 8
Enterprise State 56-2-32-29 I42-389-41703
0.0 KM · Anadarko E&P Onshore LLC · Section with this well →
| Delaware | 3,200 | -360 |
| Bell Canyon | 3,200 | -360 |
| Delaware | 3,221 | -381 |
| Delaware | 3,375 | -535 |
| Cherry Canyon | 4,177 | -1,337 |
| Bone Spring | 7,140 | -4,300 |
| Bone Spring | 8,385 | -5,545 |
| Bone Spring | 9,182 | -6,342 |
10 TOPS · FIRST 8
Baku State 56-2-41-44 F42-389-41528
0.6 KM · Anadarko E&P Onshore LLC · Section with this well →
| Bell Canyon | 3,151 | -298 |
| Delaware | 3,151 | -298 |
| Delaware | 3,182 | -329 |
| Delaware | 3,336 | -483 |
| Cherry Canyon | 4,138 | -1,285 |
| Bone Spring | 7,011 | -4,158 |
| Bone Spring | 8,242 | -5,389 |
| Bone Spring | 9,065 | -6,212 |
10 TOPS · FIRST 8
Baku State 56-2-41-44 G42-389-41529
0.6 KM · Anadarko E&P Onshore LLC · Section with this well →
| Bell Canyon | 3,149 | -296 |
| Delaware | 3,149 | -296 |
| Delaware | 3,170 | -317 |
| Delaware | 3,341 | -488 |
| Cherry Canyon | 4,125 | -1,272 |
| Bone Spring | 7,009 | -4,156 |
| Bone Spring | 8,248 | -5,395 |
| Bone Spring | 9,051 | -6,198 |
10 TOPS · FIRST 8
Baku State 56-2-41-44 H42-389-41530
0.6 KM · Anadarko E&P Onshore LLC · Section with this well →
| Bell Canyon | 3,155 | -302 |
| Delaware | 3,155 | -302 |
| Delaware | 3,177 | -324 |
| Delaware | 3,338 | -485 |
| Cherry Canyon | 4,140 | -1,287 |
| Bone Spring | 7,020 | -4,167 |
| Bone Spring | 8,269 | -5,416 |
| Bone Spring | 9,067 | -6,214 |
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/38941560, documented in the API reference.