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: Liberty Tire Recycling-SLC

Injury · Job transfer or restriction

At a glance

On , an injury at Liberty Tire Recycling-SLC in 1398 Beck St, Salt Lake City, UT 84116 resulted in job transfer or restriction. Employee was mechanic in recyclable materials (e.g., glass, metal, paper) merchant wholesalers.

Watch Liberty Tire Recycling-SLC — free Get an email when a new federal OSHA severe-injury report for Liberty Tire Recycling-SLC is published. One employer, no account, unsubscribe in one click.

Where did this happen?

Establishment
Liberty Tire Recycling-SLC
Parent company
Liberty Tire Recycling
Street
1398 Beck St
City
Salt Lake City
State
UT
ZIP
84116
On-site location
Building C Maintenance Shop- truck pit

What was the outcome?

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

Before the incident

Working under semi-truck

What happened

[REDACTED] fell in the mechanic 's right eye when he moved some hoses aside.

Injury or illness

Foreign object in right eye corneal abrasion

Object or substance involved

falling debris

Summary line

Foreign object in the eye-

Employee and industry

Job description
Mechanic
SOC code
9999 — Uncoded
NAICS code
423930 — Recyclable materials (e.g., glass, metal, paper) merchant wholesalers
NAICS vintage
2022
Avg employees
115
Total hours worked
275751
EIN
43613449
Establishment ID
1156748
Employer case #
11

When (timing detail)

Date of incident
Shift started
6:00:00.000
Filing year
2023
Submitted
24FEB24:02:25:00

More injuries at Liberty Tire Recycling-SLC

View Liberty Tire Recycling-SLC's full OSHA safety record →

More injuries in this industry (NAICS 423930)

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.