My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
BOARD01150
CWCB
>
Board Meetings
>
Backfile
>
1001-2000
>
BOARD01150
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/16/2009 2:58:35 PM
Creation date
10/4/2006 6:50:36 AM
Metadata
Fields
Template:
Board Meetings
Board Meeting Date
5/24/1999
Description
WSP Section - Colorado River Basin Issues - Colorado River "15-Mile Reach" ESA Section 7 Consultation
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.
/
9
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 />Tom Pius <br />Peter Evans <br />Re: lSMRPBO and Yampa River Issues <br />May 18. 1999 <br />Page 2 <br /> <br />. <br /> <br />meeting the flow shortages; and a recommended alternative to mcet thc Servi<:<.:'s [lnw <br />recommendations. enlargementofElkheadllllll Stegecoach Reservoirs. A subsequent detailed study <br />was conducted focusing on alternatives for enlarging Elkhead Reservoir and managing flows in the <br />Yampa River recognized as the short ~ solution. Subsequent to that report NEP A was initiated <br />on the proposed Elkhead enlargement, aU with Recovery Program funds and with the participation <br />of the Service and the State of Colorado. <br /> <br />Based on what we learned, and to find alternatives to enlarging Elkhead and Stagecoach Reservoirs. <br />we collectively agreed to pursue a Yampa River Management Plan and try to bring basin water <br />Dlallagers and their resources to the "table." However, the Service was not totally comfortable with <br />the late-summer season low.flow recommendations, so the Recovery Progranl sponsorcd an <br />intensive low-flow study. The Recovery Program also conducted a second economic study (which <br />confirmed the results of the first) and developed a second hydrologic model (using ST A TEMOD). <br />The USFWS signed an MOU of cooperation with the Yampa River Basin Partnership and h,L~ <br />become an active participant along with the State and the Partnership working toward dcvclopmcnt <br />of the "Plan." <br /> <br />. <br /> <br />The only way to describe the present situation is confusing. The !ow-flnwstudies have been <br />completed. I have been told that the Recovery Program's Biology Cornmitlcc has adopted thc <br />position that the 93 c,f.s. low-flow recommendation is critical, that flows cannot he allowed tn go <br />below this figure more frequently than has occurred in the past, hJ.l! that augmentation is not <br />nccessary and there must be no future depletions during the peak months or April-July It,r <br />augmenting fish flows. At the May 12th Management Committee meeting Service l3iologist, Frank <br />Ptiefer, stated "if looking for storing on peak - don't bother." Meanwhile, the Recovery Progrum <br />pays $30,000 annually to lease 2,000 a.r. of water stored on the peak in Steamboat Rcservoir for <br />FWS-directed release to support low flows. <br /> <br />Further, the Bureau of Reclamation has severed (or threatened to sever) funding for the Yampa River <br />activities, believing (quite appropriately) that based on what they believe the Service's current <br />position to be capital funds should not be used for further activities on the Yampa River at least until <br />structural alternatives are proposed. <br /> <br />Meanwhile, the Service has issued biological opinions on the operation of Flaming Gorgc and the <br />Duschene River which rely on hydrology from the Yampa and White River systems. The Service <br />has issued a draft biological opinion for the High Savory Project which relies 011 the Yampa River <br />Management Plan (and depletes an average of 7,700 a.f. form the peak of the Lillie Snake River). <br /> <br />. <br />
The URL can be used to link to this page
Your browser does not support the video tag.