WELL · 42-389-32660 · DISTRICT 8
Roadrunner #1
Reeves County · Phantom (Wolfcamp) field · Producing · Vertical
Roadrunner #1 (API 42-389-32660) is a well in Reeves County operated by Permian Resources Operating LLC, completed August 11, 2011 and listed as producing on the RRC schedule.
The RRC has issued 2 drilling permits (amended once) between 2010 and 2017, permitted to 12,258 ft.
It was permitted by Centennial Resource Prod, LLC and has since transferred to Permian Resources Operating LLC on the wellbore schedule.
Completion filings report 7 formation tops, including Permian (undifferentiated), Delaware, Bell Canyon, Cherry Canyon.
Its 2 leases have reported 1.73M barrels of oil and 3.11M mcf of gas since August 2011, last reporting in July 2026. The leases carry 7 wells, so these are lease totals, not this well alone.
Operator of record
Permian Resources Operating LLC
Permitted by Centennial Resource Prod, LLC; the EWA schedule now lists a different operator.
- Based in
- Midland, TX
- P-5 status
- Active (A)
- P-5 last filed
- Nov 25, 2025
- Permits on file
- 608
- Phone
- (432) 695-4222
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Centennial Resource Prod LLC |
| Production reports | Permian Resources Operating, LLCthrough Apr 2026 |
| Latest permit | Centennial Resource Prod, LLCMar 17, 2017 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 12,258
- total depth, ft
- 3
- permits on file
- Mar 17, 2017
- last permit issued
- Aug 11, 2011
- completed
- 1.73M
- cumulative oil, bbl
- 3.11M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Aug 2011 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Aug 11, 2011
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: Active (A)
Surface location
No coordinates on the permit record yet. The RRC's GIS record usually lands within days of issuance; historical master-file permits never carry one.
Lease production
PDQ LEASE REPORTS · REPORTED THROUGH APR 2026
Texas reports oil by lease, not by well. These are the 2 leases this well is completed on; they carry 7 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Roadrunner O-10-48996 | Phantom (Wolfcamp) | Permian Resources Operating, LLC | 6 | 1.71M | 3.06M | Oct 2015 – Jul 2026 |
| Gibson O-10-42362 | Wolfbone (Trend Area) | Centennial Resource Prod, LLC | 1 | 27.9K | 45.2K | Aug 2011 – Feb 2018 |
Oil, barrels lease total
Last 12 months 156,506 · prior 12 95,801(+63%)
Gas, mcf lease total
Last 12 months 275,627 · prior 12 202,040(+36%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Atlantic Operating, Inc.Aug 2011 → Oct 2012
- 2Atlantic Exploration, LLCNov 2012 → Aug 2014
- 3Centennial Resource Prod, LLCSep 2014 → Dec 2022
- 4Permian Resources Operating, LLCJan 2023 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 824077-99 | Field transfer | Centennial Resource Prod, LLC | Mar 4, 2017 | Mar 17, 2017 | — | 13,000 |
| 696875-98 | Drill | Atlantic Operating, Inc. | Apr 19, 2011 | Jun 8, 2010 | Apr 19, 2011 | 13,000 |
| 696875-99 | Drill | Atlantic Operating, Inc. | Jun 1, 2010 | Jun 8, 2010 | — | 13,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Aug 11, 2011 | Roadrunner O-10-48996 | Phantom (Wolfcamp) | Permian Resources Operating LLC | Producing | 12,258 |
| Aug 11, 2011 | Gibson O-10-42362 | Wolfbone (Trend Area) | Centennial Resource Prod LLC | Not on Schedule | — |
Formation tops
As filed on W-2/G-1. Subsea from 2,744 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Permian (undifferentiated)PERMIAN | 1,175 | 1,569 |
| Delaware | 5,085 | -2,341 |
| Bell Canyon | 5,119 | -2,375 |
| DelawareDELAWARE CONSOLIDATED GAS | 5,119 | -2,375 |
| DelawareFORD-DELAWARE | 5,119 | -2,375 |
| Cherry Canyon | 6,018 | -3,274 |
| Bone Spring | 8,066 | -5,322 |
| Bone Spring3RD BONE SPRING | 9,590 | -6,846 |
| Hoban | 10,255 | -7,511 |
| Wolfcamp | 10,352 | -7,608 |
| Wolfcamp | 10,376 | -7,632 |
| Bone Spring3RD BONE SPRING | 10,750 | -8,006 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 10,282 | 12,029 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 13.375 | 965 | 17.5 | 850 S |
| 9.625 | 5,041 | 12.25 | 1,700 S |
| 5.5 | 12,258 | 8.75 | 1,770 S |
| 9.625 | — | 12.25 | 600 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 →
| Suffix | Filed | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Apr 11, 2018 | Mar 12, 2018 | — |
| 00 | Dec 6, 2017 | May 16, 2017 | Yes |
| 00 | Mar 25, 2013 | Sep 27, 2011 | Yes |
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-32660 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-389-32660 → 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.
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/38932660, documented in the API reference.