Belleville, MI —
OSHA Injury Report: Neapco Drivelines - Belleville, MI
Injury · Job transfer or restriction
At a glance
On , an injury at Neapco Drivelines - Belleville, MI in Belleville, MI 48111 resulted in job transfer or restriction. Employee was driveline Assembler in drive shafts and half shafts, automotive, truck, and bus, manufacturing.
Where did this happen?
- Establishment
- Neapco Drivelines - Belleville, MI
- Parent company
- Neapco Drivelines LLC
- Street
- 6735 Haggerty rd
- City
- Belleville
- State
- MI
- ZIP
- 48111
- On-site location
- 4-2 Assembly
What was the outcome?
- Outcome
- Job transfer or restriction (code 3)
- Type
- Injury (code 1)
- Days restricted or transferred
- 3
Before the incident
The employee was moving components in a material basket
What happened
EE states that while running 4-2 assembly and removing a part from the basket a part that was located behind it (steel driveshaft half piece) rolled forward and smashed his finger resulting in a contusion laceration of his finger. EE was treated by first responders and then sent to the clinic. Employee was returned to work with restrictions which resulted in job transfer.
Injury or illness
Laceration and Contusion: Finger (Left)
Object or substance involved
Steel Driveshaft (half)
Summary line
EE states they smashed their finger on 4 line handling steel driveshaft.
Employee and industry
- Job description
- Driveline Assembler
- SOC code
- 51-2099 — Assemblers and Fabricators, All Other
- NAICS code
- 336350 — Drive shafts and half shafts, automotive, truck, and bus, manufacturing
- NAICS vintage
- 2022
- Avg employees
- 670
- Total hours worked
- 1390494
- EIN
- 261107337
- Establishment ID
- 1415590
- Employer case #
- R2025025
When (timing detail)
- Date of incident
- Shift started
- 15:00
- Time of incident
- 15:20
- Filing year
- 2025
- Submitted
- 18FEB26:15:36:00
Source
Data from OSHA ITA Form 300/301 electronic submissions, filing year 2025. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.