My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
ENFORCE37944
DRMS
>
Back File Migration
>
Enforcement
>
ENFORCE37944
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/24/2016 7:46:47 PM
Creation date
11/21/2007 3:50:02 PM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
C1982055
IBM Index Class Name
Enforcement
Doc Date
5/13/1993
Doc Name
ENERGY FUELS MINING CO RATON CREEK MINES ABATEMENT RESPONSES FOR NOVS C-93-46/48/52
From
ACZ INC
To
MLR
Violation No.
CV1993048
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
May 1993 L• II;C " nucn Creeh dines " NO V A6aizment Fapomes i 2 <br />Response: All of the noted culverts have been removed with the exceptions of those culverts <br />referenced in the NOV as items 3, 7 and 8. Hydrologic designs for culverts 3, 7, and 8 have <br />been completed and accompany these responses for insertion in the Permit Application <br />document. The drainage design information, and a Technical Revision application form together <br />comprise the Technical Revision ('I'R-08) application required for abatement. The noted items <br />accompany these responses for OMLR review and approval. <br />Abatement Step 9 - Submit a TR for the existing power(ine light use road as identified in TR-06 <br />Response: The design information previously provided in TR-06 does not match the az-built <br />configuration due to limitations imposed by the relatively steep topography. Field surveys will <br />be necessary to accurately determine actual configuration. In order to allow adequate time for <br />required field work, the abatement date for item 9 has been extended to June 26, 1993. <br />Abatement Step 10 - Submit a Technical Revision with appropriate designs for the catchment basin <br />Response: The referenced catchment basin was actually a check dam constructed of heavy <br />timbers with gaps between the timbers to provide for controlled Elow through the structure. <br />Given the existence and effectiveness of the two designed catchment basins upgradient from the <br />check dam, EFMC haz removed the check dam structure. <br />Abatement Step 11 -Submit an updated A4ap 12 identifying these stnrcrures <br />Response: As noted in [he response to Abatement Step 3 for NOV C-93-46 above, a draft copy <br />of revised Map 12, identifying the subject structures, accompanies these responses for OMLR <br />review and comment. <br />NOV C-93-52 -Failure to properly install sections of approved upland diversions. <br />Abatement Steps 1-3 - I) Install approved section of diversion, and, 2) Reconstruct portion of <br />diversion to drain into permanent watershed diversion as approved, or, 3) Submit a Technical <br />Revision to redesign diversions around substaziot: area to reflect existing site conditions and provide <br />a revised Nlap 12 to show southern diversion location and sections relative to approved designs, as <br />done for northern diversion <br />Response: The current drainage configuration in the vicinity of the substation area waz <br />reviewed and found to be less than optimal for effective drainage control, access, and <br />maintenance. The drainage configuration in this area has been redesigned az reflected by the <br />revised draft Map 12 which accompanies these responses. EFMC requests that OMLR review <br />the proposed drainage modifications and provide any comments prior to completion of fina] <br />designs. Given that EFMC is proceeding with Abatement Step 3 as an approved alternative to <br />Abatement Steps 1 and 2, the effective abatement date for submittal of revised designs is May <br />19, 1993 with submittal of final revised copies of Map 12 by June 25, 1993. <br />
The URL can be used to link to this page
Your browser does not support the video tag.