Laserfiche WebLink
Page 1 of 1 <br />Hernandez, Daniel <br />From: Berry, David <br />Sent: Wednesday, April 01, 2009 12:35 PM <br />To: Hernandez, Daniel; Musick, Jason <br />Cc: Brown, Sandy; Mathews, Dan; Berry, David <br />Dan and Jason - I apologize for my delay in responding to your inqiuiries of yesterday regarding the NOI vs. MR <br />issue for the pending Sage Creek exploration activities. I will respond here in the interest of time. <br />It is my understanding that Sage Creek wishes to conduct geotechnical investigations in advance of the pending <br />new Sage Creek mine permit application, on the Seneca II permit area, by amending an existing NOI. You <br />correctly advised Mr. Nettleton that exploration within a permit area should be done by the MR process rather <br />than by the NOI process. Mr. Nettleton called me following your advice to do so, and he explained their position <br />that the proposed geotechnical investigations should be reviewed under the NOI process. After my inquiry to Mr. <br />Nettleton, I also received an email from Mr. Nettleton indicating the phase II bond release application status for <br />the Seneca II Mine area in question. <br />I understand that the proposed geotechnical investigations will be instructive to mine planning and mine permit <br />application process for the potential Sage Creek Mine application. This application will eventually overlap a <br />portion of the existing Seneca II permit. Once (and if) the Sage Creek Permit is issued, then the overlap area will <br />be removed by an appropriate permitting/release process from the Seneca II permit. <br />First, I continue to advise that when exploration is conducted by an entity, within the same entity's permit area, we <br />should be requiring that said exploration should be addressed as an MR or TR to the entity's permit. This course <br />seems to be consistent with both state and federal regulations that make reference to exploration activities, by <br />regulation section title, as activities outside the permit area. <br />The present situation involving Sage Creek may be a slightly different in that we have two separate business or <br />permitting entities (Sage Creek and Seneca) involved in the situation. In this case, the exploration is proposed to <br />be conducted by Sage Creek, but on Seneca permit area. It is my understanding that Seneca is not conducting <br />the proposed activities. Although a strict interpretation of our regulations might lead us to conclude that Seneca <br />should provide an MR to permit all of the exploration, I do not think that is a practical solution in this case because <br />the Seneca entity is not conducting the exploration. <br />I recommend that we allow Sage Creek to permit the proposed geotechnical drilling on the Seneca permit area <br />using the NOI process. I suggest this course because Sage Creek is the exploring entity, not Seneca. Sage Creek <br />does not yet have a permit, thus their exploration will not be occurring in any Sage Creek permit area. I also <br />recommend that there should be a concurrent MR to the Seneca permit to formally recognize that the Sage Creek <br />activity will be occurring and that the Seneca entity agrees that the Sage Creek exploration activity will be <br />occurring on Seneca permit area. The NOI must be precise in describing exploration disturbance locations and <br />boundaries to ensure proper compliance accountability to Sage Creek and to prevent any detrimental compliance <br />implications to the Seneca entity and reclamation/liability release process. <br />This issue is difficult given the mix of regulatory and practical issues, so this recommendation is for this situation <br />only and is not to be taken as precedent for any other circumstance. Please continue to check with me if and as <br />these situations arise. Your initial advice to Mr. Nettleton was generally consistent with our previous and ongoing <br />direction. Feel free to forward this message to the Sage Creek and/or Seneca representatives. <br />Thanks, DB <br />4/2/2009