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

Salt Lake City, UT —

OSHA Injury Report: Silver King Beverage Company

Injury · Other recordable case

At a glance

On , an injury at Silver King Beverage Company in 5454 west 150 south, Salt Lake City, UT 84104 resulted in other recordable case. Employee was decorator Operator in metal Can Manufacturing.

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

Where did this happen?

Establishment
Silver King Beverage Company
Parent company
Silver King Beverage Company
Street
5454 west 150 south
City
Salt Lake City
State
UT
ZIP
84104
On-site location
Decorator

What was the outcome?

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

Before the incident

Employee was raising the crane and chain pulley block.

What happened

The cable on the crane broke and the chain pulley block fell and struck the fence. The chain pulley block bounced from the fence and struck employees head.

Injury or illness

head

Object or substance involved

incident involved lifting crane

Summary line

Crane cable snapped and pulley bounced off fence and hit employees head

Employee and industry

Job description
Decorator Operator
SOC code
51-9199 — Production Workers, All Other
NAICS code
332431 — metal Can Manufacturing
NAICS vintage
2022
Avg employees
367
Total hours worked
791722
Establishment ID
1432175
Employer case #
1

When (timing detail)

Date of incident
Shift started
18:00
Filing year
2025
Submitted
28JAN26:17:53:00

More injuries at Silver King Beverage Company

View Silver King Beverage Company's full OSHA safety record →

More injuries in this industry (NAICS 332431)

More injuries in UT

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.