My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
REV94677
DRMS
>
Back File Migration
>
Revision
>
REV94677
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/25/2016 3:20:01 AM
Creation date
11/21/2007 11:42:24 PM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
C1981010
IBM Index Class Name
Revision
Doc Date
2/21/1992
Doc Name
AFFIDAVIT OF PUBLICATION & LEGAL NOTICE
Type & Sequence
TR58
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.
/
4
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 />Memo - Cathy Begej - C-80-006 - 2 - June 15, 1990 <br />2. If mining proceeds to Pit 2, overburden geochemistry sampling needs to be <br />done prior to the start of mining; not as mining proceeds. KCC has <br />presently cononitted to no overburden sampling in the Pit 1 area and <br />overburden sampling in Pit 2 which would only identify possible <br />problems. A selective handling plan would only be developed if secondary <br />sampling (surface to a depth of four feet on regraded overburden) <br />indicated that mixing of overburden was not sufficient to solve the <br />problem (see pages 780-70aaa and 780-70aaaa for details). This scheme <br />may answer problems to plant growth caused by sodic and/or acid <br />overburden in Pit 2. However, once backfilling proceeds to this point, <br />it will be too late to do anything about deeply buried overburden which <br />may affect ground water. <br />3. KCC's numbers on the amount of topsoil available in stockpiles and thie <br />minor amount still to be stripped indicate that they have just enough to <br />spread 6 inches on all remaining disturbance in the area. I have not: yet <br />been able to check to see if Tabtes 57 and 58 or maps 31a and 32 have <br />been updated to indicate the changes in the topsoil handling plan. <br />4. KCC may need to update page 780-19aa to indicate changes in the <br />Overburden Stockpile section. <br />5. Pre-mining contours are needed on Map 38 for Approximate Original Contour <br />comparisons. <br />None.of the tables submitted on April 20, 1990 have a revision date on <br />them. <br />7. Table 74a-Pit Volume Calculations indicate that Pit 1 volume is <br />4,214,100 CY yet it will only be backfilled with 1,795,000 CY. Are they <br />really this short of overburden? If so, it may pay to get a commitment <br />that if mining proceeds in Pit 2, overburden from Pit 2 will initia lly be <br />backfilled into Pit 1 and mining proceed from there. <br />8. Timetables for backfilling and reclamation of the 720 Pit do not <br />coincide. See page 780-3ccccccc versus page 780-62bb. You may want to <br />check the Settlement Agreement to see if a timetable and/or minimum <br />amount of backfilling was ordered by the MLR Board prior to signing off <br />on the 300,000 CY backfilled per year as proposed in TR-07, <br />9. I cannot help but point out that, in the last paragraph of page 780-68aa, <br />KCC dedicates equipment that has reached the end of its economic use life <br />to exclusively backfilling the 720 Pit. <br />I have more concerns relating mainly to overburden geochemistry and sampling <br />that will be covered at a later date. It is also a fairly uncomfortable <br />position for me to be in to review just a part of the entire April 20, 1990 <br />KCC submittal since this small part is related to other parts of the submittal <br />and the presently approved Permit Application. I believe that if we approved <br />just the pages you have highlighted it may tend to make a permit document that <br />would be somewhat contradictory. I would encourage KCC to clearly state which <br />parts of the submittal they want considered now and which parts later. <br />/e rn <br />cc: Susan McCannon 7906F <br />
The URL can be used to link to this page
Your browser does not support the video tag.