A turbine can be ready almost all year and still produce modest energy when wind is weak or output is curtailed. It can also lose one windy day whose energy impact is much larger than its share of calendar time.
This guide follows one fictional 2 MW turbine through capacity-hours, operating states, curtailment, missing data, partial derating and expected energy.
The figures teach metric boundaries. They are not a benchmark, asset valuation or performance guarantee.
The practical habit is to preserve a small evidence receipt beside every answer. It names the object, reference condition, units, observation method, transformation and the nearest tempting claim that still does not follow.
Each changed-context check alters one consequential condition while keeping the remaining basis fixed. This makes transfer visible: the reader can predict which field should change, which should remain stable and what new evidence would be required.
The article uses five routes so readers can enter by task, but the mechanism is cumulative. Definitions establish the objects, the worked case carries the arithmetic, evidence checks test rivals, transfer cases change the context and the final route repairs common shortcuts.
A useful comparison begins with a ledger rather than a conclusion. Put the two candidate quantities in separate columns, write the numerator, denominator, reference condition and observation method for each, and leave an explicit blank when a field is unknown. Then carry one fictional record from raw observations to the narrow result. This prevents a familiar percentage, label or instrument display from borrowing certainty from a different calculation. It also makes later correction cheap: one field can change without rewriting the evidence history or silently moving the boundary of the claim.
The examples deliberately include a near-boundary case, a changed denominator and a changed physical or operational condition. These are not decorative variations. They reveal whether the reader has learned the mechanism or only memorised the first arithmetic. Before accepting a conclusion, predict the direction of change, calculate it, and explain any disagreement between prediction and result. When the answer depends on a standard, contract, laboratory method or browser rule, preserve the exact version and keep the general teaching principle separate from the local decision.
For practical use, keep three layers visible: what was directly observed, what was calculated from those observations, and what action or interpretation is being proposed. Evidence can support the first two layers without automatically justifying the third. A good report therefore states the nearest rival explanation, one check that would distinguish it, and one limit that remains after the check. This structure keeps the writing warm and readable while giving another person enough information to repeat the reasoning, challenge an assumption and transfer the method to a new case.
Before leaving the worked route, perform a reconciliation check. Confirm that units cancel as expected, totals and time intervals close, every derived value points back to a stored input, and every linked article answers a materially different question. Then read the conclusion without the surrounding explanation. If it could be mistaken for a universal rule, add the missing condition directly to the sentence. This last pass catches many errors that arithmetic alone cannot reveal: a shifted reference, a hidden exclusion, an unmatched specimen, an unvalidated conversion or a metric used outside the range in which it was defined.
This specialist guide belongs to the Wind Energy root. It also connects to The Gold Standard of Education | Learning That Transfers into Life and the How X Works hub. The worked cases are original teaching examples; their numbers are stipulated so that the reasoning can be checked.
eduKateSG · Wind Energy
Find your next learning step
Read the short answer first: capacity factor divides actual energy by rated-capacity hours; technical availability measures capability under a declared state and exclusion rule. They share a period, but they do not share a numerator.
ROUTE 1 · CHAPTERS 1–4
Define the quantities
Name the quantities, reference conditions and reporting rules.
ROUTE 3 · CHAPTERS 9–12
Audit the evidence
Check instruments, algorithms, assumptions and rival explanations.
ROUTE 5 · CHAPTERS 17–20
Report and continue
Repair shortcuts, answer questions and follow verified routes.
Chapter contents
Define the quantities · Chapters 1–4
1. Name the two performance ratios
2. Write the capacity-factor denominator
Work the mechanism · Chapters 5–8
5. Work the central annual ledger
Audit the evidence · Chapters 9–12
9. Audit rated capacity changes
Transfer the reasoning · Chapters 13–16
13. Transfer to a calm but healthy month
14. Transfer to a windy outage
Report and continue · Chapters 17–20
17. Repair high availability means high output
18. Write the supported annual conclusion
Capacity factor compares actual energy over a period with the energy possible at rated power throughout that period. Technical availability measures whether the turbine was capable of operating under the declared availability rule.
Write the evidence in the order a reader can audit: the Wind Energy quantity, its reference object, the observation or browser rule, the transformation, and the decision being made. Keeping those fields visible prevents a familiar label from hiding a changed basis.
A 2 MW turbine produces 5,256 MWh in a 365-day year. Its capacity factor is 5,256/(2×8,760)=0.30.
First-principles test: ask what physical, observational or algorithmic operation produces each value in this chapter. Then ask whether the second value could change while the first stays fixed. If it can, the two labels are not substitutes. For Wind Energy, this counterfactual is often clearer than a definition learned in isolation.
Keep energy fixed but change rated power to 2.5 MW. Capacity factor falls even though availability has not been recalculated.
Evidence check: another reader should be able to reproduce the narrow result from the stored definitions, inputs and intermediate steps, then identify the nearest stronger claim that the evidence does not support.
Availability definitions differ by contract, fleet and reporting standard.
The denominator is rated capacity multiplied by all hours in the reporting period, not only windy hours or available hours. Removing low-wind hours changes the metric.
Trace the mechanism before interpreting the result. For Wind Energy, mark which value belongs to the source, which belongs to the measurement or layout algorithm, and which is a reported summary. A calculation is useful only when those roles remain attached.
Use 2 MW×8,760 h=17,520 MWh as the annual theoretical maximum and divide 5,256 MWh by it.
Practical transfer: build two records that share the headline number but differ in the condition discussed here. If the correct interpretation changes, the omitted condition is decision-relevant and belongs in the report. This test turns a vocabulary distinction into a reusable Wind Energy checking habit.
Use a leap year with 8,784 h and show the small denominator change.
Practical check: keep one counterexample beside the worked case. If the wording fails when that one condition changes, narrow the sentence until it describes only the evidence actually in hand.
Partial periods need exact calendar boundaries and capacity changes.
A simple time-based teaching definition divides capable time by total scheduled time after declared exclusions. It does not use generated energy in the numerator.
Use a compact decision table with columns for condition, input, operation, result and limit. This makes the comparison reproducible and exposes where a missing field would force an assumption instead of an observation.
The turbine is technically capable for 8,322 of 8,760 h, giving 95.0% under the stipulated no-exclusion rule.
Misconception check: a plausible output does not prove the right reference, denominator, ancestor, spectrum or observation rule was used. Reconstruct one intermediate step and one changed-context prediction. If either cannot be stated, keep the result provisional rather than strengthening its wording.
Exclude 100 h of grid-directed shutdown from both numerator logic and denominator under a different contract; report the changed definition beside the result.
Transfer check: repeat the reasoning with one consequential condition changed while holding the rest fixed. State what changes, what stays comparable and why the original label alone was insufficient.
Do not compare availability values from incompatible exclusion rules.
CHAPTER 4 OF 20 · Define the quantities
4. Keep “available” separate from “generating”
A turbine may be available but generate nothing because wind is below cut-in, above cut-out, or curtailed externally. Conversely, energy output cannot prove continuous availability.
Preserve the raw inputs beside the derived result. If a later reader changes one condition, the original Wind Energy reasoning should still be recoverable without reverse-engineering a rounded headline or an unlabeled screenshot.
For 300 calm hours, the turbine is ready to run but wind is below cut-in. Those hours reduce capacity factor while remaining technically available.
Evidence design: retain both a positive case and a near-miss. The positive case shows when the rule applies; the near-miss changes one consequential condition and shows when the conclusion fails. Together they teach the boundary of the Wind Energy mechanism better than another unlabelled example.
Turn the same 300 hours into an internal gearbox outage. Capacity factor can stay zero in both cases while availability changes.
Audit check: retain the source version, units, settings, exclusions and rounding rule. A future correction should be able to alter one field without rebuilding the entire explanation from memory.
Operational data need state codes that separate environmental and technical causes.
The central case has 8,760 h, 438 h of internal unavailability, 300 h below cut-in, 120 h curtailment and 5,256 MWh output. Capacity factor is 30%; simple technical availability is 95%.
Ask what would have to stay fixed for the comparison to be fair. Record those controls explicitly, then name the first uncontrolled condition that could reverse the conclusion. This is the practical transfer step, not an optional footnote.
Keep every hour in one mutually exclusive state ledger and reconcile the energy meter separately.
Communication test: replace any sentence that says two things are “the same” or “different” with a sentence naming the operation, reference condition and supported consequence. The extra words are useful when they let a future reader repeat the decision without access to the original author.
Move 100 h from calm-but-ready to internal outage with the same zero energy. Capacity factor stays 30% while availability falls.
Decision check: end with an action or interpretation that follows from the stated conditions, followed by a boundary sentence explaining when a specialist rule, local procedure or additional measurement is needed.
Real state histories overlap and require priority rules.
CHAPTER 6 OF 20 · Work the mechanism
6. Separate time availability from energy availability
Time-based availability weights every hour equally. Energy-based availability weights lost production by the energy that could have been produced, so an outage in strong wind matters more than an outage in calm conditions.
Write the evidence in the order a reader can audit: the Wind Energy quantity, its reference object, the observation or browser rule, the transformation, and the decision being made. Keeping those fields visible prevents a familiar label from hiding a changed basis.
Two 10 h outages have equal time loss; one coincides with 1.8 MW expected power and the other with 0.1 MW. Their energy losses differ sharply.
First-principles test: ask what physical, observational or algorithmic operation produces each value in this chapter. Then ask whether the second value could change while the first stays fixed. If it can, the two labels are not substitutes. For Wind Energy, this counterfactual is often clearer than a definition learned in isolation.
Swap the wind conditions between outages. Time availability stays fixed while energy-based availability changes.
Evidence check: another reader should be able to reproduce the narrow result from the stored definitions, inputs and intermediate steps, then identify the nearest stronger claim that the evidence does not support.
Expected-energy models introduce uncertainty from wind and power-curve estimation.
A turbine can be technically operating yet capped below rated power. A binary time-availability flag may miss the loss; a capacity-weighted or energy method can represent it.
Trace the mechanism before interpreting the result. For Wind Energy, mark which value belongs to the source, which belongs to the measurement or layout algorithm, and which is a reported summary. A calculation is useful only when those roles remain attached.
Operate 100 h at a 1 MW cap on a 2 MW turbine. A simple uptime measure counts all 100 h as available.
Practical transfer: build two records that share the headline number but differ in the condition discussed here. If the correct interpretation changes, the omitted condition is decision-relevant and belongs in the report. This test turns a vocabulary distinction into a reusable Wind Energy checking habit.
Raise the cap to 1.5 MW. Uptime is unchanged while potential energy loss narrows.
Practical check: keep one counterexample beside the worked case. If the wording fails when that one condition changes, narrow the sentence until it describes only the evidence actually in hand.
Contractual availability may specify how derates are counted.
Curtailment can arise from grid, noise, wildlife or market instructions. Whether it is excluded from an availability guarantee does not make its lost energy disappear from capacity factor.
Use a compact decision table with columns for condition, input, operation, result and limit. This makes the comparison reproducible and exposes where a missing field would force an assumption instead of an observation.
The turbine is healthy during 120 curtailed hours, so simple technical availability remains high while actual annual energy falls.
Misconception check: a plausible output does not prove the right reference, denominator, ancestor, spectrum or observation rule was used. Reconstruct one intermediate step and one changed-context prediction. If either cannot be stated, keep the result provisional rather than strengthening its wording.
Reclassify the same hours as an internal control fault. Capacity factor is unchanged and technical availability falls.
Transfer check: repeat the reasoning with one consequential condition changed while holding the rest fixed. State what changes, what stays comparable and why the original label alone was insufficient.
Cause codes and exclusion rights need traceable evidence.
Repowering, uprating or a midyear capacity change makes one fixed denominator misleading. Split the period and sum capacity-hours.
Preserve the raw inputs beside the derived result. If a later reader changes one condition, the original Wind Energy reasoning should still be recoverable without reverse-engineering a rounded headline or an unlabeled screenshot.
Operate 1 MW for 4,380 h and 2 MW for 4,380 h, giving 13,140 MWh of capacity-hours before dividing actual energy.
Evidence design: retain both a positive case and a near-miss. The positive case shows when the rule applies; the near-miss changes one consequential condition and shows when the conclusion fails. Together they teach the boundary of the Wind Energy mechanism better than another unlabelled example.
Pretend the full year used 2 MW and observe the denominator inflation.
Audit check: retain the source version, units, settings, exclusions and rounding rule. A future correction should be able to alter one field without rebuilding the entire explanation from memory.
Nameplate, grid limit and commercial capacity can differ.
Gross generator energy, auxiliary consumption and net export are different quantities. Capacity factor should name which energy and capacity boundary it uses.
Ask what would have to stay fixed for the comparison to be fair. Record those controls explicitly, then name the first uncontrolled condition that could reverse the conclusion. This is the practical transfer step, not an optional footnote.
A turbine generates 5,256 MWh gross, uses 70 MWh auxiliaries and exports 5,186 MWh net.
Communication test: replace any sentence that says two things are “the same” or “different” with a sentence naming the operation, reference condition and supported consequence. The extra words are useful when they let a future reader repeat the decision without access to the original author.
Hold turbine operation fixed and increase substation auxiliary use. Net capacity factor changes while technical availability does not.
Decision check: end with an action or interpretation that follows from the stated conditions, followed by a boundary sentence explaining when a specialist rule, local procedure or additional measurement is needed.
Meter accuracy and loss allocation require their own checks.
Maintenance, low wind and curtailment can overlap. A state hierarchy prevents the same hour from being counted twice or assigned to the most convenient cause.
Write the evidence in the order a reader can audit: the Wind Energy quantity, its reference object, the observation or browser rule, the transformation, and the decision being made. Keeping those fields visible prevents a familiar label from hiding a changed basis.
During a 2 h repair, wind is below cut-in for 30 min. Apply the declared precedence and retain both raw conditions.
First-principles test: ask what physical, observational or algorithmic operation produces each value in this chapter. Then ask whether the second value could change while the first stays fixed. If it can, the two labels are not substitutes. For Wind Energy, this counterfactual is often clearer than a definition learned in isolation.
Reverse the precedence and show how cause totals move while total calendar hours remain fixed.
Evidence check: another reader should be able to reproduce the narrow result from the stored definitions, inputs and intermediate steps, then identify the nearest stronger claim that the evidence does not support.
A hierarchy is an accounting rule, not a causal discovery method.
Missing records are not automatically downtime or uptime. Reconstruct from independent meters, event logs and neighbouring signals, and retain an unknown category when evidence is insufficient.
Trace the mechanism before interpreting the result. For Wind Energy, mark which value belongs to the source, which belongs to the measurement or layout algorithm, and which is a reported summary. A calculation is useful only when those roles remain attached.
A 6 h communication gap has continuous export-meter data at expected power, supporting operation but not every internal status.
Practical transfer: build two records that share the headline number but differ in the condition discussed here. If the correct interpretation changes, the omitted condition is decision-relevant and belongs in the report. This test turns a vocabulary distinction into a reusable Wind Energy checking habit.
Remove the export data. The same gap becomes less classifiable and uncertainty grows.
Practical check: keep one counterexample beside the worked case. If the wording fails when that one condition changes, narrow the sentence until it describes only the evidence actually in hand.
Imputation should not manufacture precision.
A low-wind month can show high technical availability and low capacity factor. This is expected when the machine is ready but the resource is weak.
Use a compact decision table with columns for condition, input, operation, result and limit. This makes the comparison reproducible and exposes where a missing field would force an assumption instead of an observation.
The turbine is available 99% of March but produces only 18% of rated capacity-hours.
Misconception check: a plausible output does not prove the right reference, denominator, ancestor, spectrum or observation rule was used. Reconstruct one intermediate step and one changed-context prediction. If either cannot be stated, keep the result provisional rather than strengthening its wording.
Replace calm conditions with strong wind while preserving availability. Capacity factor rises.
Transfer check: repeat the reasoning with one consequential condition changed while holding the rest fixed. State what changes, what stays comparable and why the original label alone was insufficient.
Resource comparisons need long-term and site-specific wind context.
An outage during strong wind can reduce both metrics, but by different mechanisms: unavailable hours lower availability and lost energy lowers capacity factor.
Preserve the raw inputs beside the derived result. If a later reader changes one condition, the original Wind Energy reasoning should still be recoverable without reverse-engineering a rounded headline or an unlabeled screenshot.
A 24 h gearbox outage occurs at an expected 1.7 MW. Record 24 unavailable hours and 40.8 MWh expected loss separately.
Evidence design: retain both a positive case and a near-miss. The positive case shows when the rule applies; the near-miss changes one consequential condition and shows when the conclusion fails. Together they teach the boundary of the Wind Energy mechanism better than another unlabelled example.
Move the outage to a calm interval. Time availability is unchanged while energy impact shrinks.
Audit check: retain the source version, units, settings, exclusions and rounding rule. A future correction should be able to alter one field without rebuilding the entire explanation from memory.
Expected power is modelled rather than directly observed during the outage.
A fleet average can be capacity-weighted, turbine-weighted or energy-weighted. A simple average of percentages can overrepresent small machines.
Ask what would have to stay fixed for the comparison to be fair. Record those controls explicitly, then name the first uncontrolled condition that could reverse the conclusion. This is the practical transfer step, not an optional footnote.
Combine a 1 MW turbine at 90% availability and a 4 MW turbine at 98%; capacity-weighted availability is 96.4%.
Communication test: replace any sentence that says two things are “the same” or “different” with a sentence naming the operation, reference condition and supported consequence. The extra words are useful when they let a future reader repeat the decision without access to the original author.
Swap their capacities while retaining percentages. The weighted fleet result changes.
Decision check: end with an action or interpretation that follows from the stated conditions, followed by a boundary sentence explaining when a specialist rule, local procedure or additional measurement is needed.
Fleet rules must treat overlapping periods and changing capacity consistently.
CHAPTER 16 OF 20 · Transfer the reasoning
16. Keep uncertainty beside expected energy
Capacity factor from calibrated meters is largely observed; energy-based availability relies on counterfactual expected output. Wind measurements, wakes, icing and power-curve error widen that estimate.
Write the evidence in the order a reader can audit: the Wind Energy quantity, its reference object, the observation or browser rule, the transformation, and the decision being made. Keeping those fields visible prevents a familiar label from hiding a changed basis.
Report a lost-energy estimate of 40.8 MWh with a stated range rather than a single exact value.
First-principles test: ask what physical, observational or algorithmic operation produces each value in this chapter. Then ask whether the second value could change while the first stays fixed. If it can, the two labels are not substitutes. For Wind Energy, this counterfactual is often clearer than a definition learned in isolation.
Widen wind-speed uncertainty and show how the expected-loss range responds.
Evidence check: another reader should be able to reproduce the narrow result from the stored definitions, inputs and intermediate steps, then identify the nearest stronger claim that the evidence does not support.
A narrow arithmetic result is not proof of a narrow physical uncertainty.
CHAPTER 17 OF 20 · Report and continue
17. Repair high availability means high output
High availability says the asset was capable under a rule. It does not guarantee strong wind, no curtailment or high capacity factor.
Trace the mechanism before interpreting the result. For Wind Energy, mark which value belongs to the source, which belongs to the measurement or layout algorithm, and which is a reported summary. A calculation is useful only when those roles remain attached.
Rewrite “98% available, therefore excellent production” as two separate claims with energy evidence for the second.
Practical transfer: build two records that share the headline number but differ in the condition discussed here. If the correct interpretation changes, the omitted condition is decision-relevant and belongs in the report. This test turns a vocabulary distinction into a reusable Wind Energy checking habit.
Hold availability at 98% across two sites with different wind resources and compare output.
Practical check: keep one counterexample beside the worked case. If the wording fails when that one condition changes, narrow the sentence until it describes only the evidence actually in hand.
Business performance also depends on price, losses, costs and reliability consequences.
A strong conclusion names the period, capacity-hours, energy boundary, capacity factor, availability definition, exclusions, unknown states and major loss categories.
Use a compact decision table with columns for condition, input, operation, result and limit. This makes the comparison reproducible and exposes where a missing field would force an assumption instead of an observation.
Write: “The fictional 2 MW turbine achieved 30% gross capacity factor and 95% time-based technical availability under the stated no-exclusion rule.”
Misconception check: a plausible output does not prove the right reference, denominator, ancestor, spectrum or observation rule was used. Reconstruct one intermediate step and one changed-context prediction. If either cannot be stated, keep the result provisional rather than strengthening its wording.
Ask a second reader to recompute both ratios from the ledger without inferred fields.
Transfer check: repeat the reasoning with one consequential condition changed while holding the rest fixed. State what changes, what stays comparable and why the original label alone was insufficient.
The example is not a benchmark for a real wind farm.
Reconcile SCADA states to meter energy, maintenance tickets, curtailment commands, clock quality and capacity changes before publishing ratios.
Preserve the raw inputs beside the derived result. If a later reader changes one condition, the original Wind Energy reasoning should still be recoverable without reverse-engineering a rounded headline or an unlabeled screenshot.
Find a 12 h “available” code with zero wind-independent auxiliary signatures and flag it for review.
Evidence design: retain both a positive case and a near-miss. The positive case shows when the rule applies; the near-miss changes one consequential condition and shows when the conclusion fails. Together they teach the boundary of the Wind Energy mechanism better than another unlabelled example.
Correct the state code while preserving the original audit trail.
Audit check: retain the source version, units, settings, exclusions and rounding rule. A future correction should be able to alter one field without rebuilding the entire explanation from memory.
Operational safety and maintenance decisions belong to qualified teams.
Power-curve averaging explains why average wind speed cannot be inserted into a nonlinear curve; missing-interval bounds handle incomplete generation records; aerodynamic versus generator output separates energy boundaries.
Ask what would have to stay fixed for the comparison to be fair. Record those controls explicitly, then name the first uncontrolled condition that could reverse the conclusion. This is the practical transfer step, not an optional footnote.
Place resource, machine state and meter output in three linked ledgers.
Communication test: replace any sentence that says two things are “the same” or “different” with a sentence naming the operation, reference condition and supported consequence. The extra words are useful when they let a future reader repeat the decision without access to the original author.
Change the question from annual utilisation to missing-data recovery and select the relevant sibling.
Decision check: end with an action or interpretation that follows from the stated conditions, followed by a boundary sentence explaining when a specialist rule, local procedure or additional measurement is needed.
The neighbouring owners should remain distinct.
Continue through the verified reading route
Apply the power curve before averaging wind speeds
Apply the power curve before averaging wind speeds. Use this when nonlinear resource conversion affects expected energy.
Bound generation with missing intervals
Bound generation with missing intervals. Use this when incomplete meter or SCADA intervals must remain visible.
Aerodynamic input and generator output
Aerodynamic input and generator output. Use this when efficiency and loss boundaries separate resource power from electrical output.
Frequently asked questions
Can a turbine have high availability and low capacity factor?
Yes. It can be ready during weak wind or external curtailment.
Does zero generation prove an outage?
No. Wind, curtailment, grid state and meter boundaries must be checked.
Should fleet percentages be averaged directly?
Only after choosing a justified weighting and common definition.
Authoritative sources and further reading
US Department of Energy Small Wind Guidebook. The official guidebook explains capacity factor and availability as distinct influences on wind-system production.
US EIA capacity factor glossary. The official glossary defines capacity factor as actual output relative to possible full-capacity output over a period.
US EIA capacity and generation FAQ. The official FAQ explains why nameplate capacity and actual generation answer different questions.
Return to the Wind Energy subject guide, The Gold Standard of Education, or the How X Works hub.