Mining Incidents
Trainer viewPrint or save as PDF from your browser (⌘P / Ctrl+P).
← Standard view
Case study · MSHA Record #220182150018

Outside Foreman, Leadman fatality

July 31, 2018 at 7:00 AM
C-2 · Susag Sand & Gravel Inc · Wells County, ND
Investigator narrative
The loader operator was lowering a piece of metal chained to the bucket onto the top of a rock crushing plant. The loader operator did not see that the accident victim was between the loader bucket and the rock crusher frame.
Record details
Classification
POWERED HAULAGE
Accident type
Caught in, under or between a moving and a stationary object
Activity at time
Hang Or Reposition Tubing
Subunit / location
STRIP, QUARY, OPEN PIT
Source of injury
SURFACE MINING MACHINES
Nature of injury
CRUSHING
Total mining experience
40.23 years
Experience at this mine
40.23 years
Experience in this job
35.13 years
Mine type
Surface
Sector
Metal/Nonmetal
Similar incidents in MSHA records· same classification: POWERED HAULAGE
  • April 3, 2026 · Ohio County Coal Resources, Inc. · WV · Section Foreman, Bullgang Foreman, Labor Foreman, Leadman, Shift Boss

    An employee was working on a winch rope on a 650 scoop that was loaded with a shield, this shield was hit by another 650 scoop, causing the employee to be caught between the scoop he was working on and the shield tip.

  • January 8, 2026 · Ash Grove Cement South Texas LLC · TX · Haul/Off Road/Coal/Ore/Pit/Quarry/Rock/Rubber Tire Truck Driver, Transportation Truck Driver

    Third party delivery driver of raw materials was found deceased trapped between the frame and dump bed of EE's I-Bar owned and operated delivery truck. The driver was located on the West edge of the iron ore stockpile.

  • December 18, 2025 · Greenbrier Minerals, LLC · WV · Master Mechanic, Foreman, Supervisor

    The employee stepped out of manhole and onto the slope and was struck by a slope tractor traveling down the slope.

Source: US Mine Safety and Health Administration (MSHA) public records · Document 220182150018 · Mine ID 3200250
Mining Incidents · miningincidents.org/incident/213131