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

Salt Lake City, UT —

OSHA Injury Report: Vobev

Injury · Other recordable case

At a glance

On , an injury at Vobev in 5454 West 150 South, Salt Lake City, UT 84104 resulted in other recordable case. Employee was decorator operator in aluminum cans, light gauge metal, manufacturing.

Where did this happen?

Establishment
Vobev
Parent company
Vobev
Street
5454 West 150 South
City
Salt Lake City
State
UT
ZIP
84104
On-site location
Can Making Back end

What was the outcome?

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

Before the incident

Right [REDACTED]-was trying to loosen a bolt once bolt was loose wrench and metal pitched my finger and made a cut.

What happened

Right [REDACTED]-was trying to loosen a bolt once bolt was loose wrench and metal pitched my finger and made a cut.

Injury or illness

Right pinky-was trying to loosen a bolt once bolt was loose wrench and metal pitched my finger and made a cut.

Object or substance involved

Right Pinky finger was cut by bolt

Summary line

Laceration of right pinky pinched between tool

Employee and industry

Job description
Decorator operator
SOC code
9999 — Uncoded
NAICS code
332431 — Aluminum cans, light gauge metal, manufacturing
NAICS vintage
2022
Avg employees
281
Total hours worked
665295
EIN
842143545
Establishment ID
1077080
Employer case #
3

When (timing detail)

Date of incident
Shift started
6:00:00.000
Time of incident
0:00:00.000
Submitted
18JAN24:20:25:00

More injuries at Vobev

Salt Lake City, UT—

Vobev

Salt Lake City, UT—

Vobev

Salt Lake City, UT—

Vobev

Salt Lake City, UT—

Vobev

Salt Lake City, UT—

Vobev

View Vobev'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 unspecified. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.