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 Terminal-NON DOT

Injury · Other recordable case

At a glance

On , an injury at North Salt Lake Terminal-NON DOT in 695 W. 1100 North, North Salt Lake, UT 84054 resulted in other recordable case. Employee was mechanic in general Automotive Repair and Office Duties.

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

Where did this happen?

Establishment
North Salt Lake Terminal-NON DOT
Parent company
CRETE CARRIER CORPORATION
Street
695 W. 1100 North
City
North Salt Lake
State
UT
ZIP
84054
On-site location
CRETE TERMINAL

What was the outcome?

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

Before the incident

[REDACTED]

What happened

Tech was picking up a torque wrench when they felt a pop in their left knee

Injury or illness

Dislocation - Misc Other - Left - Knee

Object or substance involved

LIFTING TOOL

Summary line

PICKING UP TORQUE WRENCH AND FELT PAIN IN LEFT KNEE

Employee and industry

Job description
Mechanic
SOC code
49-3023 — Automotive Service Technicians and Mechanics
NAICS code
484121 — General Automotive Repair and Office Duties
NAICS vintage
2022
Avg employees
22
Total hours worked
39728
EIN
470496288
Establishment ID
989387
Employer case #
2023322424

When (timing detail)

Date of incident
Shift started
8:00:00.000
Time of incident
9:30:00.000
Filing year
2023
Submitted
21FEB24:22:59:00

More injuries at North Salt Lake Terminal-NON DOT

View North Salt Lake Terminal-NON DOT's full OSHA safety record →

More injuries in this industry (NAICS 484121)

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.