Laserfiche WebLink
SPAWNING CUES FOR COLORADO SQUAWFISH <br />flow patterns between the gages and the spawning <br />area is that the beginning of the -flow spike oc- <br />curred simultaneously at the two gage sites, sug- <br />gesting that rainstorms affected the region and not <br />a more limited upstream locale. <br />Sampling Artifact or Spawning Cue? <br />The frequency distribution of estimated spawn- <br />ing dates was a function of number of larvae <br />sampled. The question arises as to whether peaks <br />observed in these frequency distributions in 1983- <br />1986 were sampling artifacts caused by a flushing <br />effect in the spawning grounds due to the flow <br />spike or a result of drift nets sampling more water <br />(and thus more larvae) during rising flow even <br />though catch per unit of water volume sampled <br />remained the same. The answers are no to both, <br />because lengths, not numbers, of captured larvae <br />were used to estimate spawning dates, that is, <br />when the eggs were deposited in the gravel. The <br />bimodal distribution of Colorado squawfish larvae <br />captured in 1985 (Nesler 1986) supports this argu- <br />ment. The length range of Colorado squawfish <br />larvae responsible for the July 23 spawning peak <br />was similar to that of larvae responsible for the <br />June 25 spawning peak (8.0-9.5 mm versus 7.9- <br />9.4 mm total length, respectively). This indicates <br />that both groups consisted of protolarvae and that <br />the later spawning peak was not an artifact caused <br />by older, larger larvae being flushed out with the <br />second flow spike. <br />Hamman (1981) observed that Colorado <br />squawfish eggs are adhesive and that hatched <br />larvae do not leave the interstitial spaces of the <br />cobble substrate for 3-4 d following hatching. <br />These observations suggest that the eggs are fairly <br />well protected from flow variations and that Col- <br />orado squawfish larvae would emerge from the <br />gravel some time after the flow spike occurrence. <br />Larvae were captured at lower flow levels well <br />after the flow spike event occurred. Also, larvae <br />were captured by drift nets in the nearshore zone <br />of the river cross section. The characteristic low <br />flow of this zone is unaffected by the amount of <br />water moving downstream. The nearshore zone, <br />and hence the drift-net sampling site, merely <br />changed its relative position in the channel with <br />little increase in current velocity or volume of <br />water sampled. The critical point is that estimated <br />spawning dates derived from total lengths of the <br />captured larvae indicate the larvae were deposited <br />in the gravel as eggs during a flow spike event. <br />The spawning periods estimated from collec- <br />tions of larval Colorado squawfish have been <br />7s <br />corroborated by radiotracking data on adults and <br />collections of ripe adults on the spawning ground. <br />Estimates of spawning dates made from larval <br />collections, radiotracking, and collection of ripe <br />adults were generally in agreement during 1981- <br />1985 (Tyus et al. 1987). Estimations of optimal <br />spawning periods for 1981-1985 were presented <br />by Tyus et al. (1987). Their estimates and ours <br />agree closely except for 1984; their estimated <br />optimal spawning period was July 20-August 10 in <br />1984, but we estimated the end of peak spawning <br />activity at July 18. The optimal spawning period <br />estimated by Tyus et al. (1987) for 1984 was based <br />on data from five radiotracked fish, the collection <br />of 16 ripe adults (only two of which were females), <br />and 58 larvae collected in the Green River below <br />the confluence of the Yampa River in late August- <br />early September. Our estimate resulted from 365 <br />larval Colorado squawfish collected from July 17 <br />through August 8. Tyus et al. did observe ripe <br />Colorado squawfish adults on the primary spawn- <br />ing reach in the Yampa River at least as early as <br />July 15. We believe that substantial spawning <br />activity occurred prior to this date but was not <br />detected from radiotracking observations or adult <br />fish sampling efforts by Tyus et al. (1987). <br />In reference to flow conditions at the cessation <br />of peak spawning activity, remarkably similar <br />flows occurred in 1983, 1985, and 1986, whereas <br />the 1984 flow seemed notably higher. Another <br />unaccountable variable was the overall number of <br />adult Colorado squawfish participating in the <br />spawning run from year to year. Most of the <br />available adult Colorado squawfish might have <br />participated during the peak of spawning in 1984, <br />leaving relatively feyv adults to spawn afterwards <br />even though flows were still above 55-65 m3/s. <br />The cessation and resumption of spawning with <br />fluctuating flows in 1985 supported the hypothesis <br />that major spawning activity ceased at flows be- <br />low this threshold. <br />Flow Spikes as Spawning Cues <br />Our approach to the observed relationship be- <br />tween Colorado squawfish spawning and seasonal <br />flow regimes in the Yampa River is quite simplistic <br />in scope relative to the complex interaction of <br />external and internal cues that may initiate and <br />regulate gonadal development, migratory behav- <br />ior, spawning, and egg deposition. The relation- <br />ship between internal and external rhythms is <br />subtle and the timing of a species' reproductive <br />cycle is a compromise involving many environ- <br />mental considerations (Bye 1984). Environmental <br />