My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
FLOOD10335
CWCB
>
Floodplain Documents
>
DayForward
>
1
>
FLOOD10335
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/26/2010 10:13:03 AM
Creation date
10/19/2007 11:55:14 AM
Metadata
Fields
Template:
Floodplain Documents
County
Mesa
Stream Name
Indian Wash
Basin
Colorado Mainstem
Title
Watershed Work Plan - Indian Wash Watershed, Mesa County, CO
Date
9/1/1961
Prepared By
Upper Grand Valley Soil Conservation District
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.
/
59
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 />e <br /> <br />e <br /> <br />e. <br /> <br />.. <br /> <br />.. <br /> <br />,.., <br /> <br />~ <br /> <br />L <br /> <br />( <br /> <br />- 10 - <br /> <br />The only flood event on Indian \'iash for which there is an adequate <br />___record of peak-flow and-an estimate of monetary damages is the flood. <br />resulting fram the stonn of June 6, 1958. This stonn was concentrated <br />in the upper watershed area with-very little_rainfall i~_ the principal <br />damage areas located-downstream-frOIli the High LineCanat. The <br />precipitation recorded at the U. S. Weather Bureau Station at the <br />--- Grand Junction airport was -:0.63 -inch. <br /> <br />In their '~eport on Flood of 6 June 1958 on Indian Wash, Grand <br />Junction and Vicinity, Coloradd' dated August 1958, the U. S. <br />Corps of Anny Engineers estimated the peak discharge was 2,700 c.f.s. <br />in- the Indian Wash channel near. the High Line Canal flume-and the total-- <br />damages to be about $25,000. The principal damage was to residences, <br />business establishments, and streets as shown by p~otographs taken <br />during and after the flood (see Plates 1, 2 and 3). <br /> <br />( <br /> <br />The principal reason for the lack of reliable data concerning <br />previous flood damages on Indian Wash is that the build-up of residential <br />and commercial property in the area subject to damage has taken place <br />fairly recently, mostly since about 1955. Consequently, floods that <br />occurred at earlier dates were generally much less damaging than those <br />occurring more recently. Urbanization of agricultural land in the <br />damage area is continuing at a steady rate, and large floods occurring <br />in the future will have a much higher damage potential than floods of <br />similar size would have at the present time. . <br /> <br />Sediment and Erosion Damage <br /> <br />The higher peak discharges of floods on Indian Wash are accompanied <br />by large amounts of sediment derived mainly fram highly erodible lands <br />above the High Line Canal. The principal sediment damage results from <br />the deposition of silt, sand, and other debris on lawns, parking lots, <br />city streets, and in buildings, as well as on irrigated cropland and <br />in irrigation and drainage ditches. Removal of sediment and debris <br />fram lawns, streets, basements, and main floors of buildings in <br />particular involves considerable expense to the City of Grand Junction <br />and to private interests. <br /> <br />Sheet, gully, and streambank erosion are all major sources of <br />sedL~ent in the upper watershed area. They also act to reduce forage <br />production on the rangeland. Sheet and gully erosion are most <br />damaging in the areas where shale lies at or near the surface. Above <br />the High Line Canal, channel entrenchment into alluvial floodplain <br />deposits has occurred along Indian Wash and most of the larger <br />tributaries. Downcutting is reaching stability, but widening or the <br />channels through streambank erosion is still taking place. <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.