My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2013-03-11_REVISION - C2010089
DRMS
>
Day Forward
>
Revision
>
Coal
>
C2010089
>
2013-03-11_REVISION - C2010089
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/24/2016 5:14:46 PM
Creation date
3/11/2013 2:40:07 PM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
C2010089
IBM Index Class Name
Revision
Doc Date
3/11/2013
Doc Name
Preliminary Adequacy Review
From
DRMS
To
Western Fuels Association, Inc
Type & Sequence
TR1
Email Name
MLT
SB1
SLB
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.
/
9
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
Doug White, Western Fuels <br />C- 2010 -089 TR -01 PAR <br />Mar. 11, 2013 <br />Page 3 of 9 <br />(1.96 cfs) of pit water pumping, with the initial pool elevation at 5671.5 ft., the gated <br />valve elevation. SEDCAD calculated no discharge through the emergency spillway for <br />all four cases. <br />DBMS: Response accepted. <br />4. DBMS: The placement of the primary spillway in the as -built configuration of pond <br />NHN -001 differs from the design. The spillway has been placed west of the approved <br />location, closer to the inlet of Ditch NHN -001 West. This location may result in short- <br />circuiting of the pond. Please indicate, in accordance with Rule 4.05.6(6), how WFC will <br />ensure that the pond is not short - circuited with Ditch NHN -001 West inflows. <br />WFC: The approved Pond NHN -001 principal spillway was located approximately 290 <br />feet from the inlet of Ditch NHN -001 West. The as -built principal spillway was <br />relocated to accommodate alignment with the existing county road culvert, and is <br />approximately 215 feet from the inlet of Ditch NHN -001 West. This distance is closer <br />than the approved design of Pond NHN -001, but exceeds the distance approved by <br />DRMS in the design for Pod NHN -002, which shows the inlet of Ditch NHN -002 North <br />located approximately 160 feet from the principal spillway, still a sufficient distance to <br />prevent short circuiting. This assertion is reinforced in the approved permit in Appendix <br />2.05.3(4) as stated on page 6, "gated principal spillways, as designed for all three ponds, <br />prevent short circuiting." <br />DBMS: Response accepted. <br />5. DBMS: Please include design information for the emergency spillway channel to <br />indicate the flow depth and demonstrate adequate embankment height to ensure I ' of <br />freeboard, as required by Rule 4.05.9(7) (d). <br />WFC: The four SEDCAD runs for the as -built pond show no discharge through the <br />emergency spillway, therefore no emergency spillway flow is indicated for use in <br />calculating freeboard. The minimum freeboard resulting from there four SEDCAD runs <br />occurs during the 25yr -24hr seep holes closed case, where the peak pool stage elevation <br />is 5,676.62 ft. This provides for 2.88 feet of freeboard to the top of the dam at 5,679.5 ft. <br />The emergency spillway has been built to the elevation of 5,677.5, two feet lower than <br />the top of the dam embankment. The approved Pond NHN -001 design done by Arcadis <br />included a 25yr -24hr SEDCAD run assuming no flow through the primary spillway, <br />resulting in a flow depth through the designed 10 ft. wide, 2:1 side slope emergency <br />spillway of 0.18 ft. The resulting freeboard in such a scenario is 1.82 ft. In this worst <br />case situation, where the primary spillway would become blocked, the emergency <br />spillway as built would still have greater than the required 1.0 of freeboard. The <br />emergency spillway channel as -built is a rip- rapped trapezoidal channel, 10 ft. wide with <br />2h:Iv or flatter side slopes. <br />
The URL can be used to link to this page
Your browser does not support the video tag.