My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
13000000095 Continental Dam Inundation Report
CWCB
>
Loan Projects
>
DayForward
>
3001-4000
>
13000000095 Continental Dam Inundation Report
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
2/5/2014 12:21:51 PM
Creation date
2/5/2014 12:21:51 PM
Metadata
Fields
Template:
Loan Projects
Contract/PO #
13000000095
Contractor Name
Santa Maria Reservior Company
Contract Type
Grant
Water District
20
County
Hinsdale
Mineral
Loan Projects - Doc Type
Report
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
74
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 />CONTINENTAL DAM - 2 - July 11, 2013 <br />INUNDATION MAPPING REPORT <br />Table 1. Continental Reservoir Dam Failure <br />Summary of Elevation Data <br />Description <br />1925 & 1990 <br />Plans (feet, <br />unknown <br />datum) <br />SEO Capacity <br />Table (feet, <br />gage height) <br />Dam Crest 10290 86.5 <br />Emergency Spillway Crest 10280 76.5 <br />Outlet Pipe (Upstream Invert) 10203.5 0 <br />Approx. Natural Ground under Embankment 10200 -3.5 <br /> <br /> <br />The elevations cited in the remainder of this memo are in reference to the gage height. <br /> <br />The elevation of the upstream invert of the outlet culvert defined on Revised Sheet 4 of 5 of the <br />1925 plan set closely matched gage height 0. The approximate surface area of Continental <br />Reservoir was calculated using the SEO capacity table for each gage height. At a gage height of 1 <br />foot the surface area was calculated as 3.7 acres. Based on this small surface area it was concluded <br />that any water which may be stored below gage height 0 is negligible relative to the maximum <br />storage volume of 22,678 acre-feet above gage height 0. Though no extra storage below gage <br />height 0 was considered in this analysis, the breach bottom was assumed to extend to gage height <br />-3.5 because this is the approximate natural ground elevation underneath the embankment. An <br />elevation-area-capacity curve based on the SEO capacity table is provided in Appendix B. <br /> <br />Two empirical methods for predicting the average breach width and failure time were compared. <br />The methods, which are included as spreadsheets in Appendix C are the Froehlich (2008) equations <br />and the MacDonald & Langridge – Monopolis/Washington State (MLM-WA, 2007) equations <br />(collectively referred to as the “empirical equations”). The empirical equations predict the average <br />breach width and failure time as a function of depth of water, dam height, and volume of water <br />stored. The MLM-WA method also takes into consideration the estimated volume of embankment <br />eroded. <br /> <br />The Froehlich method resulted in predicted bottom and average breach widths of 181 and 244 feet, <br />respectively, and a breach formation time of 1.08 hours. However, based on the supplemental “as- <br />built” sheet in the 1925 plan set, the canyon will constrain the breach to a bottom width of <br />approximately 90 feet and an average width of approximately 215 feet. The breach formation time <br />of 1.08 hours remains unchanged because it is independent from the breach width in the Froehlich <br />method. <br /> <br />The MLM-WA method resulted in a predicted bottom breach width of 55 feet, an average breach <br />width of 235 feet, and a formation time of 2.99 hours. The “Results Check” section of the MLM- <br />WA spreadsheet also predicted that the erosion rate calculated by the equations was slower that <br />what can be reasonably expected. For this reason, the breach parameters predicted by the MLM- <br />WA method were not considered for use in the breach simulation of Continental Dam. <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.