My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
PERMFILE63706
DRMS
>
Back File Migration
>
Permit File
>
700000
>
PERMFILE63706
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/24/2016 11:09:48 PM
Creation date
11/20/2007 8:09:03 PM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
M2006046
IBM Index Class Name
Permit File
Doc Date
1/3/2007
Doc Name
Response to 2nd Adequacy Review
From
Banks and Gesso, LLC
To
DRMS
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.
/
96
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
Applicant's Response to Second Adequacy Letter <br />Grand River Park Project, DRMS File M-2006-046 <br />January 2, 2007 <br />Page 3 <br />In its place, the formerly designated "clarification basin" will be revised to function <br />as a "regulating pond" for water management purposes (see Comment 21f <br />below). For reclamation cost estimating purposes, the differences in basin <br />function are not material, as the basic intent in both cases is to provide a <br />sufficient volume for short-term water storage and discharge flow-routing <br />capabilities. The regulating pond will require a 750,000 gallon capacity; with a <br />standard 1-foot freeboard and basin side slopes not to exceed 3H:1V, the <br />dimensions of the basin are anticipated to be approximately 200 feet by 200 feet <br />in plan view, by 3 feet deep. <br />11. In response to the applicant's request for the Division to provide feed back of <br />the applicants proposal "...to commit to mining the final slopes in excavated <br />areas adjacent to screening berms, such that subsidence may be presumed to <br />not be an issue in either the mining or post-mining condition.'; it would be <br />acceptable to the Division if the operator chooses to mine at a 3H:1 V slope to the <br />base of the screening berm. However, since the applicant has committed to <br />maintaining a mining setback distance of two times the depth of the pit, a revision <br />would be required to change the slope configuration adjacent to the screening <br />berms, should the applicant choose to do so after the permit is approved. As in <br />Item 9 above, the Division will determine whether the submittal will be a <br />Technical Revision or an Amendment when it is received. <br />As noted in the applicant's request for feedback concerning alternative locations <br />for screening berms, the intent of this dialogue is that "an appropriate degree of <br />flexibility in the placement of screening berms will be to the benefit of both the <br />operator and the neighboring property owner." Specifically, placement of the <br />berms in the alternative location (e.g., as a continuous slope set to the edge of <br />stable mine slopes, as opposed to a mining permit setback twice the depth of <br />excavation) would allow for a significant buffer of level ground between the <br />screening berms and the neighboring property. While the distance between <br />mining and the neighboring property will be the same in either alternative, the <br />conservative setback from mining for screening berms may result in a more <br />"crowded" aesthetic from the adjacent property, eliminating the off-site view of <br />open foreground. <br />The applicant's representative discussed this proposal in further detail with Carl <br />Mount of the Division on October 19, 2006. Based on this discussion, the <br />applicant understands the Division's concern that the operator commit to a stable <br />mining configuration. Also based on this discussion, we understand that it is not <br />the Division's intent to preclude flexibility if the stability and scope of alternatives <br />is clearly established by the applicant. <br />
The URL can be used to link to this page
Your browser does not support the video tag.