My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
PERMFILE48665
DRMS
>
Back File Migration
>
Permit File
>
500000
>
PERMFILE48665
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/24/2016 10:50:36 PM
Creation date
11/20/2007 1:43:04 PM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
M2000050
IBM Index Class Name
Permit File
Doc Date
4/25/2000
Doc Name
BROKEN SPEAR PIT FN M-2000-050 RESULTS OF ADEQUACY REVIEW OF 110 PERMIT APPLICATION
From
DMG
To
BARNHART AGENCY INC
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.
/
5
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 />200 feet of the permit/affected land boundary. If the proposed permit area is intended to be limited to the SE'/+ NW <br />'/. of Section 7 but lies within 2lN) feet of adjacent property indicated to be owned by someone other than the <br />Allens, that adjacem owner(s) should be idemified on the map and evidence of notifying this adjacent owner(s) uF <br />the application should be provided prior to the decision date for the application. If the proposed permit area is <br />intended to be limited to the SE'/. NW '/+ and you agree that the permit area is not accurately located on the <br />application maps, then a revised Exhibit A and revised Exhibit E mops should be provided with the proposed <br />permit area correctly located. If the proposed permit area is nut intended to be limited to the SE'/+ NW !~i of Section <br />7, then ownership of the surface and subsurface rights to the NE'/+ SW '/+ of Section 7, into which the permit area <br />apparently extends, should be identified, together with the Allens, on Page 2 of the application form and a right of <br />entry onto this property for mining purposes must be included in Exhibit G of this application. <br />EXHIBIT B (Rule 6.3.2 (b)): The application narrative states that there are no significant man-made <br />structures within 200 feet of the permit/affected land boundary. Fences qualify as such structures and are often <br />overlooked in permit applications. There is a map (See copy attached to this review.) in the file for the nearby Ellis <br />Allen Pit (Permit M-84-I85) operated by Lincoln County which seems to indicate the presence of a fence just <br />northeast of the proposed permit area for the Broken Spear Pit. <br />Please confirm that there is no fence located northeast of and within 200 feet of the proposed <br />permit/affected land boundary. If there is, the various maps in the application should be revised and the owner of <br />the fence identified. <br />EXHIBIT C (Rule 6.3.3 (b)): There is nothing in the application narrative [hat indicates if the topsoil <br />salvaged from the pit margins will be used in reclamation immediately after salvage or if it will be stockpiled and. <br />therefore, require stabilization until put to reclamation use. <br />Please indicate if the salvaged topsoil will be used for reclamation purposes immediately after stripping or - <br />if it is intended to stockpile this resotuce. If stockpiling is intended, please commit to stabilizing the stockpile(s), <br />indicate how this will be accomplished and provide a revised Exhibit E-Mining Plan Map that indicates where the <br />topsoil stockpile(s) will be located. <br />EXHIBIT C (Rule 6.3.3 (c)): The application indicates that there is overburden material in the pit banks <br />that may range up to 3 fee[ in thickness and that [his material may be used in the "backsloping'", presumably as part <br />of [he shaping of the banks prior to topsoiling. There is, however, no indication in the application if stripping of this <br />overburden and its stockpiling are intended prior [o "backsloping'". There are no overburden stockpiles indicated on <br />the Exhibit E-Mining Plan Map. <br />Please indicate if stripping and stockpiling of overburden material aze intended. If they are, provide a <br />revised Exhibit E-Mining Plan Map that locates the intended overburden s[ockpiles(s). <br />EXHIBIT C (Rules 6.3.3 (e) and (g)): The Exhibit A and Exhibit E maps show only a single haul road for <br />the proposed pit yet mention is made of the use of a "Lincoln County gravel pit road" in part. The Division will <br />accept the existence of a haul road [o the Lincoln County pi4 but the relationship of the haul road to the proposed <br />pit and the haul road to the Lincoln County Pit is not illustrated on the Exhibit A and Exhibit E maps. While the <br />portion of the haul road leading [o the proposed Broken Spear pit is referred to as a ranch road, implying it is an <br />existing road, this portion of the road does end a[ [he pit and appears intended to serve primarily as an access haul <br />road for the pit. <br />Please illustrate the relationship of the haul road for the proposed pit and the "Lincoln County gravel pit <br />road" on revised Exhibit A and Exhibit E maps and confirm [hat the portion of the haul road leading directly to the <br />proposed pi[ is an existing ranch road. <br />EXHIBIT C (Rule 6.3.3 (j)): The Exhibit C narrative indicates that a Corps of Engineers 404 Permit will <br />be acquired and that it is the applicant s belief that this will eliminate any need for a Storm Water Discharge Permit <br />from the WQCD. There is, however, no evidence that contact is intended with the WQCD to confirm this. <br />Please commit to contacting the WQCD and confirming this assumption. <br />EXHIBIT C (Rule 6.3.3 (k)): The Exhibit C nazrative says that "No refuse, acid-forming or toxic materials <br />will be involved in this operation". The Rule, however, requires a description of how such shall be handled if <br />encountered and not whether such materials are expected to be encountered. <br />Please satisfy the requirements of the Rule. <br />
The URL can be used to link to this page
Your browser does not support the video tag.