My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2010-08-02_REVISION - C1996083
DRMS
>
Day Forward
>
Revision
>
Coal
>
C1996083
>
2010-08-02_REVISION - C1996083
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/24/2016 4:17:21 PM
Creation date
8/3/2010 12:47:35 PM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
C1996083
IBM Index Class Name
REVISION
Doc Date
8/2/2010
Doc Name
3rd Adequacy Review Letter
From
DRMS
To
Bowie Resources, LLC
Type & Sequence
PR12
Email Name
JJD
SB1
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.
/
17
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
52. The information on revised page 2.05-120 and on Map 9 shows that there is no upstream monitoring <br />site for Steven's Gulch. An upstream monitoring site is needed to compare with the monitoring <br />information gathered at downstream monitoring site SW-5. Please propose a Steven's Gulch upstream <br />monitoring site or explain why such a site is impractical. <br />This issue is resolved. BRL added a new upstream surface water monitoring site, designated as SW- <br />11. In the July 8, 2010 submittal, pages 2.05-118 and 2.05-120 as well as Map 9 were revised. <br />53. A discussion of the Bruce Park Dam begins on page 2.05436 The permit text continues to refer to <br />the Bruce Park Dam, while the various permit maps use the name "Terror Creek Reservoir ". In the <br />interest of clarity, please consider adding, "and Bruce Park Dam " to the feature on the various maps <br />and/or modify the permit text to explain that the reservoir formed by the Dam is the Terror Creek <br />Reservoir. <br />This issue is resolved. BRl revised page 2.05-136 in the June 1, 2010 submittal. <br />54. Please explain why the creek in Steven's Gulch is not included along with Hubbard Creek and Terror <br />Creek in the discussions on revised pages 2.05-136 and 2.05-142. <br />This issue is resolved. Pages 2.05-136 and 2.05-142 were revised in the June 1, 2010 submittal. In the <br />July 8, 2010 submittal, BRL explained that the monitoring data for SW-5 show that Steven's Gulch is <br />a perennial stream. <br />55. Discussion of the Bruce Park landslide begins at the top ofpage 2.05-137. While the feature is <br />analyzed in detail in the referenced Yeh study, the location of the landslide is not apparent on Map 06 <br />- Geological Hazards. Please modify Map 06 to indicate the location of the Bruce Park landslide <br />feature. <br />This issue -is resolved. Map 06 was revised in the June 1, 2010 submittal. <br />56. The third paragraph on page 2.05-137 describes the Hubbard Creek road. Please update the text to <br />incorporate the new Hubbard Creek Fansite. <br />This issue is resolved. Pages 2.05-132 and 2.05-138 were revised in the June 1, 2010 submittal. <br />57. On revised page 2.05-137, BRL states that the Stevens Gulch road will be subsided and that the road <br />is protected where severe damage would occur by limited extraction. The Division does not agree that <br />Stevens Gulch road is protected by limited extraction areas from activities as proposed under PR-12. <br />Permit text on page 2.05-141 accurately describes the subsidence consequences and mitigation for the <br />Stevens Gulch road. Please correct the permit text on page 2.05-137. <br />This issue is resolved. Page 2.05-137 was revised in the submittal dated June 1, 2010. <br />58. The 3'-d paragraph on page 2.05-140 refers to the potential impact to the Bruce Park landslide of <br />mine-induced seismic activity. Please consider modifying this paragraph to include a reference to the <br />Yeh 2006 study. <br />This issue is resolved. Page 2.05-140 was revised accordingly in the June 1, 2010 submittal. <br />12
The URL can be used to link to this page
Your browser does not support the video tag.