Laserfiche WebLink
<br />Mr. Jeff Schwarz <br />December 4, 2001 <br />Page 2 <br /> <br />an aerial base map vvi[It topography superimposed. One can see contours, which irregularly define a <br />depression adjacent to the Flood control levee. This Reclamation Plan mapping was based on the Gingery <br />and Associates, 1977 mapping ([his mapping was also utilized for [he flood insurance study). <br />Point 3 <br />Part A Geomorphic Analysis <br />On October 10, 2001, [prepared and submitted to you a forensic analysis of the bank failure and stream <br />capture by the pre-existing Bull Seep Slough. Tom Schreiner mentions a failure of a Flood control levee <br />in his letter of November 21, 2001. Specifically, the implication of a flood control levee is that such a <br />feature was an engineered structure. In the case of the May ~, 2001 failure, the actual area that failed was <br />a'`rebuilt stream bank". This same location had tailed in the past and this bank failure resulted in the Bull <br />Seep Slough. The Bull Seep Slough was a depression and often contained standing water in many, if not <br />all of the post 1972 aerial photos. To the best of my knowledge, (1) this reconstructed bank was not <br />engineered and (2) [he "builders" of this "bank" did not prepare any "as-builts" or perform any quality <br />control during construction. It is my understanding that the material used in this bank fill was a <br />combination of unclassified (silts, sands, gravels and clays) materials derived from the Macintosh <br />property. It is also my understanding that broken concrete and construction debris was part of the <br />construction fill. Based on the nature of this fill, it is unlikely that the material placement would meet <br />modem construction standards attd therefore should not be referred to as "a flood control levee". <br />My letter of October 10'" presented a historical analysis of [he fluvial system (see Figure 2.1). This figure <br />suggests that the reach where the 2001 bank failure occurred is a very dynamic stream reach. Review of <br />Figure 2.3 illustrates that in-channel gravel mining occurred upstream of the Bull Seep Slough, beginning <br />sometime after 1973 and ending around 1983. Gravel mining also occurred near the Bull Seep Slough's <br />outlet to the South Platte River (i.e., the Hazeltine Pit). This is documented in several aerial photos of <br />1960s vintage. In-channel mining significantl}• affected sediment transport and channel morphology. In <br />my letter of October 10'h, [also noted that the "artificial grade control" known as the 8ranmer Diversion <br />Dam influenced the channel morphology of our reach of interest. <br />1 have included Figure 2.2 to illustrate the qualitative impacts of "in channel mining" and the presence of <br />a grade control such as the Brantner Diversion Ditch. In summary ,upstream "in-channel" mining will <br />trap sediment and will release "hungro water". This "hungry' water will be erosive and will result in <br />channel bed degradation and/or bank erosion. Bank erosion typically results in an increase in the <br />channel's tendency to meander or increase in sinuosity. Since the channel grade is controlled at the <br />Brantner, bed degradation is minimal. Therefore, the net response to "in-channel mining" is bank erosion <br />or an increase in the channel's sinuosity. <br />Figures 2.4 and 2.5 provide an historical analysis of the changes that have occurred through time in the <br />reach of interest. The bank line analysis illustrates a decrease in channel slope through an increase in <br />channel length. The erosional processes which are associated with these changes in channel morphology <br />result in the development of bars. As the channel becomes more sinuous, the material eroded from the <br />outside of a bend is deposited along the inside of the next downstream bend. As the bar continues to <br />grow, the flow often becomes more tbcused resulting in a more direct line of attack on the outer bank of <br />the next downstream bend. <br />