My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2015-06-02_REVISION - M2014045 (8)
DRMS
>
Day Forward
>
Revision
>
Minerals
>
M2014045
>
2015-06-02_REVISION - M2014045 (8)
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/15/2021 6:00:28 PM
Creation date
6/4/2015 8:15:51 AM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
M2014045
IBM Index Class Name
REVISION
Doc Date
6/2/2015
Doc Name
Responses to 6/2/2015 Comments CN01
From
Braun Environmental, Inc.
To
DRMS
Type & Sequence
CN1
Email Name
TC1
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.
/
18
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
Comment 4 Revise Section 7 so DRMS can determine potential acid generation <br />Response: <br />Additional discussion has added regarding the handling of potential acid generating <br />material, if it should ever be found. <br />Comment 5 Revise Section 10 so DRMS can determine Potential acid generation <br />Response: <br />The section has been modified to reflect the DRMS demand. Since the possible volume <br />(none found to date) of any potentially acid generating rock would be small, if found at <br />all, it can be easily managed underground without storing it on the surface. Thus, there is <br />no need for surface containment. <br />Comment 6 Geochemical Data and Analysis for Sample MH -3 <br />Response: <br />We are quite familiar with CC&V and their history with you. However, one thing you <br />are confusing is the source of their new iron sulfide and their solution with respect to <br />what we are dealing with. Recall back when you and I discussed the Mineral Hill project <br />being located within rock that is similar to the top of their original pit. Also remember <br />when you initially were adamant about the permit area on Mineral Hill being within <br />Precambrian rock, and recall that you were wrong. You might also not have full <br />understanding of the CC&V site and some of the nuances associated with their new <br />orebodies. The rock they want to be sending to their mill is not quite the same as at the <br />Mineral Hill site. <br />As already outlined in paragraph one of Section 7 in the Environmental Protection Plan, <br />the materials will be monitored, and will be tested if found to be potentially acid <br />generating. I believe that the plan is sufficiently detailed to protect the environment. Per <br />your Comment 4, a portion of this section has already been revised to provide a plan in <br />the event potentially acid generating material is ever found. <br />Comment 7 Map E -1A is Unacceptable, Unprofessional - Come on Mr. Braun <br />Response: <br />You are exactly correct that a map with those attributes would be unsuitable, especially if <br />it the print were too small to read and the scale did not fit within DRMS rules. However, <br />I did not submit that map for you to review, and it is somewhat of a mystery where you <br />would have come up with it. The fact is that two copies of the map were sent along with <br />my response letter dated February 10, 2015, to you via registered mail the next day on <br />February 11. I have the return receipt. I would have much preferred that you had just <br />called me so that we could have simply resolved this issue. If you had called, I could <br />have directed you to simply look through you own DRMS files until you found them <br />instead of trying to read something on a postage stamp. I find you words and <br />unprofessional behavior quite distasteful in this instance. However, at this point, this <br />issue is easiest resolved by us simply including two additional sealed maps. If you find <br />the other maps, you will have extras, and if not, you can no longer blame us. <br />
The URL can be used to link to this page
Your browser does not support the video tag.