My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2010-01-21_PERMIT FILE - M2009082 (11)
DRMS
>
Day Forward
>
Permit File
>
Minerals
>
M2009082
>
2010-01-21_PERMIT FILE - M2009082 (11)
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/24/2016 3:58:47 PM
Creation date
1/29/2010 7:46:06 AM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
M2009082
IBM Index Class Name
PERMIT FILE
Doc Date
1/21/2010
Doc Name
Response to Adequacy Review #1 Comments
From
Vecchi & Associates, LLC
To
DRMS
Email Name
JLE
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.
/
70
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
'I? <br />Page 10 of II <br />Mr. Jared Ebert <br />January 20, 2010 <br />Adequacy Review #3 Comments and Responses: <br />1. The Division did not receive copies of the PA04 series of borings. Please submit <br />copies of the boring for Division review. <br />The site plan showing boring information for the PA 04 series borings is the best <br />available information. <br />2. The screening berm and stockpiles are indicated as 7.5 feet in height in the stability <br />analysis models. The applicant must not construct the stockpile above the indicated <br />height used in the stability analysis during mining activities. The Division will <br />include the stockpile height as a permit condition. <br />We understand that this comment refers to the perimeter screening berms above the <br />mining highwall analyzed in the stability analysis. These screening berms do <br />stockpile soil but they are for screening purposes. We understand that the applicant <br />will need to commit to a maximum height of 7%2 feet for these perimeter screening <br />berms. However, the applicant cannot commit to this limitation for internal <br />stockpiles. <br />3. The Division does not consider the use of conglomerated data adequate to provide a <br />critical cross section and to determine the setback from critical structures. The <br />applicant must provide stability analysis for each individual boring(s) associated with <br />a critical structure. The Applicant must provide a proposal for a single general <br />setback or multiple setbacks, if applicable for a structure, based on the analysis <br />results. The Division recommends the applicant use the greatest setback distance <br />from a structure if multiple setbacks are indicated by the individual boring analysis. <br />Attached is a revised slope stability exhibit which addresses the setbacks. We have <br />also attached a revised Exhibit S to reflect the setback information contained in the <br />revised slope stability exhibit. <br />Whitney Ditch and WCR 64.5 - Phase IA Example <br />The applicant states a worst case cross section was used to evaluate the set back <br />distances for each phase during mining. In the individual cross sections for each <br />phases of mining, the applicant indicates the location of the worst case scenario for <br />each phase, however the soil profile analyzed for each phase is based on a <br />conglomeration of soil information from various borings not the actual worst case <br />scenario. <br />The applicant states the worst case scenario for Phase 1 A is represented by the north <br />mining highwall of the phase. The applicant used conglomerated data from ET02- <br />BH06, ET02-TP03, ET02-PI05, No. 1, No. 2 and MW-3 to determine the offset for <br />the Whitney Ditch and WCR 64.5. The Division agrees the north highwall is the <br />worst case scenario for Phase IA; however the applicant must perform individual <br />analysis for each boring and propose a setback from the critical structures based on <br />the individual results instead of the conglomerated data results.
The URL can be used to link to this page
Your browser does not support the video tag.