My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
CWCB San Miguel PHS Final
CWCB
>
Instream Flow Appropriations
>
DayForward
>
1-1000
>
CWCB San Miguel PHS Final
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/15/2016 11:39:23 PM
Creation date
8/23/2011 9:03:15 AM
Metadata
Fields
Template:
Instream Flow Appropriations
Case Number
11CW0129
Stream Name
San Miguel River
Watershed
San Miguel
Water Division
4
Water District
60
County
Montrose
Instream Flow App - Doc Type
ISF INV - Hearing
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
987
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
CDOW and BLM were concerned that the standard R2CROSS method may not be appropriate <br />for this reach of the San Miguel River due to its major width (over 75' wide in most places), type <br />of fish species present (warm /cool water species) and its big river channel hydraulics and <br />characteristics. <br />Accordingly, BLM and CDOW staff compared results from their PHABSIM/RHABSIM data <br />analysis with their R2CROSS analysis. Using the results from the PHABSIM/RHABSIM data <br />analysis, the maximum amount of usable habitat for bluehead suckers was produced at a flow of <br />500 cfs and for flannelmouth suckers at a flow of 325 cfs. The R2CROSS analysis indicated that <br />a spring /summer flow of approximately 650 cfs was necessary to meet all three of the critical <br />hydraulic criteria at this site and a fall /winter flow of 115 cfs would meet 2 of 3 of the hydraulic <br />criteria. <br />CDOW and BLM are recommending that a flow of 325 cfs, for the time period of April 15 <br />through June 14, is the minimum amount necessary to preserve the natural environment to a <br />reasonable degree, for this reach of the San Miguel River. This is based on the assumption that <br />325 cfs would preserve 90% of the weighted useable area available to the bluehead sucker and <br />100% of the weighted useable area available to the flannelmouth sucker. BLM and CDOW staff <br />also believe a flow that maintains adequate bluehead and flannelmouth sucker habitat should also <br />maintain adequate roundtail chub habitat. The spring /summer flow of 325 cfs was reduced to <br />170 cfs for the June 15 through July 31 time period because of water availability concerns. The <br />instream flow recommendation of 170 cfs was derived to maximize the existing bluehead and <br />flannelmouth sucker habitat available under a declining hydrograph, by maintaining an average <br />depth of 1.0 foot over the measured riffle cross - section. An average depth of 1.0 foot combined <br />with average velocities exceeding 1.3 ft/sec, were determined to be marginally suitable bluehead <br />sucker habitat (see Anderson & Stewart Report — Appendix F). <br />Because the PHABSIM/RHABSIM data only quantified suitable versus unsuitable hydraulic <br />habitat as a function of discharge, CDOW and BLM staff used the results of the R2CROSS <br />Method to develop the fall /winter instream flow recommendation of 115 cfs. The R2CROSS <br />Method suggests that fall /winter flows should maintain at least 2 of 3 of the identified critical <br />hydraulic criteria. At the Cross Section #1 site, 115 cfs meets 2 of 3 criteria (average depth and <br />velocity) by providing on average, 0.8 feet of depth and velocities well over 1.0 ft/sec. The <br />fall /winter flow recommendation was further reduced to 80 cfs, for the time period of September <br />through February, due to water availability concerns. It should be noted however, that 80 cfs <br />still maintains adequate velocity (approximately 2.5 ft/sec), a wetted perimeter of almost 60% <br />and an average depth of nearly 0.7 feet. <br />M <br />
The URL can be used to link to this page
Your browser does not support the video tag.