2,042,423Injury reports 130,778Establishments Most recent incident 2025-12-31
Safety Incidents OSHA Severe Injury Reports · 2015–2025

Vicksburg, MI —

OSHA Injury Report: Summit Polymers Inc. Plant 8

Injury · Job transfer or restriction

At a glance

On , an injury at Summit Polymers Inc. Plant 8 in 115 S Leja Drive, Vicksburg, MI 49097 resulted in job transfer or restriction. Employee was assembly Utility in television housings, plastics, manufacturing.

Where did this happen?

Establishment
Summit Polymers Inc. Plant 8
Parent company
Summit Polymers Inc
Street
115 S Leja Drive
City
Vicksburg
State
MI
ZIP
49097
On-site location
Assembly Department

What was the outcome?

Outcome
Job transfer or restriction (code 3)
Type
Injury (code 1)
Days restricted or transferred
22

Before the incident

Pushing totes across the floor.

What happened

Employee was pushing totes and there was a protruding bolt that the totes got caught on and employee jammed her thumb into totes causing it to sprain.

Injury or illness

Left thumb sprain

Object or substance involved

pushing totes across the floor.

Summary line

Employee was pushing totes and there was a protruding bolt that the totes got caught on and employee jammed her thumb into totes causing it to sprain.

Employee and industry

Job description
Assembly Utility
SOC code
51-2099 — Assemblers and Fabricators, All Other
NAICS code
326199 — Television housings, plastics, manufacturing
NAICS vintage
2022
Avg employees
337
Total hours worked
544105
EIN
381990845
Establishment ID
1123907
Employer case #
5

When (timing detail)

Date of incident
Shift started
16:00:00.000
Time of incident
18:30:00.000
Submitted
24FEB24:03:54:00

More injuries at Summit Polymers Inc. Plant 8

View Summit Polymers Inc. Plant 8's full OSHA safety record →

More injuries in this industry (NAICS 326199)

More injuries in MI

Source

Data from OSHA ITA Form 300/301 electronic submissions, filing year unspecified. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.