SALT LAKE CITY, UT —
OSHA Injury Report: USU
Injury · Other recordable case
At a glance
On , an injury at USU in SALT LAKE CITY, UT 84104 resulted in other recordable case. Employee was driver Sales Rep in freight Transportation.
Where did this happen?
- Establishment
- USU
- Parent company
- XPO Logistics Freight Inc.
- Street
- 858 S 3760 W
- City
- SALT LAKE CITY
- State
- UT
- ZIP
- 84104
- On-site location
- CUSTOMER 'S DOCK YARD
What was the outcome?
- Outcome
- Other recordable case (code 4)
- Type
- Injury (code 1)
Before the incident
in trailer
What happened
The EE was pulling the pallet jack in the back of the trailer. The pallet jack stopped due to trash on the floor of the trailer causing the EE to trip in the trailer. When the EE tripped and fell to the floor of the trailer he was still holding onto the pallet jack handle causing the pallet jack handle that he was holding on to come down and smash his left wrist. The EE suffered inflammation and a contusion to his left wrist. The EE sought medical treatment.
Injury or illness
STRAIN
Object or substance involved
pallet jack
Summary line
EE tripped and fell to the floor of the trailer he was holding onto the pallet jack handle causing the pallet jack handle that he was holding on to come down and smash his left wrist. The EE suffered inflammation and a contusion to his left wrist
Employee and industry
- Job description
- Driver Sales Rep
- SOC code
- 41-3091 — Sales Representatives of Services, Except Advertising, Insurance, Financial Services, and Travel
- NAICS code
- 484122 — Freight Transportation
- NAICS vintage
- 2022
- Avg employees
- 234
- Total hours worked
- 486848
- EIN
- 942904084
- Establishment ID
- 108505
- Employer case #
- 8.27993E+1
When (timing detail)
- Date of incident
- Shift started
- 0:00:00.000
- Time of incident
- 13:00:00.000
- Submitted
- 11MAR24:20:20:00
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.