My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
9432 (2)
CWCB
>
UCREFRP
>
Public
>
9432 (2)
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/14/2009 5:02:35 PM
Creation date
5/20/2009 10:09:36 AM
Metadata
Fields
Template:
UCREFRP
UCREFRP Catalog Number
9432
Author
Modde, T. and M. Fuller.
Title
Feasibility of Channel Catfish Reduction in the Lower Yampa River.
USFW Year
2002.
USFW - Doc Type
Vernal.
Copyright Material
NO
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
120
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
1998-Tagged Fish <br />Capture and Release. Four adult Colorado pikeminnow captured in the Lower <br />Gunnison River between the Redlands Dam plunge pool and the confluence with the <br />Gunnison River were implanted with 29-gram LOTEK° transmitters between 18 May and <br />22 June (mean TL=691 mm; range=594-767). These fish were then translocated and <br />stocked upstream of the Redlands Dam in the Gunnison River. Three fish were <br />released at Whitewater (RM 14.7) and one at Bridgeport (RM 29.3). Two other <br />adult pikeminnow captured in the 15-mile reach of the Upper Colorado River were <br />also implanted with 29-gram LOTEK° radio transmitters during-April. These two <br />fish were part of another ongoing study to evaluate the potential use by <br />endangered and non-endangered native fishes of the recently constructed fish <br />passageway and notch at the Grand Valley Irrigation Company's diversion dam at <br />Palisade, Colorado (Appendix; Table J.1.). The movements of these two fish were <br />included in this study because there was every likelihood that they could move <br />downstream from their release point in the Upper Colorado River, move upstream <br />in the Lower Gunnison River, and migrate through the passageway at Redlands. <br />Movement and Dispersal. In 1998, three of the four fish translocated and <br />released at two different sites upstream of the Redlands Dam moved downstream <br />over the dam in late-June just prior to the spawning season. Three of these four <br />fish continued traveling downstream in the Gunnison River and entered the <br />Colorado River. One pikeminnow was detected in mid- and late-July in Horsethief <br />Canyon at RM 145 in the Colorado River. One other pikeminnow was found in mid- <br />July at RM 164, immediately upstream of WWWA. It is speculated that these fish <br />were moving downstream in response to descending flows and were returning to the <br />Colorado River to spawn (Appendix; Table K.7.). The location of one pikeminnow <br />(Code 117) was unknown from late-June until early-November. Two of the three <br />radio-tagged pikeminnow returned in early-August to the Lower Gunnison River. <br />These two fish were ultimately located in the plunge pool of the Redlands Dam on <br />8 August. They both remained there for 20 days. Contact was reestablished with <br />all four of the pikeminnow implanted with radiotags in 1998 until late-September. <br />Contact was made in early-November with two of the translocated pikeminnow.. One <br />fish (Code 117) was contacted at RM 157 and the other (Code 116) at RM 146 in the <br />Colorado River. The fourth pikeminnow (Code 121) remained upstream of the <br />Redlands Dam in the Gunnison River and was last located at RM 3.4 on 8 August <br />(Appendix; Table K.3.). <br />Monitoring of four pikeminnow radiotagged in 1998 was scaled back following <br />spawning because three of the four fish had moved downstream over Redlands Dam, <br />the fate of the four fish following release upstream of the dam was known, and <br />the radiotags would expire before the 1999 spawning season. Therefore, the <br />duration of time that these pikeminnow were monitored and contacted by boat was <br />42
The URL can be used to link to this page
Your browser does not support the video tag.