My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2011-08-10_APPLICATION CORRESPONDENCE - C2010088 (2)
DRMS
>
Day Forward
>
Application Correspondence
>
Coal
>
C2010088
>
2011-08-10_APPLICATION CORRESPONDENCE - C2010088 (2)
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/24/2016 4:36:44 PM
Creation date
9/8/2011 7:40:05 AM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
C2010088
IBM Index Class Name
Application Correspondence
Doc Date
8/10/2011
Doc Name
Adequacy Review Letter No. 3
From
DRMS
To
CAM Colorado, LLC
Email Name
MPB
SB1
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.
/
19
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
Corey Heaps <br />CAM Colorado LLC <br />August 10, 2011 Page 11 <br />feet of the railroad loop track but is protected only by ditch D2 -b. Please consider adding a <br />section of protective berm on the outside of ditch D2 -b in this area and revising Map 16 <br />accordingly. <br />CAM - The section near D2 -h is in cut, so a berm is not required. For clarity, contours have been <br />more clearly annotated on Map -16. For additional clarity, please see Map -21 section A- <br />A'. <br />Division Response: The Division requests that the discussion of the silt fences on <br />permit text page 2.05 -46 be updated to discuss all of the silt fences on site. <br />51. Item resolved. <br />Additional Questions regarding Haul Road #1 <br />51a. Typical Section on Map 15 - How will thickness of Pit Run be determined? Is there a <br />minimum thickness? No discussion is provided. <br />CAM - Please see revised Map 15, and text added to page 2.05 -13. Thickness of pit run will be <br />determined prior to construction. From and email from Ken Haley, City of Fruita <br />Engineer, "The City of Fruita would require that improvements are in place to <br />structurally support the amount of truck traffic proposed ". Similarly, DRMS Rule <br />4.03.1(5) requires haul roads be surfaced and designed according to the proposed volume <br />of traffic, weight and speed of vehicles. The section shown on Map -15 is based upon <br />haul roads constructed at other mines and used by similar trucks, with similar weights <br />and volumes. There does not appear to be a standard that must be followed for haul road <br />construction. If during construction, after placement of pit run, the road appears to <br />'pump' with heavy vehicle traffic, more pit run will be added until a stable foundation is <br />formed. Twelve inches minimum pit run has been specified, additional pit run could be <br />added if required by on -site conditions. <br />Division Response: CAM has adjusted the Pit Run thickness to be 12" minimum for <br />constructing Haul Roads #1 and #2, and states that more pit run will be added if <br />necessary to achieve stability. The cover letter response to this item indicates that the <br />City of Fruita Engineer requires only that "improvements are in place to structurally <br />support the amount of track traffic proposed." CAM indicates that the section shown <br />here is based upon haul roads constructed at other mines and used by similar trucks, with <br />similar weights and volumes. <br />CAM is correct that there is no particular standard that must be followed for haul road <br />construction. However, for roadways used by the traveling public, pavement sections <br />(including one or more types of road base) are typically designed using AASHTO <br />(American Association . of State Highway and Transportation Officials) procedures or <br />modifications thereof. of <br />thicknesses will vary depending upon the native soils, <br />climate, type of road base and/or pavement, type and volume of traffic, and the desired <br />
The URL can be used to link to this page
Your browser does not support the video tag.