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

Cannon Falls, MN —

OSHA Injury Report: Henkel US Operations Corporation - Cannon Falls, MN

Injury · Other recordable case

At a glance

On , an injury at Henkel US Operations Corporation - Cannon Falls, MN in 301 Washington Street W, Cannon Falls, MN 55009 resulted in other recordable case. Employee was shipper in filters, electronic component-type, manufacturing.

Where did this happen?

Establishment
Henkel US Operations Corporation - Cannon Falls, MN
Parent company
Henkel US Operations Corporation
Street
301 Washington Street W
City
Cannon Falls
State
MN
ZIP
55009
On-site location
Shipping

What was the outcome?

Outcome
Other recordable case (code 4)
Type
Injury (code 1)

Before the incident

Cutting apart a gaylord box

What happened

Laceration to right knee when cutting a box

Injury or illness

Laceration to the right knee

Object or substance involved

Retractable Box Cutter

Summary line

Laceration to the right knee when using a Retractable box cutter

Employee and industry

Job description
Shipper
SOC code
43-5071 — Shipping, Receiving, and Inventory Clerks
NAICS code
334419 — Filters, electronic component-type, manufacturing
NAICS vintage
2022
Avg employees
202
Total hours worked
353078
EIN
410957894
Establishment ID
1139569
Employer case #
25823403

When (timing detail)

Date of incident
Shift started
6:00
Time of incident
8:46
Filing year
2025
Submitted
28JAN26:17:56:00

More injuries at Henkel US Operations Corporation - Cannon Falls, MN

View Henkel US Operations Corporation - Cannon Falls, MN's full OSHA safety record →

More injuries in this industry (NAICS 334419)

Boalsburg, PA—

Blatek

Boalsburg, PA—

Blatek

More injuries in MN

BROOKLYN PARK, MN—

WM 1864

OAK PARK HEIGHTS, MN—

WM 1861

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.