My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2008-09-08_REVISION - C1994082
DRMS
>
Day Forward
>
Revision
>
Coal
>
C1994082
>
2008-09-08_REVISION - C1994082
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/24/2016 3:36:07 PM
Creation date
9/8/2008 1:50:20 PM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
C1994082
IBM Index Class Name
REVISION
Doc Date
9/8/2008
Doc Name
Response to Preliminary Adequacy Comments
From
Seneca Coal Company
To
DRMS
Type & Sequence
TR37
Email Name
DTM
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.
/
12
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
Technical Revision 37 <br />Response to Adequacy Comments <br />Page 4 <br />them with a single map showing the revised watershed designations. Alternatively, the appropriate watershed designations could be added <br />to the new Exhibit 13-12.1A. <br />Response: Exhibit 13-12.1, Yoast Mine Watersheds, shows a conservative watershed area estimate that was used by <br />SCC for the designs of Ponds 012, 013 and 014. These designs were all completed in 1999 in accordance with Rule <br />2.05.3(4) of the Regulations of the Colorado Mined Land Reclamation Board for Coal Mining. The rule reads (a) <br />General `A general plan and detailed design plan shall be submitted for each sediment pond, impoundment, other treatment fadko, and <br />diversion proposed (emphasis added) to be constructed within the permit area. " (a) (i) (B) "Contain a description, map, prepared <br />according to 2. 10,... " Exhibit 13-4B, Pond 010 - Existing Watershed Conditions August 2006 (emphasis added) was also <br />prepared in accordance of Rule 2.05.3(4). As noted in the title, the drawing shows conditions as of August 2006. <br />Attachment 13-3A Part II contains references to this exhibit. These drawings are needed to support design and as-built <br />documentation in accordance with Rule 2.05.3(4). Consequently SCC believes that it is inappropriate to remove, or <br />update, either exhibit. Finally, Channel YPM-22 is shown on Exhibit 13-12.1A, Permanent Channel and Pond <br />Watersheds. Exhibit 13-3A, Part I (prepared for TR-37 [with a revision date of 02/08]) indicates that drainage areas <br />used in the SEDCAD demonstrations were measured from Exhibit 13-12.1A (see page 13-3A.1-2). Again, there is no <br />need to revise Exhibit 134B since the plan view of YPM-22 is shown on both Exhibit 13-12.1A and Exhibit 20-2, <br />Postmining Topography Map. <br />10. Please revise Appendix 13-12.3 with an updated channel design(s) for the YPM4, 4-1, 4-2, YPM-17 and Diversion 13A rystem of <br />channels that flow into Pond 013. There were no previous existing designs for Diversion 13A and it appears that that the existing <br />channel information to be retained for YPM4, 4-1, and YPM-17 do not match the new Pond 013 As-Built SEDCAD design <br />information for contributing areas and peak discharger <br />• Response: As noted above in SCC's response to Comment No. 3, Appendix 13-12.3 contains channel des s. The <br />approved designs are representative of the minimum configuration needed to convey the estimated runoff from a <br />proposed topography. Consequently, the approved demonstrations in this appendix should be designs for YPM-4, 4-1 <br />and 17, not the as-builts. Unfortunately, neither SCC nor the Division recognized that "designs" and "as-built" were <br />different earlier in the permit revision process. If SCC had recognized this issue earlier it would have proposed leaving <br />the original "designs" in Attachment 13-12 and, would have subsequently prepared as-built demonstrations (which <br />would have superseded the design demonstrations) as part of the bond release process. <br />To assure consistency with material currently in the PAP (e.g., the revised "designs" inserted into Attachment 13-12 as <br />part of TR-36 and TR-37, as well as, the inputs that were used for pond permanent feature demonstrations) the channel <br />demonstrations for YPM-4 and 4-1 have been revised. The design for YPM-4-2 was submitted as part of the March <br />2008 TR-37 package; the SEDCAD demonstration and channel designs start on page 13-12.3-241. An updated as-built <br />demonstration for YPM-17 which includes Diversion 13A was also included in the March 2008 TR-37 package (see <br />page 13-12.3-169). The original ditch design for Diversion 13A is found in the Pond 013 design demonstration (see <br />Appendix 13-12.1, Sediment Pond SEDCAD4 Design Results, starting on page 13-12.1-98). Diversion 13A is included <br />in the model network as Structure #2. <br />11. Since the recent slide activity at Pond 012, the configuration of the pond has obviously changed This was confirmed by the pond storage <br />capacity survey submitted May 28, 2008 forAbatement Step 1 of NOV CV-2008-001. In the new certified As-Built Report for <br />Pond 012 (Option 1) page 13-12A-1.4, SCC indicates that `Exhibit 13-6, As-Built Pond 012, presents the existing impoundments <br />configuration and structure elevations" This statement is no longer correct since the slide occurred after the submittal of TR-37 and the <br />configurations and stnrcture elevations have changed Please remove the revised Attachment 13-12A As-Built Report fmm the revision <br />application since this report is no longer appmpriate. As stated above in Item S, we recommend the two pond option (012 and 012A <br />in series) that should be designed in concert with the slide remediation plan and takes into consideration a smaller dimension for Pond <br />012. Please resubmit a new design for the two pond system accordingly. New certified As-Built Report and new As-Built Map far the <br />two pond option (012 and 012A design) will be required following construction.
The URL can be used to link to this page
Your browser does not support the video tag.