My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
APPCOR10566
DRMS
>
Back File Migration
>
Application Correspondence
>
1000
>
APPCOR10566
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/24/2016 6:26:57 PM
Creation date
11/19/2007 2:11:39 PM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
C1989074
IBM Index Class Name
Application Correspondence
Doc Date
3/20/1990
Doc Name
ADEQUACY ISSUES RIMROCK MINE PN C-89-074
From
MLRD
To
RIMROCK COAL CO
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 />i -- , <br />Rule 2.04.9(1)(c) - Soil Resource Information <br />The information provided is a major improvement over the original information <br />and will be suitable for determining the extent of the soil available for <br />reclamation. However, for the purpose of a complete and comprehensive permit <br />application with adequate baseline date and maps, the operator should provide <br />a map which delineates the extent of the Ayon and Capulin soils. The map <br />submitted uses range site descriptions which apparently correlate with the <br />soil types. The Division believes it would be more appropriate to show the <br />soil delineations with soil unit names attached instead of range site <br />descriptions. <br />Also, the SCS in Trinidad has informed the Division that the "Basalt Breaks" <br />range site should be "Cobbly Foothills" instead. Therefore, on the soils map <br />the "Basalt Breaks" alias "Cobbly Foothills" should be Ayon soil type and the <br />"Loamy Plans" should be the Capulin soil type. The SCS also submitted <br />additional description information concerning the soil type, and range sites <br />which probably should be inserted into the permit as baseline information. <br />Rule 2.04.10 <br />The application does not contain adequate vegetation baseline data. In order <br />to evaluate the success of revegetation efforts, the Division needs a baseline <br />vegetation study which describes on-site plant communities in term of species <br />composition, vegetative cover and productivity and woody plant density. <br />Reference is made to data in Exhibit H. However, the species numbers in the <br />text are not contained in Exhibit H. The production figures in the text do <br />not agree with those in the exhibit. Review of this site specific information <br />may precipitate further questions on the revegetation plan. <br />Rule 2.05.3(4) <br />The design presented for the permanent diversion of the Engelville Gulch was <br />inadequate to handle the 100-year, 24-hour peak flow. The Division requests <br />you submit an alternate design that will safely pass the 10-year, 24-hour <br />event which will constitute a temporary diversion. <br />Also the permanent diversion of Engelville Gulch will have to be removed from <br />all narratives of the permit application. <br />The statement on page 5 of Section 2.05.3(1) and (2) that "the sediment pond <br />will be converted to a stock pond when all mining activities cease" should be <br />revised to indicate compliance with Rule 4.05.6(12), i.e. ponds shall not be <br />removed until the disturbed area is reclaimed and it is demonstrated to the <br />Division that the requirements of 4.05.2(2) are met. For ponds proposed to <br />remain as permanent structures, it must be demonstrated to the Division that <br />the requirements of 4.05.9 are met. <br />Though the calculations for the sizing of the sediment pond appear to be <br />adequate there is still a lack of proper design and contour information with <br />plan view. All drawings used to establish the requirements of 4.05.6(3) shall <br />be included in the permit application. <br />
The URL can be used to link to this page
Your browser does not support the video tag.