2,098,129Injury reports 132,232Establishments Most recent incident 2025-12-31
Safety Incidents OSHA Severe Injury Reports · 2015–2025

Salt Lake City, UT —

OSHA Injury Report: CHEFSTORE Salt Lake City 501

Injury · Days away from work

At a glance

On , an injury at CHEFSTORE Salt Lake City 501 in 370 Paxton Avenue, Salt Lake City, UT 84101 resulted in days away from work. Employee was department Lead in grocery.

Watch Chefstore Salt Lake City 501 — free Get an email when a new federal OSHA severe-injury report for Chefstore Salt Lake City 501 is published. One employer, no account, unsubscribe in one click.

Where did this happen?

Establishment
CHEFSTORE Salt Lake City 501
Parent company
US Foods
Street
370 Paxton Avenue
City
Salt Lake City
State
UT
ZIP
84101
On-site location
Aisle 7 by the flour

What was the outcome?

Outcome
Days away from work (code 2)
Type
Injury (code 1)
Days away from work
2

Before the incident

putting up topstock

What happened

Fell off ladder while pulling top stock

Injury or illness

Nature of InjuryIllness Sprain Strain Body Parts KneeRight

Object or substance involved

slipped on ladder while stepping down ladder

Summary line

Nature of InjuryIllness Sprain Strain Cause of InjuryIllnessFall Different Level Body Parts KneeRight Object Substance slipped on ladder while stepping down ladder

Employee and industry

Job description
Department Lead
SOC code
9999 — Uncoded
NAICS code
424410 — Grocery
NAICS vintage
2022
Avg employees
8
Total hours worked
17076
Establishment ID
1098415
Employer case #
US-501 SAL

When (timing detail)

Date of incident
Shift started
11:00:00.000
Time of incident
14:30:00.000
Filing year
2023
Submitted
01FEB24:02:24:00

More injuries at CHEFSTORE Salt Lake City 501

View CHEFSTORE Salt Lake City 501's full OSHA safety record →

More injuries in this industry (NAICS 424410)

More injuries in UT

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.