My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
PERMFILE46723
DRMS
>
Back File Migration
>
Permit File
>
500000
>
PERMFILE46723
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/24/2016 10:48:50 PM
Creation date
11/20/2007 12:54:20 PM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
M1988112
IBM Index Class Name
Permit File
Doc Date
11/8/1988
Section_Exhibit Name
APPENDIX Q ADEQUACY REVIEW QUESTIONS AND RESPONSES
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.
/
55
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
<br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br />storm (varies from 29 to 41 ac-ftJ. In order to support the design <br />principal for containment, please submit either a revised pond capacity <br />volume or model documentation which indicates sufficient pond capacity <br />will be provided. <br />Response: The water balance table contained in Appendix G contains <br />cumulative storage requirements, i.e. normal storage plus <br />draindown or normal storage plus draindown plus 100 year storm <br />flows. The draindown estimate is fixed at 21 acre-ft, while the <br />100 year storm volume ranges from 5 to 13 acre-ft as the facility <br />is expanded. The range of total required storage volume to <br />contain all the variables is calculated to be 29 to 4l acre-ft <br />which is less than the 52 acre-ft capacity. A figure has been <br />added to Appendix G to show the pond storage fluctuation with <br />time. In addition, the water balance table shown in Appendix G <br />has been revised to explain each of the water balance components <br />in more detail. <br />Appendix G, Water Balance Table clarified 2/15(89. <br />39. The draindown volume of the heap leach pad was estimated to 6e 10 <br />gallons per ton of ore (approximately 20 cubic ft. or .74 cubic yds.). <br />Appendix G, Heap Leach Water Balance indicates that although only <br />700,000 tons of ore will be processed at any one time, the heap )each <br />pad is planned to contain up to 6.5 million tons of ore. Therefore, <br />the vo]ume of the total draindown of the maximum amount of contained <br />ore should be 6.5 mi 11 ion tons x 10 gallons per ton = 65 mi 11 ion <br />gallons. Please clarify. <br />Response: The operating concept for the leach facility is based on a <br />maximum irrigation rate of 700 gpm distributed as 0.005 gpm/sq. <br />ft. This criteria provides the basis for the pond sizing and <br />water balance. Based on these numbers, only 140,000 sq. ft. of <br />the heap surface will be under leach at any one time. Assuming <br />that this area was the uppermost lift, 5 lifts of ore would <br />underlie the area and approximately 700,000 tons of ore would be <br />under active leach. 700,000 represents the maximum tonnage under <br />leach at any one time and thus the source for the design <br />draindown volume used in the water balance calculations and pond <br />sizing. Under no circumstances will all 6.5 million tons of ore <br />be under leach at one time. <br />No application change necessary. <br />40. The solution containment ponds should include spillway structures <br />allowing for controlled release of solutions, rather than possible <br />embankment erosion and resulting failure, in the event that a storm <br />which exceeds the design event occurs. Please provide design <br />specifications, including embankment erosion control measures and <br />locations of spillway structures. <br />Response: BMR believes that spillway structures for the purpose of <br />channeling excess solutions from the solution storage ponds into <br />the natural drainage channel are potentially undesirable and are <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.