My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
GENERAL40747
DRMS
>
Back File Migration
>
General Documents
>
GENERAL40747
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/24/2016 7:59:53 PM
Creation date
11/23/2007 10:50:39 AM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
C1980002
IBM Index Class Name
General Documents
Doc Date
4/4/1996
Doc Name
BOND FORFEITURE OHIO CREEK 2 MINE PN C-80-002
From
DMG
To
OSM
Permit Index Doc Type
RECLAMATION PROJECTS
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.
/
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
III IIIIIIIIIIIIIIII <br />999 <br />STATE OF COLORADO <br />DIVISION OF MINERALS AND GEOLOGY <br />Deparimenl of Natural Resources <br />1313 Sherman 51., Room 215 <br />Denver, Colorado 8020] <br />Phone: (3071 866-3567 . <br />FAX: 13031832-8106 <br />April 4, 1996 <br />Mr. Glen Golden, Civil Engineer <br />Office of Surface Mining <br />Western Regional Coordinating Center <br />1999 Broadway, Suite 3400 <br />Denver, Colorado 80202-5733 <br />Re: Bond Forfeiture -Ohio Creek No. 2 Mine (Permit No. C-80.002) <br />Dear Mr. Golden: <br />I~~~ <br />DEPARTMENT OF <br />NATURAL <br />RESOURCES <br />Roy Romer <br />Governor <br />lames 5. Lochhead <br />Ezeculive Director <br />Michael B. Long <br />Division DnKlor <br />This letter is provided to respond to your correspondence of March 28, 1996. It is our hope that <br />with this response, your agency can agree that the existing Ohio Creek No. 2 Mine reclamation <br />plan and bond are adequate. Our goal is to initiate the reclamation of the site as soon as possible. <br />Our responses are presented~t following the reiterated OSM question. <br />- Will the site be reclaimed in accordance with the approved permit reclamation plan? <br />It is our intent to reclaim the site in accordance with the existing permit reclamation plan. At <br />this time, we do not foresee any need for significant deviations from the plan. <br />- Ors 10/4/95, the permittee submitted a request to revise the "regrading and hydrologic control <br />plan. " Ors 10/16/95, DNR approved Technical Revision No. 04, which pertained to backfilling <br />and grading operations. Does Technical Revision No. 04 include the revisions to the regrading <br />and hydrologic control plan? In addition, other than a rescheduling of reclamation tasks, what <br />changes were made to the permit backfillirsg and grading plan as a result of Technical Revision <br />No. 04? <br />In general, Technical Revision No. 04 provided additional detail regarding the backfilling and <br />grading plan. This detail included material balance information, better mapping, and better site <br />cross-section information. The plan also provided post-mining drainage control details. <br />According to,finding X~7l, page 17, of the OSMJune 1987 Mining Plan Decision Documera, <br />portals are to have an MSK4 approved sea! and be backfilled and graded as shown in Exhibit 9. <br />An unsigrsed, undated sketch of the proposed portal reclamation was found in the permit, but <br />nowhere in the DNR files could there be found a certification attesting to the fact that the <br />portals were reclaimed as planned. State Rule 4.07 requires verification that underground <br />openings have been adequately reclaimed. What information is available, e.g. an engirseer's <br />certification, that would attest to the adequacy of the reclaimed portals? <br />To the best of our knowledge, the portals have been backfilled with a minimum of 25 feet of <br />inert material. It is also our understanding that the backfdl was placed against block seals. We <br />are not aware of any specific cer[i5cations to verify this work. <br />
The URL can be used to link to this page
Your browser does not support the video tag.