My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2012-12-17_REVISION - M2004030
DRMS
>
Day Forward
>
Revision
>
Minerals
>
M2004030
>
2012-12-17_REVISION - M2004030
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/15/2021 6:00:12 PM
Creation date
1/3/2013 8:04:51 AM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
M2004030
IBM Index Class Name
REVISION
Doc Date
12/17/2012
Doc Name
Adequacy Review-02 Response
From
T Bone Stone, Inc.
To
DRMS
Type & Sequence
CN1
Email Name
MAC
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.
/
6
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
Mr. Tenore <br />Page 12 <br />October 2, 2012 <br />No comment. <br />6.4.3 Exhibit C — Pre - mining and Mining Plan Map(s) of Affected Lands <br />3. The Mining Plan Map does not portray all adjoining surface owners of record as required by <br />Rule 6.4.3(a). Please revise the Mining Plan Map to include this information. <br />see revised T -Bone Stone, Inc., Mining Plan Map. Adjoining surface owners shown along <br />property boundaries. John Bell was notified in error (his property is not within 200 feet of the <br />area affected by quarry operations). J.C. Burdick has ingress /egress easements over the roads <br />above the quarry and through the lower processing area of the quarry that is not in an area <br />affected by the quarry operations. <br />4. The Mining Plan Map does not contain a scale. Please revise the Mining Plan Map to include <br />a scale. As required by Rule 6.2.1(2)(e), the acceptable range of map scales shall not be <br />larger than 1 inch = 50 feet nor smaller than 1 inch = 660 feet. <br />Scale is now shown on both maps: 1" = 240.63' <br />5. As required by Rule 6.4.3(c), please revise the Mining Plan Map to include the name and <br />location of all creeks, roads, buildings, oil and gas wells and lines, and power communication <br />lines on the area of the affected land and within 200 feet of all boundaries of such area. <br />REA Utility lines are now shown on both maps. <br />6. The Mining Plan Map did not contain a title. Please revise the Mining Plan Map to include a <br />title. <br />see revised maps with new titles. <br />7. As required by Rule 6.4.3(g), revise the Mining Plan Map to show the owner's name, type <br />of structures and location of all significant, valuable and permanent man -made structures <br />contained on the area of affected land and within 200 ft. of the affected land. <br />Fences along western and southern property lines were installed by Mike Loukenon several years <br />before 112 Permit expansion application; no expansion is planned within 200' of the fences. <br />8. The Mining Plan Map outlines areas of existing and future excavations. In addition, the <br />Mining Plan Map states the entire 25 acres will be bonded, which indicates the Operator <br />intends to excavate outside of the depicted excavation areas. Please revise the areas of <br />existing and future excavations on the Mining Plan Map accordingly. <br />The total proposed permit area is approximately 25 acres, approximately 5 acres on the property <br />have been affected by quarry operations to date (excluding processing areas), primarily in the <br />northwestern area of the parcel. The quarry expansion proposed is in the southern and eastern <br />portions of the original quarry sites, with a new quarry area proposed east of TBS2 (3.6 acres), <br />and an area south and east of TBS 1 to be staged at some point in the distant future (4.6 acres). <br />The Operator is making arrangements to secure a reclamation bond in the amount of $68,574.00 <br />(Option CN -01), as determined by the 10 -acre Cost Summary dated 11/15/2012. <br />6.4.4 Exhibit D — Mining Plan <br />
The URL can be used to link to this page
Your browser does not support the video tag.