My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
HYDRO31405
DRMS
>
Back File Migration
>
Hydrology
>
HYDRO31405
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/24/2016 8:55:07 PM
Creation date
11/21/2007 1:42:36 AM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
M1980244
IBM Index Class Name
Hydrology
Doc Date
12/5/1994
Doc Name
CRESSON PROJECT PN M-80-244 SUBMISSION OF ADDITIONAL EXPLANATION OF DATA ADDRESSING ACID
From
CRIPPLE CREEK & VICTOR GOLD MINING CO
To
DMG
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.
/
30
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
<br />Water Quality Standazds. Of course, the DMG does not set or enforce water quality <br />standards. However, the DMG does require that as a condition of minimization of impacts <br />to the hydrologic balance that operators meet all other Local, State, and Federal <br />requirements. In that regazd, the criterion upon which the DMG must measure effluents <br />generated within the mine permit boundary is surface and ground water quality standazds. <br />Thus, until the CDPHE indicates otherwise, process waters that do not meet water quality <br />standards must be controlled by the operator, either from forming or from dischazging." <br />Dr. Posey's discussion is flawed in two respects. First in the selection of water-quality <br />criteria upon which to judge the acceptability of runoff and second in the use of the term <br />"process waters." <br />CC&V assumes that Dr. Posey's position translates to a requirement to treat natural springs <br />and associated ground water, as well as natural surface waters to meet "Table Value <br />Standards" ("TVSs"). (TVSs aze obtained through site-specific application of the information <br />contained in the Water Quality Commission's regulations §3.1.16(1). Dr. Posey appears to <br />ignore ambient-based water-quality standards and the fact that Arequa Gulch is not classified. <br />As one result, he has selected a set of Table Values Standards and applied them to a stream <br />whose water quality is poorer than these arbitrary "Table Value Standazds." With experience <br />in water quality regulations, one recognizes that one can not be held to controlling anon- <br />point source discharge of water to standards that the receiving stream cannot meet. Water- <br />quality standazds aze, of course, site-specific and TVSs aze not assigned everywhere if <br />ambient water quality is poorer. <br />We point out that under the Water Quality Commission's regulations, specifically at <br />§3.1.7(1)(b)(ii), "Ambient Quality-Based Standards" are defined as follows: <br />"For State surface waters where the natural or irreversible man-induced <br />ambient water quality levels are higher than specific numeric levels contained <br />in Tables I, II, and III, but are determined adequate to protect classified uses, <br />the Commission may adopt site-specific chronic standards equal to the 85th <br />percentile of the available representative data. Acute standards shall be based <br />on table values or site-specific-criteria-based standards, and in no case may an <br />ambient chronic standard be more lenient than the acute standard." <br />Thus it is abundantly clear that in situations such as Arequa Gulch, ambient water quality <br />standards, when standards are established (see below), are justified. <br />Further, the Commission's regulations, at §3.1.6(1)(e), specify: <br />"Classifications should be for the highest water quality attainable. <br />Attainability is to be judged by whether or not the use classification can be <br />attained in approximately twenty (20) years by any recognized control <br />techniques that are environmentally, economically, and socially acceptable as <br />6 <br />
The URL can be used to link to this page
Your browser does not support the video tag.