My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
PERMFILE137697
DRMS
>
Back File Migration
>
Permit File
>
400000
>
PERMFILE137697
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/24/2016 10:38:19 PM
Creation date
11/26/2007 6:25:22 AM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
C1980007A
IBM Index Class Name
Permit File
Doc Date
4/8/2005
Doc Name
pages 2.05-157 to 2.05-267
Section_Exhibit Name
2.05 Operation and Reclamation Part 3
Media Type
D
Archive
Yes
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
87
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
Wes! Etk Mine <br />• Although MCC's increases for total iron appear noteworthy, inspection of the data <br />• indicates that these increases are not significant. During the two months that there were <br />stream standard exceedances for iron (March and April) even the ambient water quality <br />upstream from the mine exceeded the stream standard of 1.0 mg/L. Table 54 shows <br />that MCC's contributions to downstream total iron concentrations during March were <br />negligible (1 percent). In April, MCC discharges actually reduced the downstream <br />total iron concentration in the North Fork. <br />The largest total iron increase occurred in July, when the river upstream was 0.13 <br />mg/L and downstream from the mine was 0.17 mg/L. While this calculates to a high <br />percentage increase, the absolute increase was of no practical significance and the <br />resulting concentration was well below the stream standard. <br />• MCC's 1996 discharges to the North Fork did not affect the pH of the river. <br />• In addition to reviewing the water quality data for actual discharge events during 1996, <br />WWE considered a "worst case" scenario in order to project future PHC's associated <br />with mine discharges. The worst case scenario assumes the rare situation of: (1) both <br />ponds discharging simultaneously, as occurred in March 1996, and (2) winter low flow <br />conditions in the North Fork. Even under these extreme circumstances, where the <br />discharge flow comprises nearly one quarter of the downstream flow, the mixed total <br />iron concentration is still less than the stream standard. Also, the mixed TSS <br />• concentration of 21 mg/L is well within the natural variability of TSS in the North <br />Fork. The pH was unaffected by pond discharges under the worst case scenario. This <br />worst case scenario also considered the effects of the increase in the TDS concentration <br />on crops during the irrigation season, which is discussed in more detail in the following <br />section. <br />Impact of TDS on the North Fork <br />TDS levels in the North Fork are elevated under natural conditions. For example, in April <br />1996, the TDS concentration in the North Fork upstream from the mine was 316 mglL; <br />MCC's discharges increased the TDS concentration to 319 mg/L (based on mass balance <br />computations, see Table 54). <br />As shown in Table 54, all of the TDS concentrations downstream from the mine were below <br />any numeric standards for TDS that WWE has been able to locate, irrespective of the <br />beneficial use classification that is to be protected (Table 55). For comparison, the highest <br />TDS concentration calculated downstream of the mine during 1996 was 319 mg/L. Even <br />under the worst case scenario, the downstream TDS concentration was calculated to be 426 <br />mg1L (see Table 54), less than the most stringent limit shown in Table 55 (450 mg/L). <br />Under the worst case scenario, as shown in Table 54, the downstream mixed TDS <br />• concentration would be approximately 670 mg/L. This concentration would occur only during <br />2.05-200 Revisedlun. 1995 PR06: Revised Nov. /998 TR80; 1/98 PR08 <br />
The URL can be used to link to this page
Your browser does not support the video tag.