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

Fillmore, UT —

OSHA Injury Report: Great Lakes Cheese of Utah, Inc.

Injury · Job transfer or restriction

At a glance

On , an injury at Great Lakes Cheese of Utah, Inc. in 780 West 1400 South, Fillmore, UT 84631 resulted in job transfer or restriction. Employee was warehouse Worker in cheese merchant wholesalers.

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

Where did this happen?

Establishment
Great Lakes Cheese of Utah, Inc.
Street
780 West 1400 South
City
Fillmore
State
UT
ZIP
84631
On-site location
Warehouse

What was the outcome?

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

Before the incident

IE improperly stepped off of a sit-down forklift with wet shoes.

What happened

IE slipped off the step of the sit-down forklift and felt pressure in his abdomen.

Injury or illness

Hernia

Object or substance involved

Not utilizing 3 points of contact while exiting equipment.

Summary line

Abdominal Hernia

Employee and industry

Job description
Warehouse Worker
SOC code
53-7062 — Laborers and Freight, Stock, and Material Movers, Hand
NAICS code
424430 — Cheese merchant wholesalers
NAICS vintage
2012
Avg employees
368
Total hours worked
700260
Establishment ID
955222
Employer case #
11

When (timing detail)

Date of incident
Shift started
15:00
Time of incident
16:44
Filing year
2024
Submitted
21JAN2025:22:58:00

More injuries at Great Lakes Cheese of Utah, Inc.

View Great Lakes Cheese of Utah, Inc.'s full OSHA safety record →

More injuries in this industry (NAICS 424430)

More injuries in UT

Source

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