ASHTABULA WIND II LLC
OperatingWind power plant
- Capacity
- 120 MW
- Primary fuel
- Wind
- County
- Steele County
- Operator
- ASHTABULA WIND II LLC
- Status
- Operating
- Commissioned
- 2009
- EIA plant ID
- 57121
- Generators
- 1
- Technology
- Onshore Wind Turbine
- Net generation (2024)
- 328 GWh
- Capacity factor (2024, EIA nameplate)
- 31%
- Data vintage
- EIA-860 2024 final; EIA-923 2022-2024 final
- Coordinates
- 47.1284, -97.9043
ASHTABULA WIND II LLC, a 120 MW Wind power plant in Steele County, North Dakota. Operated by ASHTABULA WIND II LLC, commissioned 2009.
How ASHTABULA WIND II LLC compares
With 120 MW of capacity, ASHTABULA WIND II LLC ranks 11th among the 40 operating power plants Bywatts maps in North Dakota and 5th of the 21 operating Wind plants in the state. It accounts for about 7.0% of North Dakota's operating Wind capacity and 1.9% of all operating capacity in the state. Nationally it is the 184th-largest of the 708 operating Wind plants in the database. Commissioned in 2009, it is newer than 57% of the 40 operating North Dakota plants with a recorded commissioning year. It shares Steele County with one other operating plant, LUVERNE WIND FARM.
EIA-860 lists 1 generator at the site with 120 MW of nameplate capacity, all onshore wind turbine technology. Net generation was 328 GWh in 2024 (a 31% capacity factor), down 14% from 2022.
Grid neighborhood
The closest transmission line found within 10 miles is a 230 kV line owned by OTTER TAIL POWER CO, about 0.3 miles away. Another 4 operating power plants totaling 308 MW sit within 25 miles; the largest is FPL ENERGY ASHTABULA WIND LLC (149 MW, Wind).
Computed by Bywatts from HIFLD power plant and transmission line records and EIA-860/923 survey data; distances are straight-line. Sources and methodology
Weather peril exposure
ASHTABULA WIND II LLC is a 120 MW wind power plant in Steele County, ND, operated by ASHTABULA WIND II LLC, commissioned in 2009. Steele County carries critical modeled catastrophe exposure in the FEMA National Risk Index, scoring 4.4 of 5 at the 85th national percentile. Winter weather is the leading peril, rated Relatively Low by FEMA at the 99th percentile.
The Bywatts loss layer is calibrated to solar PV hardware, so it is not applied to a wind plant. The ratings below are the FEMA National Risk Index county hazard ratings for this location.
Steele County hazard ratings
| Peril | FEMA rating | National percentile | Peril score | Events per year |
|---|---|---|---|---|
| Winter weather | Relatively Low | 99th | 5.0 of 5 | 23.5 |
| Strong wind | Relatively Moderate | 98th | 4.9 of 5 | 2.4 |
| Ice storm | Relatively Moderate | 98th | 4.9 of 5 | 0.62 |
| Hail | Relatively Moderate | 84th | 4.4 of 5 | 4.2 |
| Tornado | Very Low | 83rd | 4.3 of 5 | 0.53 |
| Heat wave | Very Low | 77th | 4.1 of 5 | 1.3 |
| Lightning | Very Low | 55th | 3.2 of 5 | 28.4 |
| Wildfire | Very Low | 46th | 2.8 of 5 | <0.01 |
| Earthquake | Very Low | 4th | 1.1 of 5 | <0.01 |
| Riverine flooding | Very Low | 2nd | 1.1 of 5 | 0.75 |
Perils not assessed in Steele County
These perils carry no usable National Risk Index figure for this county, so they are excluded from the scoring rather than scored zero. A zero would claim the peril was assessed and found benign.
| Peril | Why it is not scored |
|---|---|
| Hurricane | FEMA rating is "Not Applicable" for this county |
| Coastal flooding | FEMA rating is "Not Applicable" for this county |
Model hail, wind and flood exposure for Steele County in the weather risk calculator
Ratings are the FEMA National Risk Index county hazard ratings; the peril score is a Bywatts transform of the FEMA national percentile. Full data sources and the solar vulnerability methodology are in the weather risk calculator.
Modeled estimate for screening and negotiation. Built from FEMA National Risk Index county hazard data and a solar vulnerability layer documented above. Not a quote, a binder, or actuarial advice, and not a substitute for a carrier's own model. Hazard data: FEMA National Risk Index December 2025, synced 2026-07-24. Resolution is county level, not site level.