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

Pico Rivera, CA —

OSHA Injury Report: CA-Pico Rivera-783-YRC Freight

Injury · Job transfer or restriction

At a glance

On , an injury at CA-Pico Rivera-783-YRC Freight in 9933 Beverly Blvd, Pico Rivera, CA 90660 resulted in job transfer or restriction. Employee was dock Worker in freight Trucking lTL.

Where did this happen?

Establishment
CA-Pico Rivera-783-YRC Freight
Parent company
YRC Freight
Street
9933 Beverly Blvd
City
Pico Rivera
State
CA
ZIP
90660
On-site location
Company Premises

What was the outcome?

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

Before the incident

working

What happened

Struck Injured By Object Being Lifted or Handled

Injury or illness

Fracture

Object or substance involved

normal work equipment or process

Summary line

Mr. [REDACTED] was unloading a deck bar from a trailer at the 84 door and when he arrived to the deck table to put the bar away he noticed that some improperly stacked deck bars were going to fall. He held the falling bars with his left hand as he tried

Employee and industry

Job description
Dock Worker
SOC code
53-7062 — Laborers and Freight, Stock, and Material Movers, Hand
NAICS code
484122 — Freight Trucking lTL
NAICS vintage
2022
Avg employees
111
Total hours worked
221333
EIN
340492670
Establishment ID
1242540
Employer case #
2300000501

When (timing detail)

Date of incident
Shift started
14:00:00.000
Time of incident
22:30:00.000
Submitted
15MAY24:18:01:00

More injuries at CA-Pico Rivera-783-YRC Freight

View CA-Pico Rivera-783-YRC Freight's full OSHA safety record →

More injuries in this industry (NAICS 484122)

MANCHESTER, NH—

XNH

More injuries in CA

Rancho Cucamonga, CA—

087-RCDC

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.