Laserfiche WebLink
<br />reaches known to support humpback chub in Colorado, Yampa Canyon on the Yampa River and <br />Black Rocks on the Colorado River, research has failed to discover a significant threat of <br />extirpation to eit!ler population under current environmental conditions. This includes the <br />presence of an abundant and potentially predatory channel catfish population in both reaches. The <br />Black Rocks popuhtion has demonstrated a relative stability since monitoring began in the early <br />1980s (see Valdez 1980, Miller et al. 1982, Valdez and Clemmer 1982). Due to the relatively <br />unmodified flow l"('girne and habitat within Yampa Canyon and the persistence of the humpback <br />chub population monitored there since the late 1980s (see Tyus and Karp 1989), this population <br />is also presumed to be relatively stable. Also five natural populations currently exist in the Upper <br />Basin, and appear t<) have persisted in these locations in relatively stable numbers since their initial <br />discovery and identification. However, population estimates are planned to determine abundance <br />in all of these existing populations relative to desired abundance criteria required for recovery and <br />downlisting and d~listing. Other recovery program tools, such as nonnative fish control (e.g. <br />channel catfish) and flow management remain under evaluation as feasible and effective <br />approaches to increasing humpback chub population abundance in Black Rocks and Yampa <br />Canyon. Augmentltion stocking may be considered if population estimation results for the Yampa <br />Canyon population indicate expansion of humpback chub numbers in the Lodore, Whirlpool and <br />Split Mountain canyon reaches is desirable to augment the Yampa Canyon population. The <br />objective here would be to facilitate progress toward developing a self-sustaining population at <br />desired abundance level and composed of a complex of multiple subpopulations within these <br />adjacent canyon habitats. <br /> <br />Stocking Plan - Razorback sucker (Table 1) <br /> <br />Razorback Bucker are considered first priority for stocking in Colorado due to the presence <br />of, but declining trend of wild populations due to inadequate recruitment. Rationale for the <br />stocking is straighlforward. Populations of razorback previously occupied habitat in all three <br />target river reacheil (Holden et al. 1981, Burdick 1992), but are now nearly extiIpated, and <br />insufficient numben: exist in the wild upon which to base a natural expansion and recolonization <br />strategy. Factors thought to be responsible for the razorback sucker's decline include primarily <br />loss of floodplain habitats as nursery areas with concomitant establishment of nonnative fish <br />species as effective predators/competitors in remaining low-velocity nursery habitats. If <br />successful, stocking will establish a multi-year class population of razorback sucker late-juveniles <br />and adults that are largely invulnerable to predation. Threat of predation to razorback sucker <br />occurs primarily in the Grand Valley reach from existing populations of channel catfish and red <br />shiner, the most significant introduced species demonstrating abundant populations and <br />documented predation upon razorback sucker young in laboratory conditions (Muth and Beyers <br />1991). Monitoring of this population will track growth and survival to maturity, general habitat <br />use, use of available spawning habitat, and production and fate of larvae. Monitoring of stocked <br />populations will also provide clues to potential causes of failure to survive as well. The presence <br />of a long-lived aclult population attempting to reproduce will subsequently facilitate the <br />detennination of wh,ch presumed limiting factors-nursery habitat, predators, irrigation canal loss, <br /> <br />6 <br /> <br />r <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I ' <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />