My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
BOARD00716
CWCB
>
Board Meetings
>
Backfile
>
1-1000
>
BOARD00716
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/16/2009 2:53:28 PM
Creation date
10/4/2006 6:43:19 AM
Metadata
Fields
Template:
Board Meetings
Board Meeting Date
5/24/1999
Description
WSP Section - Colorado River Basin Issues - Quantification of the National Park Service Reserved Water Right for the Black Canyon of the Gunnison National Monument (USA v Denver 79SA99 and 100)
Board Meetings - Doc Type
Memo
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
11
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
<br />c' <br /> <br />t <br /> <br />Summary of Public Comments re: <br />NPS Proposed Black Canyon Water Right Quantification <br /> <br />.j <br /> <br />e <br /> <br />PEAK FLOWS <br /> <br />I, Too big - results in downstream flooding. <br />. commercial and residential properties. agricultur~llands and related water structures. city <br />property, highways and bridges. waste water tre'llment plant may be threatened. <br />. will NPS accept responsibility? <br />. how is BR involved? Will there be continued coordinated effort with BR to regulate Aspinall <br />releases during emergencies? Can NPS force BR to increase flood flows? <br />. timing ofNPS pe:lk flow? When? To coincide \\~th the North Fork pe:Ik? <br /> <br />Aspinall Unit spills can result in an uncontrolled downstream environment which: <br />. could jeopardize public safety <br />. may be detrimental to young-of-the-year trout fry <br /> <br />How will dam safety and the safety of downstream property and residents be insured? Who will bear <br />the cost of increased operation and maintenance expenses associated with wear and tear on spillways? <br /> <br />Operation of the Aspinall Unit should be optimized to prevent spills and take advantage of power <br />generation revenue. . <br /> <br />Flows in excess of 12,500 cubic feet per second (cfs) could cause severe damage to the Uncompahgre <br />Valley Water Users Association diversion dam at the East Portal of the Gunnison TunneL <br /> <br />e <br /> <br />Proposed peak flow releases when coupled with rainstonn-driven flash floods cause unnecess:lry <br />downstream flooding. <br /> <br />2. Too smaIl. <br />. NPS recom!nenced flows are ~considernbly short of what studies have shown are needed for <br />sufficient sediment trnnsport." High-flow targets must be OCc:lSionally higher. <br /> <br />. Average annual peak flow target should be closer to the historic average of 12,000 cfs, and <br />adjusted from there based on annual water'supply forecast. <br /> <br />3. "FLUSHING" flows. <br />. debris and sediment being flushed from the canyon... ~debris that has been there since <br />1931" - what impact is this going to have on downstream environment and infrastructure? <br /> <br />4, NPS pe:Ik flow requests are vague and based on future, continuing negotiations, not a firm <br />commitment to a specific flow regime, NPS should develop binding criteria for releases based on <br />different snowpack and runoff scenarios; criteria should include duration. ramping rates, shoulder <br />flows. These criteria should be released for public comment. Ai least for "wet", "normal", and "dry" <br />years, with and without full consumption of 240,000 acre-feet from the Aspinall Unit. <br /> <br />GENERAL HYDROLOGY <br /> <br />L Why is the NPS using pre-tunnel hydrology as basis for baseflow requirements and post-tunnel for <br />peak flow tcquiremcnts? Exercise caution when referencing 1933 conditions, they do not necessarily <br />represent "natur~l" conditions, but possibly a tr.msitory condition in a dynamic system. <br /> <br />e <br />
The URL can be used to link to this page
Your browser does not support the video tag.