Wind turbine
Bulk fluid flowAerodynamic and hydrodynamic liftMechanical motionRotating-machine generator actionCharge carriersElectrical work
Blade lift turns the rotor; the rotor turns the generator.
Epistemic state of the route
- known constituent relations
- 5 / 5 established or replicated · weakest constituent established
- constituent maturity floor
- K4 · experimentally observed
- search for this exact route
- A recorded pathway or a reviewed search records a demonstration of this composition.
- recorded pathway
- Wind turbine · commercial
- composition maturity
- K8 · commercial technology — Wind turbine
- recorded-pathway overlap
- this route is the recorded pathway Wind turbine
- route-level evidence
- 3 sources for the complete composition · 5 cited by the constituent steps
- boundaries and interfaces
- BOUNDARY compatible · no region transition
Explorematrix context · physics checks · performance · steps · route evidence · constituent evidence · cite
Matrix context
D = disequilibrium row · C = coupling family column. A cell reads the state of the atlas for that pair.
D.10 × C.24 · Bulk fluid flow × Turbomachineryfamily: TurbomachineryD.10 × C.14 · Bulk fluid flow × Electromagnetic inductionfamily: Electromagnetic induction
Measured or reported performance
- peak rotor power coefficient≈ 0.45field2005Southwest Windpower Storm pre-prototype, a three-blade downwind variable-speed stall-regulated turbine rated 1.8 kW; deduced from field-test measured electrical power and dynamometer-measured alternator efficiency; a broad, flat curve near C_p ≈ 0.43 over a 4 m/s wind-speed range; preliminary, with definitive NWTC tests under way at the time — the atlas had carried 0.52 as an efficiency_record until pass 39 — the wrong quantity for a pathway that ends in electrical work; this is the rotor's coefficient, comparable with the Betz limit and nothing elserefs [6]
Typed bounds on this route
Every limit the atlas holds for this route, as constraint records: reached through bounded_by claims on the route's own entities. Hard bounds (an upper bound or a formula) decide the thermodynamic-bound check above; benchmarks, constitutive relations and resource limits are listed and never decisive. No prose limit exists anywhere (pass 42).
- Betz limit · upper-bound · hard, applies to this routeC_p ≤ 16/27 ≈ 59.3% of the kinetic power through the rotor disc
Steps
- 01kinetic → mechanical · loss to thermal
- a rotor whose blades meet the stream at a working angle of attack
bulk flow requiredrefs [1] [2] - 02mechanical → mechanicalrefs [2]
- 03mechanical → electrical · loss to thermal
- a shaft turning a rotor inside a stator, or a magnet moved past a coil
conductor required · magnetic field requiredrefs [3] [2] - 04electrical → electrical · loss to thermalrefs [3] [4]
- 05electrical → electrical · loss to thermal
- carriers driven through an external load at the potential difference the source maintains
refs [5]
Evidence for the complete composition · 3
- [1]A. Betz. Das Maximum der theoretisch möglichen Ausnützung des Windes durch Windmotoren (1920)
- [2]S. L. Dixon, C. A. Hall. Fluid Mechanics and Thermodynamics of Turbomachinery (7th ed.) (2014)
- [6]P. Migliore et al.. Balancing Performance, Noise, Cost, and Aesthetics in the Southwest Windpower 'Storm' Wind Turbine: Preprint (2005)
Evidence for the constituent relations · 5
- [1]A. Betz. Das Maximum der theoretisch möglichen Ausnützung des Windes durch Windmotoren (1920)
- [2]S. L. Dixon, C. A. Hall. Fluid Mechanics and Thermodynamics of Turbomachinery (7th ed.) (2014)
- [3]M. Faraday. Experimental researches in electricity (1832)
- [4]L. D. Landau, E. M. Lifshitz, L. P. Pitaevskii. Electrodynamics of Continuous Media (Course of Theoretical Physics, Vol. 8, 2nd ed.) (1984)
- [5]N. W. Ashcroft, N. D. Mermin. Solid State Physics (1976)
Cite this route
Physical Transformation Atlas (2026). route p-5b96b456b1: Wind turbine. Dataset revision rbfbfcbb70e57 (hash of the canonical data). https://physical-transformation-atlas.wldud5192.workers.dev/path/5b96b456b1
Ids and matrix addresses are stable across revisions; the revision hash identifies the exact canonical files the record was compiled from and is meta.data_hash in every /api export. Reuse terms: see the license field in any export.