My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2011-06-07_PERMIT FILE - M2011015
DRMS
>
Day Forward
>
Permit File
>
Minerals
>
M2011015
>
2011-06-07_PERMIT FILE - M2011015
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/24/2016 4:34:16 PM
Creation date
6/7/2011 3:01:14 PM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
M2011015
IBM Index Class Name
PERMIT FILE
Doc Date
6/7/2011
Doc Name
Adequacy Review #2
From
DRMS
To
Azurite, Inc.
Email Name
JLE
AJW
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.
/
2
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
STATE OF COLORADO <br />DIVISION OF RECLAMATION, MINING AND SAFETY <br />Department of Natural Resources <br />1313 Sherman St., Room 215 <br />COLORADO <br />Denver, Colorado 80203 D IV I S I ON OF <br />Phone: (303) 866-3567 RECLAMATION <br />FAX: (303) 832-8106 MINING <br /> <br /> SAFETY <br />June 7, 2011 <br /> John W. Hickenlooper <br />Ken Klco Governor <br />Azurite, Inc. Mike King <br />P.O. Box 338 <br />Executive Director <br />Cotopaxi, Colorado 81223 Loretta E. Pineda <br /> Director <br />RE: Silver Cliff Pit; M-2011-015,112c Application Adequacy Review #2 <br />Dear Mr. Klco, <br />The Division received your response to the first adequacy review on June 6, 2011. The application decision date has been <br />extended to June 20th, 2011. Several other issues will need to addressed prior to the decision date. If you need additional <br />time to address the following concerns, it will be your responsibility to request and extension of the decision date. If there <br />are outstanding issues when the decision date arrives and no extension has been requested, the Division will deny the <br />application. <br />6.4.3 EXHIBIT C - Pre-mining and Mining Plan Map(s) of Affected Lands <br />1.) In regards to item 43 of the Division's first adequacy review, your response indicated four phases of the operation have <br />been delineated on the corrected Exhibit C map. However, only phase 1 and 2 are written on the map. Please label the <br />remaining phases and delineate the area for each phase on the map. <br />6.4.4 EXHIBIT D - Mining Plan <br />2.) If a noxious weed control and monitoring plan cannot be provided prior to the decision date, the Division will add a <br />stipulation to the approval of the permit. The stipulation will require that mining cannot begin until a Technical Revision <br />including a weed control and monitoring plan has been submitted by the Operator and approved by the Division. Please <br />keep in mind once the application is approved, the permit will not be issued until the financial warranty has been <br />submitted by the operator and approved by the Division. The Operator will not be able to revise the mining plan until the <br />permit has been issued for the site. <br />3.) In regards to the access road, the Division will hold a financial warranty to reclaim the road in the unlikely event the <br />bond is forfeited and the landowners want the road reclaimed. <br />6.4.7 EXHIBIT G - Water Information <br />4.) In response to item #25 and the need for a Temporary Substitute Water Supply Plan (TSWSP); if impounded storm <br />water is allowed to percolate into the surface within 72 hours after a storm event, a TSWSP will not be necessary. <br />6.4.12 EXHIBIT L - Reclamation Costs <br />5.) Item #9 indicates the highwall could be 800 feet long during the operation, however items #16 and #28 assume the <br />highwall length will only be 200 feet long. For the financial warranty calculation, for a single mining phase what will be <br />the maximum length of the highwall? <br />Office of Office of <br />Mined Land Reclamation Denver • Grand Junction • Durango Active and Inactive Mines
The URL can be used to link to this page
Your browser does not support the video tag.