My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2015-04-14_REVISION - M1985029
DRMS
>
Day Forward
>
Revision
>
Minerals
>
M1985029
>
2015-04-14_REVISION - M1985029
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/15/2021 5:46:00 PM
Creation date
4/15/2015 8:51:40 AM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
M1985029
IBM Index Class Name
REVISION
Doc Date
4/14/2015
Doc Name
Adequacy Review No. 1
From
DRMS
To
High Mountain Mining Co., LLC
Type & Sequence
AM5
Email Name
MAC
TAK
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.
/
6
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
Mr. Murray <br />Page 3 <br />April 14, 2015 <br />acres has had topsoil (fines) replaced. Please clarify if topsoil still needs to be replaced over <br />the former 110 area of 11.8 acres. <br />9. The Mining Plan states the gravel operation will extract 1,100,000 tons of gravel from the <br />gravel mine area under Scenario No. .1. However, based on the projected amount of gravel to <br />be extracted from the gravel and gold mine area, a total of 1,230,000 tons of gravel will be <br />extracted. Please confirm that a total of 1,230,000 tons of gravel will be removed from the <br />gravel mine area. In addition, please confirm the final topography as depicted on Exhibit F -1 <br />is based on removing 1,230,000 tons of gravel. <br />6.4.5 Exhibit E — Reclamation Plan <br />10. The Reclamation Plan for the gold operations states that ponds #1, #3, and #4 will be <br />reclaimed to a single sediment catchment basin. Please confirm that this sediment catchment <br />basin will not contain exposed groundwater. Also, revise Exhibit F -1: Reclamation Plan Map <br />to include a label which specifies this pond will serve as a sediment catchment basin. <br />11. The Reclamation Plan states that the final cut of the gold operation, cut 47, will be reclaimed <br />as a lake. Exhibit G states that a 0.84 acre pond will be created from the last cut of the gold <br />operation. However, Exhibit F -1: Reclamation Plan Map depicts the 0.84 acre pond in the <br />vicinity of the existing pit for the gold operation. Please clarify the final location of the 0.84 <br />acre pond. <br />12. The topsoil handling plan for the gold operation calls for amending the fines used as <br />substitute topsoil and mulching the material during final reclamation. However, the <br />Reclamation Plan does not contain information on the type, rate and application method of <br />fertilizer and mulch. In addition,, the financial warranty estimate does not contain costs for <br />these reclamation tasks. Please specify the type, rate and application method for fertilizer and <br />mulch to be used during reclamation and revise the reclamation cost estimate as necessary. <br />13. The Reclamation Plan (page 49) states that all reclaimed areas will receive 2.5" to 3" of <br />topsoil or substitute fines. This appears to be in contradiction to other statements made <br />throughout the Application. The Reclamation Plan (page 48) also states that an average of 3" <br />of substitute fines would be applied to the reclaimed gravel operation, which implies a range <br />of 2" to 4" inches. In addition, the Operator has also committed to salvaging an average of <br />4.5" of topsoil from undisturbed areas. The Division understands that the gravel and gold <br />operations are conducted independently of each other. However, from the Division's <br />perspective this is a single mine site which should have a consistent reclamation plan across <br />the operations. Please clarify the average amount of topsoil and substitute fines to be <br />replaced for the whole operation. See additional comments under Items No. 5 -7. <br />
The URL can be used to link to this page
Your browser does not support the video tag.