BLOOMINGTON, CA —
OSHA Injury Report: FedEx ZSRT G SOUTH RIALTO NCPC 926
Injury · Job transfer or restriction
At a glance
On , an injury at FedEx ZSRT G SOUTH RIALTO NCPC 926 in BLOOMINGTON, CA 92316 resulted in job transfer or restriction. Employee was package Handler in courier and Express Delivery Services.
Where did this happen?
- Establishment
- FedEx ZSRT G SOUTH RIALTO NCPC 926
- Parent company
- FEDERAL EXPRESS CORPORATION
- Street
- 315 WEST RESOURCE DRIVE LAKEMONT BUSINESS PARK
- City
- BLOOMINGTON
- State
- CA
- ZIP
- 92316
- On-site location
- WAREHOUSE
What was the outcome?
- Outcome
- Job transfer or restriction (code 3)
- Type
- Injury (code 1)
- Days restricted or transferred
- 2
Before the incident
PULLING A PALLET JACK AND STACKING BOXES
What happened
employee stated I was in unload door [REDACTED] I was using a pallet jack t bring the pallet closer to the belt the pallet was stacked all the way to the top so when I got close to the belt the top layer or boxes hit the trailer door causing the boxes to
Injury or illness
Bruised Skull Struck by object Boxes
Object or substance involved
Boxes
Summary line
employee stated I was in unload door [REDACTED] I was using a pallet jack t bring the pallet closer to the belt the pallet was stacked all the way to the top so when I got close to the belt the top layer or boxes hit the trailer door causing the boxes to
Employee and industry
- Job description
- Package Handler
- SOC code
- 53-7062 — Laborers and Freight, Stock, and Material Movers, Hand
- NAICS code
- 492110 — Courier and Express Delivery Services
- NAICS vintage
- 2022
- Avg employees
- 908
- Total hours worked
- 509812
- EIN
- 710427007
- Establishment ID
- 1367662
- Employer case #
- 264472
When (timing detail)
- Date of incident
- Shift started
- 8:00
- Time of incident
- 1:40
- Filing year
- 2024
- Submitted
- 28FEB2025:01:24:00
Source
Data from OSHA ITA Form 300/301 electronic submissions, filing year 2024. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.