My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
REV15451
DRMS
>
Back File Migration
>
Revision
>
REV15451
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/25/2016 1:26:46 AM
Creation date
11/21/2007 11:05:31 AM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
C1982057
IBM Index Class Name
Revision
Doc Date
2/26/1999
Doc Name
SENECA II-W PN C-82-057 PR2
From
DMG
To
SENECA COAL CO
Type & Sequence
PR2
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.
/
6
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
Seneca II-w. PIi~' <br />February 26, 1999 <br />Paec ~ <br />should continue to be monitored. Please incorporate [his site into the current surface <br />water monitoring program. <br />28.-32. Responses accepted. <br />33. To verify the projected impacts to the Wadge overburden and coal seam aquifers. <br />groundwater monitoring down gradient of the proposed pit areas in the II-W South area <br />will be required. This may be accomplished by installing and monitoring one overburden <br />groundwater well down gradient of the proposed pit areas in the II-W South extension <br />area, and by continuing to monitor existing wells 4W and 4WC in the II-W South area. <br />Please refer to item nos. 23. and 26. above. <br />34. Based on the information presented in Table 17-42a, it appears that the projected <br />dissolved solids concentration will result in exceedances of the Division's material <br />damage suspect levels. The salinity suspect level for the Yampa River Basin is I.0 <br />millimhos/cm for specific conductance. Postmining TDS concentrations as high as 1, <br />888 mg/1 are predicted for Hubberson Gulch. This would equate to specific conductance <br />concentrations in excess of 2.0 millimhos/cm. <br />A postmining TDS concentration of 1,650 mgll is shown for Site WSWTF2 located on <br />Watering Trough Gulch. It appears that this site is located upstream on Watering Trough <br />Gulch outside of any potential impacts from mining. Please explain how the postmining <br />concentration of 1,650 mg/1 was calculated for this location. Please also provide an <br />explanation of how the postmining TDS concentration of 1,336 was determined for site <br />WSDS on Dry Creek. <br />An evaluation of crop productivity declines is presented. In the discussion, SCC explains <br />that the grass hay fields were not included in the vegetation survey, yet SCC concludes <br />that since most hay fields in Routt County produce a mixture of smooth brome, timothy, <br />orchard grass and barley, this field must also. Please verify the crops grown with the <br />landowner. <br />Crop verification is critical, because the data presented by SCC shows that there will be <br />material damage to the hay field from the mining operation. Different crops have <br />different salt tolerances that will impact the productivity and resulting material damage <br />assessment . Based on SCC's calculations, the decline in crop productivity will be 3.3%. <br />This is based on salinity threshold values and yield decrease values for barley and <br />orchard crass from the D~IG's 1988 Material Damage Assessment Process (page 4). <br />Where did the values For smooth brome come from? No values for timothy are presented <br />in Table 17-43a, yet the text on page 112a indicates "experimental" values were used. <br />Threshold ranges and yield decrease ranges for these species are presented in a study <br />titled, "Crop Salt Tolerance Study -Phase II". I can provide a copy of this document for <br />SCC if necessary. It will be important to determine the actual crops grown and ttse <br />acceptable values for those crops to assess potential material damage. <br />35. Response accepted. <br />
The URL can be used to link to this page
Your browser does not support the video tag.