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

Richmond, MO —

OSHA Injury Report: Henkel Richmond MO

Injury · Job transfer or restriction

At a glance

On , an injury at Henkel Richmond MO in 201 Highway 10 East, Richmond, MO 64085 resulted in job transfer or restriction. Employee was tool and Die Maker in motor vehicle moldings and extrusions, plastics, manufacturing.

Where did this happen?

Establishment
Henkel Richmond MO
Parent company
Henkel US Operations Corporation
Street
201 Highway 10 East
City
Richmond
State
MO
ZIP
64085
On-site location
Tool Room Shop Bench

What was the outcome?

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

Before the incident

Was fitting the insert for the mold cavity by stoning the pocket.

What happened

Tool & Die Maker lacerated right pinky finger while cleaning cavity in injection mold.

Injury or illness

Lacerated right little finger.

Object or substance involved

Sharp edge of injection mold.

Summary line

Lacerated right little finger while cleaning a mold at shop bench.

Employee and industry

Job description
Tool and Die Maker
SOC code
51-4111 — Tool and Die Makers
NAICS code
326199 — Motor vehicle moldings and extrusions, plastics, manufacturing
NAICS vintage
2022
Avg employees
346
Total hours worked
657400
EIN
410957894
Establishment ID
172601
Employer case #
2023030714

When (timing detail)

Date of incident
Shift started
7:15:00.000
Time of incident
9:45:00.000
Filing year
2023
Submitted
16FEB24:16:06:00

More injuries at Henkel Richmond MO

View Henkel Richmond MO's full OSHA safety record →

More injuries in this industry (NAICS 326199)

More injuries in MO

LEES SUMMIT, MO—

WM 573

SAINT JOSEPH, MO—

WM 2994

KIRKWOOD, MO—

WM 2694

DESLOGE, MO—

WM 95

Source

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