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
Net Catches. During the pikeminnow population estimate study, (Doug <br />Osmundson, unpublished data), the point estimate for the river net catch rate <br />(average number of fish per trammel net) for sub-adult and adult pikeminnow in <br />the upper reach of the Colorado River was reported to be the highest in 1998 <br />(0.97 fish/net). This coincided with the peak of 23 pikeminnow that used the <br />Redlands passageway in July and August 1998. In 1999 the river net catch rate <br />for pikeminnow declined about 20% (0.78 fish/net) which coincided with the <br />decline of pikeminnow collected in the fish trap. However, in 2000, the river <br />net catch rate increased slightly (0.81 fish/net) while the number of pikeminnow <br />in the fish trap-declined slightly further. Between 1998 and 2000, the net catch <br />rates were not significant (Ps 0.05). Therefore, net catch rate data does not <br />explain the decline. <br />Length Frequency. Length-frequency analysis of Colorado pikeminnow <br />captured from the upper reach during the spring/early summer of 1998-2000 shows <br />that a dominant length class increased slightly during this period (Appendix; <br />Figure E.2.). Although the length increased, smaller size classes of pikeminnow <br />(400-550 mm class) were still being recruited into the river population. <br />Consequently, during 1998-2000, a proportional number of pikeminnow were <br />available in the river population to move through the passageway, similar to <br />sizes of pikeminnow seen in fish trap catches during 1997 and 1998. <br />Body Condition. The mean relative body condition of pikeminnow in the <br />lower reach of the Colorado River during the 1998-2000 pikeminnow population <br />estimate was lowest in 1998 (0.81) compared to 0.87 in 1999 and 0.90 in 2000. <br />The mean relative body condition of pikeminnow in the lower reach during 1998 and <br />1999 was lower than the mean body condition during 1992-1994 (although not <br />significant at P5 0.05). There are no data for relative body condition for 1995- <br />1997 in the lower reach. Data from this study have demonstrated that pikeminnow <br />originally captured in the lower reach of the Colorado River have moved upstream <br />and have been recaptured in the Redlands fish trap. Three pikeminnow collected <br />in the fish trap in 1997 were recaptures that had been previously captured in the <br />Colorado River downstream from Moab (Appendix; Table E.1.). Two other <br />pikeminnow, one each in 1998 and 1999, captured in the fish trap had previously <br />been captured in the lower reach of the Colorado River. The reason for upstream <br />movements by smaller pikeminnow from the lower to upper reach were advanced by <br />Osmundson et al. (1998) and were discussed in an earlier section (Fish Trap: <br />Colorado pikeminnow: Size). <br />Population Size. Pikeminnow population point estimates increased from <br />about 344 in the early 1990's to 442 individuals (28%) in the late 1990's in the <br />lower reach. Accordingly, during the same period in the upper reach, the number <br />of pikeminnow increased from about 253 to 407, an increase of 61% (Doug <br />34
The URL can be used to link to this page
Your browser does not support the video tag.