My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2020-06-16_PERMIT FILE - M2020007 (7)
DRMS
>
Day Forward
>
Permit File
>
Minerals
>
M2020007
>
2020-06-16_PERMIT FILE - M2020007 (7)
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/7/2025 7:47:25 AM
Creation date
6/16/2020 11:36:46 AM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
M2020007
IBM Index Class Name
Permit File
Doc Date
6/16/2020
Doc Name
Adequacy Review Response #2
From
Environment, Inc.
To
DRMS
Email Name
ECS
Media Type
D
Archive
No
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
109
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).
View images
View plain text
Environment, Inc. Page 2 <br /> Adequacy Response#2 June 11, 2020 <br /> M-2020-007 <br /> required. A cost to remove their concrete supports is included in the Reclamation <br /> Cost Estimate as concrete removal. <br /> The Mining Plan has been revised to explain this process and updated to match the <br /> mining plan revisions based on the proposed bonding discussed later in this <br /> response. <br /> Pit side and lateral berm widths/armoring — please see following comments under Exhibit E and <br /> address accordingly. <br /> See response for Exhibit E. <br /> EXHIBIT E - Reclamation Plan (Rule 6.4.5): <br /> The proposed mining and reclamation plan submitted states that a minimum of 150' will be <br /> maintained between the base of the existing berms/levee and the mining extent (top of pit), <br /> however no pit wall armoring or flood control structures have been included in the mining or <br /> reclamation plans. To insure that final reclamation configurations meet requirements for <br /> long-term stability, DRMS defaults to the recommendations provided within the UDFCD <br /> Guidance for Gravel Mining and Water Storage Activities Within or Adjacent to 100-Year <br /> Floodplains for sites adjacent to the South Platte River and its major tributaries. <br /> According to UDFCD guidance Table 2.1 River top Berm Width (page 27); even if DRMS <br /> assumed that the existing riprap on the bank of the South Platte met the specifications for <br /> riverbank protection, the minimum top width of the riverbank berm with no pit-side protection <br /> would be 250 feet. If both riverbank and pitside banks are protected according to the provided <br /> guidelines, the guidance states that a minimum rivertop berm width of 150 feet is acceptable. <br /> The armoring done along the river bank and the construction of a secondary <br /> protection berm done by landowners in the past is adequate for protecting the <br /> riverside bank from flooding. This is evident and proven as both the armoring and <br /> berm have been in place for many years and resisted both the 2013 flood event and <br /> the 2015 high water periods most recently. <br /> In response to the Division's reclamation recommendations noted above, L.G. <br /> Everist's in-house engineers prepared an analysis of the river along the west sides <br /> of Phases 1 and 2 and determined that the most advantageous way to proceed was <br /> to armor the pit side of the bank of both Phases because they lie in between the <br /> 250 foot and 150 foot setback as proposed in the Mining Plan. In Phase 1 this <br /> amounts to approximately 3195 linear feet and in Phase 2 approximately 1983 liner <br /> feet. <br /> L.G. Everist will commit to armoring the west banks of Phase 1 and the Phase 2 as <br /> shown on the Reclamation Plan Maps and as described in the Bank Armoring Plan <br /> that is attached. This will be done from the surface of the ground to a point 5 <br /> feet below the thalweg of the South Platte River with a face slope of 3h to 1v using <br /> concrete rubble with all exposed rebar removed, see Figure 1 in the Bank Armoring <br />
The URL can be used to link to this page
Your browser does not support the video tag.