My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
FLOOD10353
CWCB
>
Floodplain Documents
>
Backfile
>
10001-11000
>
FLOOD10353
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
11/23/2009 12:50:35 PM
Creation date
5/15/2007 10:42:46 AM
Metadata
Fields
Template:
Floodplain Documents
County
Pitkin
Community
Redstone
Stream Name
Crystal River
Title
An Analysis of the Levee System at Redstone Colorado
Date
5/1/1992
Prepared For
CWCB
Prepared By
US Army Corps of Engineers
Floodplain - Doc Type
Flood Mitigation/Flood Warning/Watershed Restoration
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
190
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 /> <br />e <br /> <br />e <br /> <br />e <br /> <br />Redstone <br /> <br /> <br />EXISTING BANK/LEVEE CONDITIONS AND LIKELY REQUIRED IMPROVEMENTS <br /> <br />As indicated in the summary table, the existing bank <br />adjacent to the sewage lagoon and fire station (between cross <br />sections 82 and 83) is slightly below the 100-year flood <br />elevation. However, the sewage lagoon berm itself appears to be <br />slightly higher than the adjacent natural bank and Pitkin County <br />indicated that it is not concerned about the flood threat to the <br />lagoon (which was not flooded in 1985). Therefore, no potential <br />project quantities or costs were developed for this site. <br />Nonetheless, it would be advisable to include this area in any <br />future detailed analyses to verify that it is not vulnerable to <br />flooding. <br /> <br />The existing levee extends from just upstream of cross- <br />section 87 to the Coal Creek confluence between cross sections 90 <br />and 91 (Attachment 3). The upstream 1,550 feet of the levee was <br />originally built at the turn of the century and has been <br />periodically enlarged since. Following the 1985 flood, the Soil <br />Conservation Service (SCS) constructed a 250-foot emergency levee <br />downstream of the existing levee and Pitkin County built an <br />additional 400-foot levee beyond that. These two levees were <br />apparently constructed to a large extent from the adjacent <br />riverbed materials. The levee lacks adequate freeboard for both <br />the 100- and 500-year events. Immediately downstream of the <br />levee (cross-section 87) where the 100- and 500-year flood <br />elevations would exceed the bank elevation by 1.7 and 2.7 feet. <br />Therefore, it would be important to have any future levee <br />improvements tie in to high ground, especially at the downstream <br />end, to prevent backwater flooding (and at the upstream end to <br />prevent flanking). <br /> <br />FEMA standards (Appendix D) require a mlnlmum 3 feet of <br />freeboard (as well as various other criteria). The existing <br />levee has a freeboard range of -1.7 to +2.4 feet for the 100-year <br />event and -2.7 feet to 1 foot for a 500-year event. Therefore, a <br />significant increase in levee height would be required to meet <br />FEMA standards. <br /> <br />The 29 supplemental cross sections of the levee which were <br />surveyed by Pitkin County (under contract) for this study verify <br />that the levee not only lacks sufficient height but also lacks <br />structural integrity through much of its length. These cross <br />sections along with a profile of the crown elevations were <br />plotted and are compiled in Appendix E. Further, previous <br />studies make reference to the levee being composed of <br />unconsolidated material and could be eroded by the sustained high <br />flows of a snowmelt flood. The recent Corps Non-Federal Levee <br />Inspection Report (Appendix F) substantiates this. As part of <br />the inspection, a limited geotechnical analysis was made. The <br /> <br />7 <br />
The URL can be used to link to this page
Your browser does not support the video tag.