02.03.2013 Views

Independent Review of MSHA's Actions at Crandall Canyon Mine

Independent Review of MSHA's Actions at Crandall Canyon Mine

Independent Review of MSHA's Actions at Crandall Canyon Mine

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Conclusion: The consultant’s recommend<strong>at</strong>ions th<strong>at</strong> were included in reports submitted by<br />

the mine oper<strong>at</strong>or to support pillar extraction in the South Barrier section were not consistently<br />

included in the approved ro<strong>of</strong> control plan. When the ro<strong>of</strong> control plan contradicted the<br />

consultant’s recommend<strong>at</strong>ions, a thorough analysis <strong>of</strong> the potential consequences was not<br />

conducted.<br />

The District also failed to recognize the importance <strong>of</strong> mined height in the analysis <strong>of</strong> stability<br />

factors and bump potential <strong>of</strong> pillars. Plan approval was reportedly based in part on computer<br />

modeling which was conducted with an eight-foot mining height, but this was not accounted<br />

for in the ro<strong>of</strong> control plan.<br />

Recommend<strong>at</strong>ion: Consultant recommend<strong>at</strong>ions used to support mine plan submittals<br />

should be specifically addressed in such plan approvals.<br />

When plan approval is based on computer modeling, model input parameters should be<br />

specifically reflected in the plan.<br />

6) The adequacy <strong>of</strong> the required six-month plan reviews. District 9 had a formal SOP for the<br />

review and approval <strong>of</strong> ro<strong>of</strong> control plans. Specialists, including the ro<strong>of</strong> control<br />

supervisor, reviewed all new plans and supplements. Historically, the specialists assigned<br />

to the district <strong>of</strong>fice would also conduct the mand<strong>at</strong>ory six-month plan reviews required by<br />

§ 75.223(d). Due to <strong>at</strong>trition and other work assignments, these duties had been assumed<br />

and conducted by mine inspectors in District 9 since early 2006. These reviews were<br />

documented by completion <strong>of</strong> the MSHA 2000-204 Plan <strong>Review</strong> forms, which were<br />

submitted with the required quarterly inspection reports.<br />

While the use <strong>of</strong> the 2000-204 forms as a means <strong>of</strong> documenting the six-month plan reviews<br />

is in itself not a deficiency, the IRT found an issue th<strong>at</strong> impacted the adequacy <strong>of</strong> this<br />

practice in District 9. The inspectors in the Price Field Office st<strong>at</strong>ed th<strong>at</strong> when they<br />

documented a plan deficiency on the MSHA 2000-204 form, they seldom received any<br />

feedback from the District personnel responsible for th<strong>at</strong> plan area. Inspectors st<strong>at</strong>ed th<strong>at</strong><br />

this lack <strong>of</strong> communic<strong>at</strong>ion with the District Office concerning plan inadequacies cited via<br />

the 2000-204 form was not an isol<strong>at</strong>ed instance, but r<strong>at</strong>her an ongoing practice th<strong>at</strong> had<br />

existed for some time.<br />

The District 9 Ro<strong>of</strong> Control Branch SOP required the plan reviewer do the following:<br />

• <strong>Review</strong> comments from the ro<strong>of</strong> control specialist or supervisor;<br />

• <strong>Review</strong> plan review forms and previous ro<strong>of</strong> control cit<strong>at</strong>ions issued since the last plan<br />

review; and<br />

• If comments from the field personnel will not be incorpor<strong>at</strong>ed, notify th<strong>at</strong> person(s) <strong>of</strong><br />

your reasoning for not incorpor<strong>at</strong>ing the comments.<br />

27

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!