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

Lowell, MI —

OSHA Injury Report: Litehouse Foods Inc

Injury · Other recordable case

At a glance

On , an injury at Litehouse Foods Inc in 1400 Foreman St SE, Lowell, MI 49548 resulted in other recordable case. Employee was line Attendant I in salad dressings manufacturing.

Watch Litehouse Foods Inc — free Get an email when a new federal OSHA severe-injury report for Litehouse Foods Inc is published. One employer, no account, unsubscribe in one click.

Where did this happen?

Establishment
Litehouse Foods Inc
Parent company
Litehouse Foods Inc
Street
1400 Foreman St SE
City
Lowell
State
MI
ZIP
49548
On-site location
Pillow 6

What was the outcome?

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

Before the incident

Cutting excess ribbon off the core to change out the ribbon on the label printer.

What happened

When cutting the excess ribbon off the core using a retractable Safety knife the EO was not wearing cut resistant gloves and EO was cutting towards themselves and not away from them

Injury or illness

laceration to RH forearm

Object or substance involved

safety knife

Summary line

laceration RH forearm safety knife

Employee and industry

Job description
Line Attendant I
SOC code
51-9111 — Packaging and Filling Machine Operators and Tenders
NAICS code
311941 — Salad dressings manufacturing
NAICS vintage
2012
Avg employees
300
Total hours worked
560732
EIN
820348387
Establishment ID
977853
Employer case #
5

When (timing detail)

Date of incident
Shift started
15:00
Time of incident
21:00
Filing year
2025
Submitted
21JAN26:18:14:00

More injuries at Litehouse Foods Inc

View Litehouse Foods Inc's full OSHA safety record →

More injuries in this industry (NAICS 311941)

More injuries in MI

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.