My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2016-11-29_REVISION - C1982056 (2)
DRMS
>
Day Forward
>
Revision
>
Coal
>
C1982056
>
2016-11-29_REVISION - C1982056 (2)
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
11/30/2016 9:27:08 AM
Creation date
11/30/2016 8:31:13 AM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
C1982056
IBM Index Class Name
Revision
Doc Date
11/29/2016
Doc Name
Adequacy Review #2
From
Twentymile Coal, LLC
To
DRMS
Type & Sequence
TR86
Email Name
JLE
DIH
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
Twentymile Coal, LLC. <br />Page 3 <br />11/29/2016 <br />127.1) to indicate that construction activities for the borehole option east of RCR 27 will not <br />occur within the restricted timeframes specified by CPW. <br />a. TC's Response: The referenced section has been reviewed and revised to clarify the <br />relevant wildlife mitigation considerations. The revised text pages accompany these <br />responses for replacement/insertion in the PAP. <br />b. Division Response: For the Sage Grouse section, TC removed the currently approved <br />mitigation narrative item #7 regarding exploration activities within the permit area and <br />replaced it with a generic statement about how activities will be limited within identified <br />buffer zones for active lek sites and then the reader is referred to project specific <br />consultation letters. TC provided the Division a copy of the consultation letter with CPW <br />for this project, however it is unknown if it was intended to have this letter included as an <br />exhibit to the permit as has been done for other revisions. As an exhibit to the permit, <br />please include the CPW consultation letter and the e-mail confirming with CPW that the <br />timing restriction for the proposed borehole pad option on the west side of RCR 27 does <br />not apply. Or, TC could add a narrative to this section addressing this proposed project to <br />specifically state the required mitigation measures. <br />Based on the CPW letter noted above, they recommended using two specific seed mixtures for re - <br />vegetation. These seed mixtures are similar to the Rangeland Seed mixture (Table 55) approved <br />for the site, however they are not the same. Please note that any change to the seed mixture <br />proposed for the site will need to be processed as a separate revision to the permit. <br />a. W's Response: Given that the CPW reference to seed mix is a recommendation, not a <br />requirement, and given the similarities in the seed mixture, TC plans to use the approved <br />rangeland mix for reseeding. <br />b. Division Response: Resolved <br />Based on the applicant's completeness response, when the application was submitted, the tie-in <br />point was unknown and now the tie-in point will be north of Haul Road C. Proposed revised Map <br />24 Sheet 1 does not show this tie-in location. Please revise Map 24 Sheet 1 to show where this <br />tie-in location will be. Also, Figure EX49K F 1 shows the thickener underflow pipeline route <br />approved with MR223. Based on the information provided to the Division, the new tie-in <br />location should be in this area depicted by Figure EX49K-F 1, given this, it would be appropriate <br />the update this figure. <br />a. TC's Response: Map 24 has been revised to reflect the tie-in location, and the revised <br />map accompanies these responses for replacement in the PAP. Given that Figure <br />EX49K F 1 is associated with a previously approved revision, we don't agree that it <br />would be appropriate to revise this figure to show the new information as this would <br />establish a very cumbersome precedent for continuous modification/revision of <br />previously approved information. <br />
The URL can be used to link to this page
Your browser does not support the video tag.