My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
PERMFILE48481
DRMS
>
Back File Migration
>
Permit File
>
500000
>
PERMFILE48481
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/24/2016 10:50:26 PM
Creation date
11/20/2007 1:37:24 PM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
X200720511
IBM Index Class Name
Permit File
Doc Date
8/1/2007
Doc Name
Adequacy Response
From
Twentymile Coal Company
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.
/
12
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
PQabody <br />Twentymile Coal Company ~\v~O 29515 Routt County Road #27 <br />Oak Creek, CO 80467 <br />970.879.3800 <br />~ 0.~1p01 <br />ColoDrado DHemon of Reclamation, Mining, and Safety D~~iM~G~O and 5 etY o <br />1313 Sherman Street -Room 215 <br />Denver, Colorado 80203 <br />(303)866-3567 <br />Re: Twentymile Coal Company - Foidel Creek Mine. 2007-2008 Wolf Creek Seam Exploration Project <br />NOI X-2007-205-11 Adequacy Response <br />Deaz Mr. Hernandez: <br />The following responds to the adequacy issues relative to the referenced NOI, as identified in your letter of June 24, <br />2007: <br />Determination of Amount of Performance Bond Amount [Regulation 3.05.2(1)] <br />1) It is stated on page 4 of the NOI, in the section, "Site Development -Exploration Access'; that "Primary access <br />to the proposed exploration area will be via existing Routt County Road 33. As shown on Map 1, unimproved ranch <br />roads and jeep trails will be utilized to access exploration drill sites within the exploration area. " However, Map 1 <br />does not clearly indicate the locations of these unimproved ranch roads andjeep trails. So that we may be sure that <br />no new roads will need to be constructed for this project, please provide a revised Map 1 that clearly shows the <br />existing unimproved ranch roads and jeep trails that will be used during this project. <br />Response: It is important to understand that, as part of planning and laying-out an exploration progam, TCC first <br />identifies the azeas where additional geologic information is needed and the required density or number of drillholes <br />and/or seismic lines; preliminary locations are layed-out on a map, then final locations and access aze established in <br />the field and located using our high-resolution GPS receiver. In order to avoid new disturbance and minimize <br />constmction requirements, locations aze generally selected on or adjacent to existing roads, and in azeas that have <br />been previously disturbed by agricultural or other similaz activities, where feasible. The referenced language reflects <br />field location of the proposed drill-sites, and the fact that we were able to drive directly to the selected sites on <br />existing ranch roads or jeep trails, as noted. While these roads/trails have not been surveyed, we have noted their <br />approximate locations on the revised Map 1, copies of which accompany these responses. <br />Adequacy Review <br />2) Under the "Permittee" section of [he NOI application form, both the "Individual's Name" and the "Company <br />Name" were filled in. In accordance with the requirements of Regulation 2.02.2(2)(a), we prefer that only one of <br />these blanks be filled in. Please therefore submit a revised NOI application page identifying which entity should be <br />identified as the "Permittee". <br />Response: A revised NOI application page identifying the "Permittee" accompanies these responses. <br />3) In accordance with the requirements of Regulation 2.02.2(2(b), please provide the name, address and telephone <br />number of the "representative who will be present at and responsible for conducting the exploration activities" <br />
The URL can be used to link to this page
Your browser does not support the video tag.