My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2012-01-13_APPLICATION CORRESPONDENCE - C2010089 (2)
DRMS
>
Day Forward
>
Application Correspondence
>
Coal
>
C2010089
>
2012-01-13_APPLICATION CORRESPONDENCE - C2010089 (2)
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/24/2016 4:47:25 PM
Creation date
3/23/2012 12:31:53 PM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
C2010089
IBM Index Class Name
Application Correspondence
Doc Date
1/13/2012
Doc Name
Preliminary Adequacy Review No. 3 (Emailed)
From
Marcia Talvitie
To
Murari Shrestha
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.
/
62
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
C -2010 -089 PARNos. 1- 1A -1B, 2- 2A -2B, 3 <br />New Horizon North Mine Page 21 of 60 <br />one PHC discussion be presented and that it be located in Section 2:05.6(3): Item reap€ h,e <br />in Allay -2011 response. <br />11. Map 2.04,7 -1 and Map 2.05.3(3) -1 show several surface water bodies within the permit area. <br />However, there is no discussion of these water bodies in the Site Specific Surface Water <br />Information section or in the Probable Hydrologic Consequences section of Section 2.04.7 <br />and 2.05.6(3). Please revise the appropriate permit text under Rule 2.04.7(2)(a) to include a <br />description, including ownership and use, of these water bodies. Depending on their use, <br />Rule 2.04.7(3), requiring alternate water supply information, may be applicable and these <br />water bodies may need to be added to the surface water hydrology monitoring program <br />required under Rule 2.05.6(3)(b)(iv). In addition, if water rights are involved, then, those <br />rights need to be protected under Rule 4.05.15, Please revise the text where necessary. <br />A discussion of the ponds was added, and the PHC discussion has been removed from <br />Section 2.04.7. rr�rrr r evoli7ed in Iiti %a i X 1 response. <br />12. As shown in the surface water monitoring data sheets in Appendix 2.04.7 -2; monitoring sites <br />SW -N202 and SW -N203 experienced flows throughout the year but no full water quality <br />analyses were completed.. Please explain. Item resolve in 111(�17®2011 response. <br />13. In Table 2.04.7 -5 on page 17 of Section 2.04.7, surface water monitoring station SW -N205 <br />is described as being inflow for Glasier Draw. However, referring to the topographic contour <br />lines on Map 2.04.7 -1, it appears that runoff from this site would flow southwest into <br />Meehan Draw, rather than into Glasier Draw. Please explain. <br />In the May -2011 response, WFC responded that SW -N205 is located on ail irrigation ditch <br />which flows northward. The irrigation ditch appears on Map 2.04.7 -1 of the Dec -2011 <br />response. Item resolved ire Uay-2111 and 3 c -201 l responses. <br />14. In the last full paragraph on page 23 of Section 2.04.7, reference is made to pond NHN -001 <br />and ponds NHN -002 through NHN =004. Please revise this text to show that there are three <br />ponds. tent r evoli =curl iii i1 rt1 # -2 i11 r sl)rrnst <br />15: In several instances in the permit application, reference is made to baseline surface water <br />hydrology data being located in the New Horizon 1 Area and the New Horizon 2 Area <br />permit applications. Please include all baseline information relevant to the proposed New <br />Horizon North Mine in the New Horizon North Mine permit application. <br />Additional water monitoring data from the NHl Mine was added to Appendix 2.04.7 -2 in <br />the May- 2011 submittal. However; please explain why baseline surface water monitoring <br />data from the NI-12 Mine that is referenced in the New Horizon North permit application was <br />not submitted as well. <br />
The URL can be used to link to this page
Your browser does not support the video tag.