My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
GENERAL34889
DRMS
>
Back File Migration
>
General Documents
>
GENERAL34889
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/24/2016 7:56:08 PM
Creation date
11/23/2007 8:05:08 AM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
C1984063
IBM Index Class Name
General Documents
Doc Date
2/1/1990
Doc Name
Proposed Decision & Findings of Compliance for RN1
Permit Index Doc Type
FINDINGS
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.
/
14
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
Since all disturbed-area runoff as well as mineflow from the Eastside site is <br />routed into a sediment pond, and since there have been no disc haraes from this <br />pond, there have clearly been no impacts of the operation on surface water <br />quality. The worst-case predictions of the original Eastside Probable <br />Hydrologic Consequences section would involve maximum sediment pond discharge <br />during the low flow of Harvey Gap drainage, and would result in an increase in <br />Total Dissolved Solids from 775 mg/1 to 1054 mg/1 (calculations in original <br />Findings Document). This impact would not affect irrigation, since the flow <br />in Harvey Gap drainage would be less than 1 cfs during the low-flow season <br />(non-irrigation season, October through early April). Containment of the <br />runoff from the 12 acres of disturbed area at Eastside will have nea_lia_ible <br />quantitative effect on the flows in Harvey Gap drainage. <br />The Probable Hydrologic Consequences section of the original Findings Document <br />also predicted negligible around water impacts, and this assessment is still <br />valid. Seepage of water into the workings has remained at less than 2 GPM and <br />is not expected to increase substantially with further mine development. <br />There have clearly been no detectable hydrologic impacts, based on study of <br />Annual Hydrologic Reports submitted by Eastside Coal Company from 1984 through <br />1988. <br />Cumulative Hydrologic Impact Study - Rules 2.05.6(3) and 2.07.6(2)(c) <br />A Cumulative Hydrologic Impact Study (CHIS) was completed for the Eastside <br />Mine and considers the hydrologic impact of all anticipated mining and <br />reclamation activities in the area of the proposed operation at the mine <br />during the permit renewal term. This CHIS is available in company with the <br />most current versions of other such studies under a separate cover in the <br />Permit Application File area of the Division. <br />Pursuant to Rule 2.07.6(2)(c} and in consideration of the absence of <br />demonstrated significant hydrologic impacts by the anticipated mining and <br />reclamation operations in the study area, either individually or cumulatively, <br />the Division finds the proposed operation at the Eastside Mine to have been <br />designed to prevent material damage to the hydrologic balance outside the <br />proposed permit area. <br />IX. Alluvial Valley Floors - Rules 2.06.8 and 4.24 <br />The original Findings Document for the Eastside Mine determined that farming <br />on alluvial valley floors would not be affected, that no material damage to <br />quantity or quality of alluvial valley floor water supplies was expected, and <br />that the essential hydrologic function of alluvial valley floors would be <br />preserved. There are no chances to this section. <br />The operation is in compliance with the requirements of this section. <br />X. Climatological and Air Resources Information - Rules 2.04.8, <br />an <br />No changes are required to this section of the Findings Document. The <br />operation is in compliance with the requirements of this section. <br />-8- <br />
The URL can be used to link to this page
Your browser does not support the video tag.