Equivalent Forced Outage Rate For Wind

A wind operator submits a quarterly North American Electric Reliability Corporation Generator Availability Data System (NERC GADS) report, pulls the conventional equivalent forced outage rate (EFOR) formula from Appendix F, and applies it to the wind fleet. The operator gets the wrong number because NERC wrote Appendix F for thermal units, while the wind reporting framework removed the pieces that formula depends on. This is where most confusion about equivalent forced outage rate wind begins.

The equivalent forced outage rate measures forced outage hours as a fraction of the total hours a unit could have generated. Written plainly: it is forced outage hours divided by the sum of service hours plus forced outage hours, expressed as a percentage.

For wind, NERC reports a wind-specific Weighted Resource EFOR view through GADS-Wind instead of applying the conventional Appendix F EFOR calculation. Using the thermal formula in a wind filing is a mistake. It misapplies the wrong methodology to a fundamentally different resource type. The consequences include:

• Misstated forced turbine-hour exposure
• Distorted compliance submissions and resource adequacy filings
• Distorted fleet benchmarks

What is the equivalent forced outage rate for wind

The equivalent forced outage rate for wind is a reliability metric that expresses how much of a wind plant’s potential generating time is lost to forced outages, weighted by capacity across the fleet. NERC designed conventional EFOR for thermal units, where a unit runs at a defined capacity and the thermal methodology converts partial capacity reductions into equivalent full-outage hours. Wind does not work that way.

The current 2026 GADS-Wind Data Reporting Instructions (DRI), version 4.9, contains no conventional EFOR formula for wind.

• Version 4.3, published in January 2024, states in its revision history that NERC removed “‘Equivalent’ (no derates) from pertinent equations and acronyms from Appendix M.”
• NERC requires operators to report wind turbines in discrete outage states instead of equivalized partial deratings.
• The concept of Equivalent Forced Derated Hours (EFDH), which the conventional EFOR depends on, is absent from the mandatory wind reporting framework.
• Derate reporting exists in the wind standard, but operators report it voluntarily.

This adaptation reflects a physical reality. A wind plant’s maximum capacity changes constantly because it depends on atmospheric conditions. NERC notes in its wind training material that derate lost generation for wind is “very technical to calculate” for exactly this reason. When the wind drops, the turbine produces less because of a resource condition. Treating that reduction as a forced derate produces a metric that misrepresents the asset. NERC’s answer was to use named turbine-hour states and a capacity-weighted forced outage rate for the operative fleet view.

The EFOR formula for wind, step by step

The operative wind metric starts with forced turbine-hours rather than the thermal service-and-derate structure. The building blocks come directly from the performance record fields that NERC defines in Table 4.2 of the 2026 GADS-Wind DRI.

The core inputs for wind forced outage accounting are:

• Forced Turbine-Hours (FTH): The sum of all turbine-hours off-line due to forced events where the Wind Turbine Generator must be removed from service for repairs before the next Sunday at 23:59.
• Contact Turbine-Hours (CTH): Turbine-hours synchronized with the main contactor closed and generation provided to the grid.
• Net Maximum Capacity (NMC): Actual generating capability in MW at the subgroup boundary, equal to installed capacity less electrical losses.

For context, the conventional thermal EFOR from Appendix F reads as follows: EFOR = ∑(FOH + EFDH) / ∑(FOH + SH + Synchronous Condensing Hours + Pumping Hours + EFDHRS) × 100%, where FOH is forced outage hours, EFDH is equivalent forced derated hours, SH is service hours, and EFDHRS is equivalent forced derated hours during reserve shutdown. That formula cannot be assumed to apply to wind, because NERC removed the equivalent-derate terms from the wind equations in January 2024.

Appendix M of the 2026 DRI is the place to verify the current wind-specific forced outage equation before you build a calculation pipeline. Available NERC materials confirm the required wind inputs and the removal of equivalent-derate terms, but teams should confirm the current Appendix M equation directly before automating the calculation. If your reporting logic still assumes EFDH, it is applying a thermal formula to a wind framework that no longer contains that term.

How NERC GADS-Wind collects forced outage data

NERC GADS collects wind performance data in a three-level hierarchy that rolls turbine data up to the plant. Understanding where each number originates tells you where classification errors enter the submission.

The reporting structure works as follows:

1. Individual turbine operational data aggregates into sub-group performance records at the turbine level.
2. Sub-group performance data rolls up into the plant-level performance record.
3. Reporting teams submit event data separately at the plant level.

A plant is a collection of wind turbine groups at a single physical location. A single manager manages that plant from a common Operations and Management building. Operators collect performance data such as FTH and CTH at the sub-group level. Active Turbine-Hours also comes from the sub-group level. Reporting teams submit forced outage events at the plant level and only when the loss of capacity meets the reportable threshold of at least 20 MW of Plant Total Installed Capacity.

Plants submit through the GADS Wind reporting application, an online portal.

Access requires:

• NERC-registered entity status
• webCARES digital certificate

The GADS Wind application assigns each plant a unique identifier when the team imports its Plant Configuration template.

Accepted 2026 formats:

• Excel-format Extensible Markup Language (XML) templates
• Standalone XML files following the column order of the reporting templates

This is a change from the 2024 DRI, which accepted Excel templates or comma-separated values (CSV) files. If your team built automated CSV pipelines for earlier submissions, those pipelines need updating for 2026.

When to use EFOR for wind

Use the wind forced outage rate whenever you report generator availability to NERC or contribute to resource adequacy studies. Use the same metric when you benchmark plant performance against your fleet. Mandatory GADS-Wind reporting applies to every Generator Owner of a NERC-registered entity operating a wind plant that meets both criteria: Total Installed Capacity of 75 MW or greater, and a commercial operation date of January 1, 2005 or later. Category 2 Generator Owners have separate obligations effective May 2026 or later.

The regulatory basis is a NERC Rules of Procedure Section 1600 data request, effective January 1, 2024, approved by the NERC Board on November 16, 2022. Generator Owners must submit data quarterly, within 45 days after the end of each calendar quarter.

Submissions are due 45 days after the end of each calendar quarter.

The forced outage rate appears in several reliability workflows:

• Loss-of-load expectation studies, where planners model reliability under new resource mixes using GADS-Wind data
• NERC fleet benchmarking through the GADS Wind Availability Review Weighted Resource EFOR Dashboard, which presents the operative view of ongoing wind fleet performance
• NERC’s annual State of Reliability, where the weighted forced outage rate serves as a cross-fuel reliability figure informing planning reserve margins

As that rate rises, NERC notes that planning reserve margins may need to increase to address uncertainty.

Common issues and pitfalls

Most wind EFOR errors come from classification, especially curtailment and derate coding. The turbine-hour states in GADS-Wind draw sharp lines between forced outages, curtailments, and resource conditions, and misplacing hours across those lines inflates or understates the metric before any formula runs. The error starts when teams code event data at the point of capture.

Forced outages vs. forced de-rates vs. curtailments

Only forced outage events count toward the wind forced outage rate, and NERC draws the boundary explicitly. A reportable forced outage begins with a loss of at least 20 MW of Plant Total Installed Capacity due to a forced event, and it ends when 95% of the unavailable capacity returns to service and less than 20 MW remains unavailable. Those hours become Forced Turbine-Hours.

NERC states plainly that reductions from reserve shutdown, planned outages, and maintenance outages are not part of forced outages. The states and their treatment break down as follows:

Curtailments are the highest-stakes line to get right. The 2025 DRI clarified that all curtailments are considered reserve shutdown hours, and this applies whether the curtailment is operator-directed or grid-operator-directed. Reserve Shutdown covers turbine-hours off-line for economic reasons but available for service. Grid-operator curtailments are excluded from forced outage accounting entirely. When a plant reports curtailment hours as forced outages, it overstates FTH and artificially inflates the reported forced outage rate, which then distorts fleet-level figures in the State of Reliability.

Forced de-rates sit in a separate category. A forced derating is a partial capacity reduction where the turbine remains in service at reduced output, distinct from a full forced outage that removes the unit entirely. In the wind framework, derate reporting is voluntary. NERC removed derate references from the 2024 wind DRI because the term “was not analogous to conventional” generation reporting. An operator running a turbine at 80% output because of ice accumulation should not report that as a forced outage. A turbine that shuts down completely from blade imbalance caused by the same ice is reportable.

Common causes of forced outages in wind facilities

Wind forced outages cluster around component and electrical failure modes, and NERC GADS-Wind collects a primary cause code for each event with additional causes recorded separately. NREL reliability studies identify the gearbox, generator, shaft and bearings, structure, and blades and hub as the largest contributors to downtime per failure. By frequency, electrical systems fail most often, followed by blades and hub, control or hydraulic systems, the gearbox, and the generator.

Gearbox failures carry an average annual rate near 2.5%, most traced to bearings, and onshore turbines average 1.729 failures per MW per year against 1.088 offshore.

The failure mode most specific to wind as an inverter-based resource (IBR) is ride-through behavior during grid disturbances. NERC has documented root causes through Level 2 Alerts and disturbance reports:

• Protection settings near PRC-024 limits: Inverter- and plant-level protection set with trip settings directly on or near the NERC PRC-024 curve, not based on established equipment capability.
• Instantaneous protection: Voltage and frequency protection using instantaneous measurements with no time delay, causing erroneous trips during sub-cycle disturbances.
• Firmware update reversions: IBRs that improved their fault-ride-through settings, then reverted to prior settings during a firmware update.
• Underutilized ride-through capability: Fewer than one-third of reported inverter settings are based on equipment capability, leaving significant ride-through headroom unused across the bulk power system.

NERC has identified approximately 5,200 MW of bulk electric system IBRs with protection settings inside the PRC-024 no-trip zone. These trips register as forced outages when the plant is removed from service, so the settings themselves become a direct lever on the wind forced outage rate.

Types and variations

The wind reliability metric has several variants, and using the wrong one in a compliance or planning context produces figures that are technically correct but wrong for the purpose. The most common compliance distinction is the Weighted Resource EFOR view. Planning teams also encounter the demand-weighted EFORd and the offshore-specific EFOR methodology used in New York.

WEFOR (Weighted Equivalent Forced Outage Rate)

NERC’s general WEFOR acronym means Weighted Equivalent Forced Outage Rate. NERC defines WEFOR as an equation used throughout the electric industry to assess generator reliability. It measures how much of a unit’s time and generating capacity is reduced by forced outages and derates relative to the time it could be generating, weighted by net maximum capacity. In the wind dashboard context, NERC presents a Weighted Resource EFOR view built from GADS-Wind turbine-hour reporting. Do not treat that wind metric as the conventional Appendix F EFOR calculation.

The structural distinction from standard EFOR is the NMC multiplier. Standard EFOR sums raw hour components and treats every unit equally regardless of size. WEFOR multiplies each term in both numerator and denominator by NMC before summing across units. NERC states that this weighting gives larger units more impact and measures the probability that a group of units will not meet generating requirements because of forced outages or forced derates.

For wind, capacity weighting matters more than for thermal fleets. Wind plant maximum capacity is always changing with atmospheric conditions, so a raw unweighted average across turbines of very different sizes would distort the fleet picture. NMC weighting is why the Weighted Resource EFOR view is NERC’s operative wind fleet metric and the figure shown on the GADS Wind Availability Review Dashboard.

EFOR vs. EFORd for wind

EFORd is the demand-weighted variant of EFOR, and the NERC GADS-Wind framework does not apply it to wind units. For thermal units, EFORd restricts exposure to periods when the unit is demanded to run. Its denominator contains only service hours plus demand-weighted forced outage hours, which makes EFORd generally higher than EFOR for the same unit because reserve shutdown periods drop out of the denominator. The demand-weighting depends on a factor f applied to forced outage hours.

The GADS-Wind DRI does not define EFORd or the demand-weighting factors for wind units. The conventional EFORd methodology exists only for conventional units in Appendix F. This is the common reporting error: treating a wind class average EFORd from a market context as if the GADS-Wind standard computes EFORd at the plant level. It does not. The New York Independent System Operator’s (NYISO) capacity accreditation framework does reference the 1-year NERC class average EFORd value for resources of the same type when setting initial unforced capacity (UCAP) for new resources, so EFORd appears in wind market accreditation even though NERC GADS-Wind does not calculate it per plant. Keep those two contexts separate in your filings.

Onshore vs. offshore wind EFOR

Offshore wind EFOR follows a peak-period methodology under the New York Department of Public Service (NY DPS) that differs from the onshore turbine-hour approach. NY DPS defines EFOR for offshore wind as the weighted probability that the resource is not available when it is needed, calculated as the average of per-unit unserved energy across the peak-period hours in the peak season.

The methodology has three key boundaries:

• Season: May through September.
• Hours: For wind analyzed without storage, 2 p.m. to 9 p.m. to match the South Fork area load curve.
• Input data: Back-casted capacity profiles that use a historical year’s meteorological record to estimate hourly turbine output for the unserved-energy calculation.

Two framework points affect how you use these figures. Effective May 1, 2024, NYISO adopted Capacity Accreditation Rules that superseded the prior EFOR-based approach for accreditation. And under NERC GADS-Wind, NERC excludes energy storage capacity from wind plant metrics: Total Installed Capacity is the combined subgroup capacity not including energy storage, and operators report storage performance separately. There is no single combined EFOR in NERC GADS that merges wind and co-located battery performance into one facility value.

Wind EFOR benchmarks vs. coal, gas, and nuclear

Wind’s forced outage rate runs substantially higher than conventional fuels, but the comparison carries a structural caveat that changes how you should read it. NERC’s most recent State of Reliability, published June 24, 2026 covering 2025 data, reports weighted forced outage rates for conventional fuels. NERC did not list a wind figure in the 2026 report; the most recent wind number comes from the 2024 State of Reliability covering 2023 data.

The published figures are:

The wind figure rose from 18.1% in 2022 to 18.9% in 2023. Before you treat wind as three times less reliable than coal, account for the reporting difference. Wind’s metric is FTH-based and does not equivalize partial deratings. The conventional WEFOR incorporates EFDH, which converts partial capacity losses into equivalent outage hours. Wind and conventional figures use comparable but not identical weighting methodologies, so the gap partly reflects the wind-specific framework rather than a pure reliability difference. Unit-level EFOR, EFORd, and availability factors by fuel type appear in NERC’s Generating Unit Statistical Brochures, most recently the 2022 series.

Reducing wind EFOR

The direct levers on wind forced outage rate fall into two categories. First, predictive maintenance and condition monitoring address the failure modes that generate reportable FTH. Second, IBR protection settings create a software and controls lever.

Baseline turbine availability sits around 95% to 97%, with an industry range of 93% to 99%. Moving within that band depends on catching component failures before they force a unit off-line.

Maintenance teams gain lead time from condition monitoring. Vibration-based condition monitoring systems detected a gearbox anomaly several months in advance in one study, where supervisory control and data acquisition (SCADA)-only detection of the same fault gave roughly one week of warning. Digital-twin maintenance optimization has shown a 20% to 30% reduction in downtime.

The IBR software lever is distinct from mechanical maintenance. Because fewer than one-third of reported inverter settings are based on equipment capability, revising protection settings and firmware to use the available ride-through headroom prevents trips that would otherwise register as forced outages. This work depends on settings and firmware discipline, which makes it one of the lower-cost levers available.

Every reportable forced outage affects two numbers: lost generation revenue and the FTH total submitted to NERC. Classification errors sit upstream of both. When teams capture forced events accurately at the point they occur, the metric reflects real reliability and the maintenance program can target the failure modes that actually drive it.

Frequently asked questions (FAQ)

How do you calculate wind EFOR step by step under GADS?

Start with Forced Turbine-Hours, the sum of turbine-hours off-line due to forced events requiring repair before the next Sunday at 23:59. A forced event is reportable only when it removes at least 20 MW of Plant Total Installed Capacity, and it ends when 95% of that capacity returns and less than 20 MW remains unavailable. The fleet-level Weighted Resource EFOR view weights FTH against generating-capable hours by each plant’s net maximum capacity. Confirm the exact current equation against Appendix M of the 2026 GADS-Wind DRI before building a calculation, because NERC removed the equivalent-derate terms in January 2024.

How does wind EFOR differ from thermal EFOR?

Thermal EFOR converts partial capacity reductions into Equivalent Forced Derated Hours and includes them in the calculation. The wind framework removed that equivalent-derate concept in the 2024 DRI, so wind reports discrete forced outage states instead of equivalized deratings. Derate reporting is voluntary for wind. The result is that wind uses an FTH-based forced outage rate rather than the conventional EFOR formula.

When should I use WEFOR for wind?

Use the wind Weighted Resource EFOR view whenever you report or benchmark at the fleet level, because it weights each plant by net maximum capacity so larger plants carry proportionate influence. NERC uses that wind fleet view in the State of Reliability and on the GADS Wind Availability Review Weighted Resource EFOR Dashboard.

How do I treat curtailments and de-rates?

Classify all curtailments as Reserve Shutdown Turbine-Hours, whether operator-directed or grid-operator-directed, per the 2025 DRI clarification. They do not count toward the forced outage rate. Treat forced de-rates as voluntary reporting only, and never report a turbine running at reduced output as a full forced outage.

Is EFORd used for wind?

Not in the NERC GADS-Wind framework. EFORd is a demand-weighted thermal variant defined only for conventional units in Appendix F. NYISO’s capacity accreditation does reference a NERC class average EFORd value for new resources of the same type, so EFORd appears in wind market accreditation even though NERC GADS-Wind does not compute it at the plant level.

How PowerGADS automates GADS event capture

Equivalent availability factor and forced outage rate share the same underlying problem: both depend on turbine-hour states that teams often code manually across disconnected systems. That is where transcription errors originate. The same event gets keyed more than once, and the misclassification surfaces later as curtailment hours in FTH or a forced outage rate that no longer reflects the plant.

PowerGADS connects directly to your PI historian and SCADA systems, captures unit events in real time, runs 200+ built-in validations against reporting rules, and generates NERC GADS submissions with a full audit trail. The claimed outcome is an 80% reduction in GADS compliance workload. Most teams are live in under four weeks.