09.06.2015 Views

Condit Dam Removal Condit Dam Removal - Access Washington

Condit Dam Removal Condit Dam Removal - Access Washington

Condit Dam Removal Condit Dam Removal - Access Washington

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Condit</strong> <strong>Dam</strong> Hydroelectric Project<br />

Final Supplemental EIS<br />

Based on telephone conversations with local WDFW, National Oceanic and Atmospheric<br />

Administration (NOAA) (formerly NMFS), and USFWS biologists, observed behavior patterns<br />

of dip-in anadromous salmonids indicate that they utilize deep pools throughout the bypass reach<br />

for thermal refuge. The increased flows in the bypass reach and colder water after dam removal<br />

would increase both the quality and quantity of thermal refuge habitat, compensating for any<br />

potential loss of thermal refuge below the bypass reach.<br />

Issue 4: Temporary migration impacts to steelhead associated with the presence of the<br />

cofferdam after the dam is removed could occur.<br />

Resolution: PacifiCorp has committed to remove the cofferdam by May 1 of the year following<br />

dam removal to prevent blocking passage for migrating salmonids. The FSFEIS (FERC 2002)<br />

indicates that the entire year-class of age-0 (juveniles produced during the spring of the year of<br />

dam removal) winter-run steelhead are expected to be lost as a result of turbidity levels in the<br />

river associated with the proposed dam removal. According to PacifiCorp, the cofferdam would<br />

be removed in time for the following summer run to pass unobstructed. PacifiCorp does not<br />

anticipate migration impacts to winter or summer steelhead from the cofferdam.<br />

The FSFEIS acknowledges the loss of most of the fish in the river channel at the time of dam<br />

removal and the loss of a year-class of winter-run steelhead as a result of turbidity levels<br />

associated with dam removal. The cofferdam would be removed in time for summer steelhead,<br />

salmon, and subsequent year-classes of winter-run steelhead passage to upstream habitat. Thus,<br />

unavoidable impacts to fish from dam removal have been recognized. There is enough overlap<br />

in the life history of winter-run steelhead (i.e., a portion of adult winter-steelhead from other<br />

year-classes will return to the White Salmon River during the years that adults from the lost yearclass<br />

would have potentially returned) that the run from that year-class would likely rebuild over<br />

the long term.<br />

Issue 5: There is a potential for erosion and scour impacts to the structural stability of the two<br />

downstream bridges (one highway, one railroad) across the White Salmon River.<br />

Resolution: The supports for the downstream highway and railroad bridges are located in the<br />

slack water pool at the mouth of the river created by Bonneville <strong>Dam</strong>. These bridge supports<br />

have withstood historical flood flows, including the flow from the 1996 flood estimated at<br />

45,000 cfs. The highest flow anticipated from the dam breach is 10,000 cfs. Because the dam<br />

breach flows are less than one-quarter the flow from the 1996 flood, no significant erosion or<br />

scour impacts are anticipated from the short-term high flows associated with the dam breach.<br />

2.4 SCOPE OF THIS SEIS<br />

The focus of this SEPA SEIS is the “Settlement Agreement with Modifications” alternative,<br />

since it was the FERC staff-recommended alternative in the FSFEIS. The description of that<br />

alternative has been supplemented with additional detail provided by PacifiCorp. The no-action<br />

alternative and its analysis from the FEIS is adopted and not further addressed. In the FSFEIS,<br />

FERC considered an adequate range of alternatives, which are not addressed further here.<br />

2-5

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!