CLEARWATER PAPER IPP LEWISTON

Operating

Biomass power plant

Capacity
114 MW
Primary fuel
Biomass
County
Nez Perce County
Operator
CLEARWATER PAPER CORPORATION
Status
Operating
Commissioned
1950
EIA plant ID
50637
Generators
4
Technology
Wood/Wood Waste Biomass
Net generation (2024)
376 GWh
Capacity factor (2024, EIA nameplate)
38%
Data vintage
EIA-860 2024 final; EIA-923 2022-2024 final
Coordinates
46.4308, -116.9738

See it on the map

CLEARWATER PAPER IPP LEWISTON, a 114 MW Biomass power plant in Nez Perce County, Idaho. Operated by CLEARWATER PAPER CORPORATION, commissioned 1950.

How CLEARWATER PAPER IPP LEWISTON compares

With 114 MW of capacity, CLEARWATER PAPER IPP LEWISTON ranks 12th among the 123 operating power plants Bywatts maps in Idaho and is the largest of the 3 operating Biomass plants in the state. It accounts for about 90% of Idaho's operating Biomass capacity and 2.3% of all operating capacity in the state. Nationally it is the 11th-largest of the 350 operating Biomass plants in the database. Commissioned in 1950, it is older than 80% of the 121 operating Idaho plants with a recorded commissioning year.

EIA-860 lists 4 generators at the site with 114 MW of nameplate capacity, all wood/wood waste biomass technology. Net generation was 376 GWh in 2024 (a 38% capacity factor), down 4% from 2022. Its generators came online between 1950 and 1991.

Grid neighborhood

The nearest named substation is NORTH LEWISTON (230 kV), about 2.5 miles away; the closest transmission line found within 10 miles is a 115 kV line owned by AVISTA CORP, about 0.1 miles away. Another 2 operating power plants totaling 5 MW sit within 25 miles; the largest is GRIMES WAY (4 MW, Natural Gas).

Computed by Bywatts from HIFLD power plant, substation and transmission line records and EIA-860/923 survey data; distances are straight-line. Sources and methodology

Weather peril exposure

CLEARWATER PAPER IPP LEWISTON is a 114 MW biomass power plant in Nez Perce County, ID, operated by CLEARWATER PAPER CORPORATION, commissioned in 1950. Nez Perce County carries low modeled catastrophe exposure in the FEMA National Risk Index, scoring 1.1 of 5 at the 2nd national percentile. Wildfire is the leading peril, rated Relatively Moderate by FEMA at the 88th percentile.

The Bywatts loss layer is calibrated to solar PV hardware, so it is not applied to a biomass plant. The ratings below are the FEMA National Risk Index county hazard ratings for this location.

1.1 of 5Modeled catastrophe exposure
LowExposure band
WildfireLeading peril
Very LowFEMA county risk rating

Nez Perce County hazard ratings

PerilFEMA ratingNational percentilePeril scoreEvents per year
WildfireRelatively Moderate88th4.5 of 5<0.01
Riverine floodingRelatively Low75th4.0 of 50.54
Heat waveRelatively Low64th3.6 of 54.5
EarthquakeVery Low36th2.4 of 5<0.01
Strong windVery Low10th1.4 of 50.19
HailVery Low6th1.2 of 50.34
TornadoVery Low5th1.2 of 50.02
LightningVery Low3rd1.1 of 516.9
Winter weatherVery Low3rd1.1 of 512.5
Ice stormVery Low1st1.0 of 50.01

Perils not assessed in Nez Perce 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.

PerilWhy it is not scored
HurricaneFEMA rating is "Not Applicable" for this county
Coastal floodingFEMA rating is "Not Applicable" for this county

Model hail, wind and flood exposure for Nez Perce 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.