My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
1993-09-02_REVISION - M1988112
DRMS
>
Day Forward
>
Revision
>
Minerals
>
M1988112
>
1993-09-02_REVISION - M1988112
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/20/2021 9:35:53 AM
Creation date
11/21/2007 1:36:03 PM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
M1988112
IBM Index Class Name
Revision
Doc Date
9/2/1993
Doc Name
BATTLE MOUNTAIN RESOURCES INC BMRI SAN LUIS PN M-88-112 TR8
From
BATTLE MOUNTAIN RESOURCES INC
To
DMG
Type & Sequence
TR8
Media Type
D
Archive
No
Tags
DRMS Re-OCR
Description:
Signifies Re-OCR Process Performed
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
3
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
<br />~i <br />will play in the Division's determinations regarding release <br />of reclamation liability and bond. In the course of the <br />July 2 meeting BMRI noted its objection to conditions 1 and <br />5 in that these conditions as proposed would impose <br />additional obligations on BMRI with no clear or objective <br />standards by which BMRI's compliance with the obligations <br />could be judged except for a demonstration "to the <br />Division's satisfaction". In addition BMRI representatives <br />questioned how the requirements of these conditions would be <br />integrated with the requirements of the new regulations <br />pertaining to groundwater impacts <br />of mining operations as promulgated by the Board on <br />March 25, 1993. Specifically, those rules contain <br />provisions relating to protecting uses, applicable <br />standards, monitcring requirements, the establishment~of <br />compliance points, and the release of reclamation liability <br />which would potentially overlap the issues covered by <br />conditions I and 5. As we noted at the meeting, BMRI does <br />not believe that it is in anyone's best interests to attempt <br />to address issues in conditions which will have to be <br />readdressed under the new regulations within a matter of <br />months. Candidly, the Division has not yet clearly <br />responded to these issues. <br />As we noted at the meeting, BMRI has no conceptual objection <br />to filing a technical revision as outlined by the proposed <br />condition 3. In our view such a filing would constitute a <br />"modification" and therefore under Rule 6.2.(3)(d) such <br />application could not be approved by your office unless it <br />includes conditions adequate to implement all applicable <br />ground water quality standards. we would suggest that such <br />a revision could provide the vehicle to resolve BMRI's <br />issues with respect to proposed conditions i and 5 within <br />the framework of the new regulations, while at the same time <br />concluding all issues related to compliance with the new <br />groundwater rules for the site and avoiding redundant 8nd <br />unnecessary reviews. For this reason we would propose that <br />conditions 1 and 5 be deleted and proposed condition 3 be <br />revised as follows: <br />3) BMRI will submit within 90 days following <br />final approval of TR-O8, a technical revision whi h, <br />when approved, will outline the manner in which BN~jRI <br />will demonstrate to the Division's satisfaction that <br />the quality of the ground water beneath the tailings <br />facility meets the applicable requirements of Rule <br />6.2.(3) prior to request by BMRI for full release of <br />reclamation responsibility and bond. The technical <br />revision contemplated in this condition will be <br />sufficiently comprehensive to reflect compliance with <br />all requirements of Rule 6.2.(3) for the site and <br />submitted under the intent of subsection 6.2.(3)(e) as <br />a voluntary application. <br />
The URL can be used to link to this page
Your browser does not support the video tag.