11.07.2015 Views

Snake River White Sturgeon Conservation Plan ... - Idaho Power

Snake River White Sturgeon Conservation Plan ... - Idaho Power

Snake River White Sturgeon Conservation Plan ... - Idaho Power

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Idaho</strong> <strong>Power</strong> CompanyChapter 4: Conceptual Design for <strong>White</strong> <strong>Sturgeon</strong> Passage Facilitiesnumerous pools with nearby high-velocity runs for staging and rapids that are suitable forspawning; such pools are absent in the reaches below C.J. Strike and Oxbow dams. The distancesthat spawners traveled varied by reach: sturgeon traveled 0.3 to 9.0 river miles between KingHill and Bliss Dam (S3335 and S275) (Figure 3), 1.5 to 6.0 river miles below Swan Falls Dam(S339 and R133) (Figure 5a), and 0.0 to 2.0 river miles below Hells Canyon Dam (S249, S248,and S294) (Figure 6). None of the telemetered spawners in these river segments traveledupstream to the dam tailraces (Lepla and Chandler 2001).Lepla and Chandler (2001) also observed that several spawners exhibited post-spawningbehavior by departing, generally downstream, from spawning areas within a few weeks, althoughthis behavior also varied. For instance, spawners from C.J. Strike Reservoir typically returneddownstream to the reservoir by late May (S2633, S2354, S2426, and S249) (Figure 3). BelowHells Canyon Dam, we observed similar behavior in two female sturgeon that departeddownstream. The distance these fish moved downriver ranged from 13 to 61 river miles,followed by return movements back upstream (24–31 river miles) by the middle of summer(S249 and S294) (Figure 6). Still other sturgeon remained at spawning sites and displayed nodiscernable post-spawning movement at all (S3335, S2534 [Figure 3], S114, S105 [Figure 4],S339 [Figure 5a], and S248 [Figure 6a]). Overall, the predominantly localized movement byreproductive and nonreproductive sturgeon suggested that several sections of the <strong>Snake</strong> <strong>River</strong>provide suitable habitat for various life history functions, including feeding, rearing,overwintering, and spawning (Lepla et al. 2001).As mentioned already, movements of most sturgeon were highly localized, although somejuvenile and adult white sturgeon have moved downstream past dams in reaches of the middle<strong>Snake</strong> <strong>River</strong>. Lepla and Chandler (1995a, 1997) recaptured 15 hatchery sturgeon below BlissDam and 6 sturgeon (4 wild and 2 hatchery) below C.J. Strike Dam that had been originallystocked or tagged upstream of these projects. In contrast, no sturgeon (wild or hatchery) that hadoriginally been tagged above the HCC have been sampled downstream of Hells Canyon Damduring IPC’s sturgeon surveys. Based on the mark-recapture data, IPC estimated that 2% of theBliss Reach sturgeon population, on average, move downstream past C.J. Strike Dam annually(K. Lepla, pers. comm.). This estimate is comparable with the rate of annual downstreammovement (2%) estimated for sturgeon marked and released in the four lower Columbia <strong>River</strong>reservoirs (ODFW, unpubl. data).The environmental cues that drive older life stages of sturgeon to move downstream from onereach to another are poorly understood. These sturgeon may be seeking additional rearing andfeeding habitats. For instance, the <strong>Idaho</strong> Department of Fish and Game released 2,211 hatcheryrearedsturgeon (age 1) in the 13-mi segment between Lower Salmon Falls and Bliss damsduring 1989–1990 (Patterson et al. 1992). Movement by some of these stocked fish into the nextdownstream reach may have been related to searching for additional rearing habitat for whichthere was less competition. Still, other sturgeon from these stockings remained and wererecaptured at the same release point (the Lower Salmon Falls tailrace) 5 years later (IPC, unpubl.data).Hells Canyon Complex Page 9

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

Saved successfully!

Ooh no, something went wrong!