My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2015-06-14_REVISION - C1981035
DRMS
>
Day Forward
>
Revision
>
Coal
>
C1981035
>
2015-06-14_REVISION - C1981035
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/24/2016 6:08:29 PM
Creation date
6/22/2015 7:27:35 AM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
C1981035
IBM Index Class Name
Revision
Doc Date
6/14/2015
Doc Name
Preliminary Adequacy Review
From
DRMS
To
GCC Energy, LLC
Type & Sequence
TR24
Email Name
MLT
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.
/
14
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
T. Bird, GCC Energy <br />C-1981-035 / TR -24 / AdegReview#1 <br />14 -Jun -2015 <br />Page 3 of 10 <br />paragraph may be considered confidential for purposes of these rules if the requirements <br />of Rule 2.07.5 are met.) <br />DRMS 06/14: The text was updated, as requested, to include the lease modification <br />presently being sought by GCC. In the midterm review, the Division should also have <br />requested that the portion of existing Lease COC -63920 within the OSM permit area (Ute <br />Mountain Tribe surface) be described. Please expand 2.03.4(9) to address the lease and <br />permit currently held that is contiguous to the DRMS Permit Area. <br />2.03.5 Compliance Information <br />1. DRMS 02/18: For the violation (CV -2012-003) listed in Sections 2.03.5 of the permit, Rule <br />2.03.5(3)(a) requires the following information to be provided: <br />a. DRMS 02/18: the MSHA number and the name of the person to whom the violation <br />notice was issued. Please update both sections of the permit with this information. <br />b. DRMS 02/18: For the violation listed in Section 2.03.5 for the King I mine, the permit <br />indicates the required abatement is ongoing at this time. However, this section of <br />the King 11 mine indicates the violation was terminated on December 11, 2012. <br />Please update the King I Mine permit section 2.03.5 to reflect the current state of the <br />violation in accordance with Rule 2.03.5(d). <br />C. DRMS 02/18: For both sections 2.03.5 of the permit, please discuss the actions, if <br />any, that were taken by the applicant to abate the violation. <br />DRMS 06/14: Sections 2.03.5 were updated as requested. These items have been <br />satisfactorily addressed. <br />2.03.8 Permit Term Information <br />1. DRMS 02/18: King I and King II Sections 2.03.8 direct the reader to Sections 2.05.2 and <br />2.05.3 for the anticipated start of each phase of the mining activities. Section 2.05.2 of the <br />permit indicates the King I Mine started in 1941 and ended in 2009; however, Section <br />2.05.2 for the King II permit only states the expected life of the mine is 6 to 9 years. The <br />actual start date and anticipated termination date for the King II mine is not stated. Please <br />revise the King II permit to identify the actual starting date of the King II mine and the <br />anticipated termination date of the King II mine, in accordance with Rule 2.03.8(2). <br />DRMS 06/14: King II Section 2.05.2 was revised to incorporate the required information. <br />This item has been satisfactorily addressed. <br />2. DRMS 02/18: Affected areas are tabulated in Sections 2.03.8 of the permit; the Division <br />calculates the sum of the King I and King II Affected areas to be 2,374.89 acres. King I <br />permit maps appear to indicate that some affected areas lie outside the bounds of the <br />permit area. The Division expects that this configuration was developed in order to <br />identify any impacts due to angle of draw that may have resulted from removal of coal <br />right up to the permit / lease boundary. Mining at King I was completed in 2009, so GCC <br />
The URL can be used to link to this page
Your browser does not support the video tag.