My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
FLOOD07934
CWCB
>
Floodplain Documents
>
Backfile
>
7001-8000
>
FLOOD07934
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/25/2010 7:13:11 PM
Creation date
10/5/2006 3:18:29 AM
Metadata
Fields
Template:
Floodplain Documents
County
Larimer
Community
Fort Collins
Stream Name
Mail Creek, McClellands Creek
Basin
South Platte
Title
Mail Creek and McClellands Basins
Date
12/4/1980
Prepared For
Larimer County
Prepared By
Cornell Consulting
Floodplain - Doc Type
Floodplain Report/Masterplan
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
24
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 />City of Fort Collins <br />December 4, 1980 <br />Page 3 <br /> <br />benefit/cost ratio must be greater than one for the plan to be <br />economically viable on the basis of flood control. The larger <br />the ratio, the more efficiently funds are being utilized for <br />flood control purposes. <br /> <br />Examination of the floodplains and benefit/cost data while <br />keeping in mind the goals of the study leads to the selection <br />of one alternative plan for each reach as the overall most bene- <br />ficial. A review of the flood plain conditions reveals that flood <br />damage in both the Mail Creek and McClellands study reaches is <br />localized, due primarily to specific structures or channel segments <br />which are inadequate for the design flows. Several reaches are <br />located in undeveloped areas and design flows are contained within <br />the existing natural channel resulting in minimal flood damages. <br />Where existing natural channels are adequate, it is because of the <br />basin topography and the fact that upstream development has been <br />orderly and considerate of storm drainage; detention is widespread. <br /> <br />Because of the nature of the flood hazards and potential damages <br />in Basins I & K, it is not surprising the the alternatives which <br />have the highest benefit/cost ratios are those which address specific <br />problem areas. The selected structural improvements in Reaches <br />lB, lC, and McClellands, which consist of improvements to culverts <br />and street crossings are the most effective. Similarly, in <br />Reaches 2, 3, 4 and 5, those selected structural alternatives have <br />the highest benefit/cost ratios because of the localized nature <br />of the flood damages. <br /> <br />Because of the City's policy requiring detention with development <br />and because detention enhances the B/C ratios in downstream reaches <br />by reducing construction costs, detention alternatives were considered <br />separately and in combination with local structural improvements. <br />Starting with a total of 14 detention ponds in Mail Creek and 3 in <br />McClellands, the number and size of the ponds were systematically <br />reduced until estimated construction costs became'reasonablein comparison <br />with potential benefits. We used the SWM~1 program to model the down- <br />stream effects of the proposed detention ponds. After modeling <br />several arrangements and discharges, three detention ponds in Mail <br />Creek and none in McClellands appeared cost-effective. <br /> <br />It is important to note that the cost effectiveness of the detention <br />ponds used strictly for flood control is not that good. In consider- <br />ing implementation of detention alternatives, therefore, multiple <br />use facilities should be envisioned. By using the sites for parks <br />and recreation opportunities, water quality control points, and <br />other activities, the ROW acquisition and construction costs <br />attributable to flood control would be reduced, raising the B/C <br />ratios. <br />
The URL can be used to link to this page
Your browser does not support the video tag.