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

North Salt lake, UT —

OSHA Injury Report: North Salt Lake - M&S

Injury · Job transfer or restriction

At a glance

On , an injury at North Salt Lake - M&S in 400 North 700 West, North Salt lake, UT 84054 resulted in job transfer or restriction. Employee was mover in van lines, moving and storage services.

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

Where did this happen?

Establishment
North Salt Lake - M&S
Parent company
Bailey's Moving & Storage
Street
400 North 700 West
City
North Salt lake
State
UT
ZIP
84054
On-site location
Customer 's home - bedroom

What was the outcome?

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

Before the incident

Assembling a bed headboard.

What happened

While assembling a bed headboard the headboard fell and the mirror in the headboard broke and cut right middle finger.

Injury or illness

Cut right middle finger.

Object or substance involved

headboard mirror

Summary line

Right middle finger

Employee and industry

Job description
Mover
SOC code
53-7062 — Laborers and Freight, Stock, and Material Movers, Hand
NAICS code
484210 — Van lines, moving and storage services
NAICS vintage
2022
Avg employees
109
Total hours worked
201944
EIN
870221607
Establishment ID
92419
Employer case #
5

When (timing detail)

Date of incident
Shift started
7:00:00.000
Time of incident
17:15:00.000
Filing year
2023
Submitted
31JAN24:20:42:00

More injuries at North Salt Lake - M&S

View North Salt Lake - M&S's full OSHA safety record →

More injuries in this industry (NAICS 484210)

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.