My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2011-04-05_REVISION - C1982057 (2)
DRMS
>
Day Forward
>
Revision
>
Coal
>
C1982057
>
2011-04-05_REVISION - C1982057 (2)
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/24/2016 4:32:23 PM
Creation date
4/5/2011 10:35:33 AM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
C1982057
IBM Index Class Name
REVISION
Doc Date
4/5/2011
Doc Name
Preliminary Adequacy Review
From
DRMS
To
Seneca Coal Company, LLC
Type & Sequence
TR73
Email Name
SLB
SB1
MLT
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
22. On Section C-C', the existing Pond 016A impounding structure is centered at -Sta. 1+90. As <br />shown, the Proposed Surface will result in fill above the elevation of the current structure <br />and on the downslope of the structure. This configuration appears to contradict the text <br />description provided in the Pond 16 Area Stabilization Plan Summary (Page 3 of the <br />application), which states, under Pond 016A Removal, "a portion of the existing <br />embankment will be lowered/removed to drain the current pond and then be reconfigured <br />to fit the relocated Channel PM-2 design." Please clarify the text and/or map and cross <br />section to provide consistency within the application. <br />23. On Section D-D', please depict the location of Road J/K, as the Division also requests for <br />Sections B-B' and C-C', above. <br />24. Comparison of Section D-D' with the plan view on Sheet 1 indicates that Channel PM-2 will <br />cross this section at -Sta. 1+85. Please modify this section to accurately depict the <br />proposed location and configuration of channel PM-2. <br />25. The existing Pond 016 design and as-built report indicate that the riser height of the drop- <br />inlet spillway is 5', with a spillway invert elevation of 7,462.00'. The new design retains the <br />spillway invert height of 7,462.00', but indicates the riser height will be 2.5'. Is SCC <br />proposing to modify the drop inlet spillway? <br />26. The design submitted for Pond 016 includes the two stock tanks (T-26 and T-27) as sediment <br />control features. The previously approved language in the permit application package, on <br />page 11 of Tab 13, indicates that the stock tanks are not primary sediment control <br />structures. If SCC intends to rely on these structures to control runoff and sedimentation, <br />the language of Tab 13 will need to be revised accordingly. Also, SCC will need to submit <br />detailed design information, as required by Rule 4.05.6(5), indicating that Stock Tanks T-26 <br />and T-27 will comply with Rules 4.05.6 and 4.05.9. <br />27. If the stock tanks are an integral part of the runoff and sediment control system as indicated <br />in the proposed Pond 016 drainage area plan, they would need to be maintained at their <br />design capacity until SCC can make a demonstration, under Rule 4.05.2(2), that the quality <br />of untreated drainage from the disturbed area meets applicable water quality standards. <br />Both stock tanks are a considerable distance from LU-6 (T-27 is about 1,500' away-and T-26 <br />is about 500' away). SCC will need to address access to the stock tanks for maintenance <br />during the period of time that the stock tanks are necessary for sediment control. <br />28. The SEDCAD run for Pond 016 uses a curve number of 71 for reclaimed areas, based on <br />"good (>70%)" vegetative cover and a C type soil group. This value appears to be based on <br />approved input values found in the permit application package, in Appendix 13-513; the <br />tables in Appendix 13-513 are derived from NRCS TR-55. The vegetation monitoring reports
The URL can be used to link to this page
Your browser does not support the video tag.