Palo Verde 1

Refueling Outage · Day 13

Arizona Public Service·Tonopah, AZ·PWR·1,311 MWe

Data refreshed 11.1h ago Rx Status: Oct 15, 2026 at 5:21 AM (M-F)

Reactor Status Timeline

Refueling Outage · Day 13 NRC data, Mon to Fri ? Actual daily reactor status from NRC reports (Mon to Fri) and the current state. What is coming -- the utility's published Scheduled outage and NukeWorker's model Projection -- is part of a subscription. Colored by status. How far ahead you can see depends on your plan.
Nov2025DecJan2026FebMarAprMayJunJulAugSepOctOnline: Oct 15, 2025 to Oct 2, 2026Refueling Outage (1R26): Oct 3, 2026 to Oct 15, 20261R26Today
OnlineRefueling Outage
?
Composite Operational Excellence Score (0-100) — average percentile rank across 7 dimensions in three sub-scores: Reliability (capacity factor, forced outage days, B2B avg streak), Efficiency (fuel utilization, refuel duration), and Discipline (startup duration, scram count). 5-year window. Higher = more operationally excellent. Click to see the full breakdown.
   
Excellence
Rank locked · 93 units
Subscribers
?
Days of continuous operation since the last outage ended (Started 2026-10-15). Has forced outage(s) since last refueling.
--
Current Run
offline
?
Longest recorded period of continuous operation between outages (2013-04-28 to 2014-10-11).
531
Record Run
days
?
Breaker-to-Breaker runs — continuous operation exceeding the cycle-adjusted threshold set for this unit with no trips to 0% power.
10
B2B Runs
?
Lifetime capacity factor: average power level across all recorded days (100% = always at full power).
88.1%
Capacity Factor
?
Net electricity actually generated over the most recent 12 months reported by the U.S. EIA (Form EIA-923), summed across every unit at this plant. Authoritative actuals, not an estimate.
31.17 TWh
Net Generation
EIA-923 · 12 mo to 2026-07 · plant total
?
Total number of scheduled refueling outages detected in the historical data.
19
Outages
since 1999
?
Average time from first power generation (>0%) to sustained full power (≥95% for 2+ days) across the last 3 scheduled outages. Click to compare against the fleet on the Operator Efficiency Leaderboard.
4.3
Avg Startup
days (last 3)
?
Average fuel utilization — percent of the designed fuel cycle that this unit consumes before refueling, derived from the historical burn-down trajectory. Higher = more efficient operator (refuels with less margin remaining; closer to coastdown). Computed as 100% minus the unit's average refuel-point fuel %, using the last 3 years where available, otherwise lifetime average. Click to compare against the fleet on the Operator Efficiency Leaderboard.
98.9%
Fuel Utilization
3yr avg

Reactor Status

Capacity Factor (365-Day)

?
0%
Current
96.4%
365-Day Avg
#5
of 94 plants
Min: 0% Max: 100% 13 days <80%

Outage Days by Year

?
Total days spent in outage each year, split by scheduled refueling (blue) and forced/unplanned (red). Lower totals indicate better reliability and outage execution. Hover for details.
Across its recorded history, Palo Verde 1 has spent 776 days in scheduled refueling outages and 235 days in forced or unplanned outages. Taller bars mark the years with the most downtime.
?
Duration of each outage in days, shown chronologically. Green bars are scheduled refueling outages, red bars are forced/unscheduled. The orange dashed line marks the average duration. Extended outages (>180 days) and D&D periods are excluded.

Outage Duration Trend

Palo Verde 1 has 41 outages plotted here, averaging 25 days each. The most recent, in Oct 2026, was a scheduled refueling outage lasting 13 days.
?
Scheduled refueling outage durations over time. Green bars are at or below this unit's average, amber up to 30% above it, red beyond that. The dashed line is the average. Shorter outages mean better execution.

Refueling Duration Trend

Palo Verde 1 has completed 19 scheduled refueling outages on record, averaging 41 days each. The most recent, in Oct 2026, ran 13 days.
?
Time in days from first power generation (>0%) to sustained full power (≥95% for 2+ consecutive days) after each scheduled refueling outage. The dashed line marks the average. Includes startup testing holds and power dips.

Startup Duration Trend

After a refueling outage, Palo Verde 1 takes about 4 days to climb from first power back to full power. That average is drawn from 17 startups on record, and the most recent took 4 days.
?
Daily reactor power over the 120 days before each scheduled refueling outage, one line per refueling, lined up on the day the outage began. A coastdown is the slow decline as the fuel runs out near the end of a cycle. The highlighted line is the most recent refueling and fainter lines are older. Counts and medians cover coastdowns of a week or longer. A shutdown straight from full power, with no decline ahead of it, is what a forced outage looks like.

Coastdown Before Refueling

4 of 19 refuelings 9 days median 90% power at shutdown 0.6% per day
Palo Verde 1 coasted down for a week or longer before 4 of its 19 refuelings on record. Those coastdowns ran a median of 9 days and ended near 90% power. The most recent refueling, in Oct 2026, began with no extended coastdown.
?
Monthly capacity factor with outage events overlaid as red bands. Green bars show average power level per month. Toggle to Daily view for raw daily data.

Power History

Over its operating life, Palo Verde 1 has run at about 88.1% of its rated capacity. Across the last 12 reported months it averaged 92.7%. On the chart, green stretches near the top are full-power running, amber marks reduced power (50 to 89%), and red drops toward zero are outages.

Outage History & Daily Power Log

This table logs every recorded outage for Palo Verde 1, 41 in all since 1999. Of those, 19 were scheduled refueling outages and 22 were unplanned or forced. The typical outage lasted about 25 days. Where the Scheduled column shows (Model), the date is a NukeWorker projection because the utility had not published one.
Scheduled 1R26
2026-10-03 In Outage 13+ 511d 2026-10-03 0d
Scheduled 1R25
2025-03-29 2025-05-10 43 504d 2025-04-09 -11d
Scheduled 1R24
2023-10-07 2023-11-11 36 178d 2023-10-10 -3d
Scram # 56459 Auto
2023-04-09 2023-04-12 4 331d - -
Scheduled 1R23
2022-04-09 2022-05-13 35 493d 2022-04-09 0d
Scheduled 1R22
2020-10-10 2020-12-02 54 521d 2020-10-10 0d
Scheduled 1R21
2019-04-06 2019-05-08 33 412d 2019-04-05 +1d
Scram # 53215 Auto
2018-02-16 2018-02-18 3 103d - -
Scheduled 1R20
2017-10-07 2017-11-05 30 390d 2017-10-07 0d
Scram # 52226 Manual
2016-09-08 2016-09-12 5 117d - -
Scheduled 1R19
2016-04-09 2016-05-14 36 515d 2016-04-09 0d
Scheduled 1R18
2014-10-11 2014-11-11 32 531d 2014-10-11 0d
Scheduled 1R17
2013-03-30 2013-04-28 30 489d 2013-03-30 0d
Scheduled 1R16
2011-10-08 2011-11-27 51 59d 2011-10-08 0d
Scram # 47133 Auto
2011-08-07 2011-08-10 4 442d - -
Scheduled 1R15
2010-04-03 2010-05-22 50 15d 2010-03-20 +14d
Unscheduled
2010-03-08 2010-03-19 12 476d - -
Scheduled 1R14
2008-10-05 2008-11-17 44 119d 2008-10-04 +1d
Unscheduled
2008-06-07 2008-06-08 2 191d - -
Unscheduled
2007-11-24 2007-11-29 6 23d - -
Unscheduled
2007-10-23 2007-11-01 10 97d - -
Scheduled 1R13
2007-05-19 2007-07-18 61 209d 2007-05-18 +1d
Unscheduled
2006-10-22 2006-10-22 1 7d - -
Unscheduled
2006-09-20 2006-10-15 26 75d - -
Unscheduled
2006-03-18 2006-07-07 112 57d - -
Unscheduled
2006-01-18 2006-01-20 3 27d - -
Scheduled 1R12SGR/Major
2005-10-08 2005-12-22 76 41d 2005-10-07 +1d
Unscheduled
2005-08-13 2005-08-28 16 145d - -
Unscheduled
2005-03-19 2005-03-21 3 28d - -
Unscheduled
2005-02-10 2005-02-19 10 237d - -
Unscheduled
2004-06-15 2004-06-18 4 36d - -
Scheduled 1R11
2004-04-03 2004-05-10 38 56d 2004-04-02 +1d
Unscheduled
2004-02-04 2004-02-07 4 178d - -
Unscheduled
2003-08-10 2003-08-10 1 132d - -
Unscheduled
2003-03-28 2003-03-31 4 136d - -
Unscheduled
2002-11-11 2002-11-12 2 10d - -
Unscheduled
2002-11-01 2002-11-01 1 2d - -
Scheduled 1R10
2002-09-28 2002-10-30 33 503d 2002-09-28 0d
Scheduled 1R9
2001-03-31 2001-05-13 44 510d 2001-03-31 0d
Scheduled 1R8
1999-10-02 1999-11-07 37 204d 1999-10-02 0d
Unscheduled
1999-03-11 1999-03-12 2 - - -
Page created in 0.227 seconds with 13 queries (cached).