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

BLOOMINGTON, CA —

OSHA Injury Report: FedEx RLTO G RIALTO 923

Injury · Job transfer or restriction

At a glance

On , an injury at FedEx RLTO G RIALTO 923 in 330 RESOURCE DRIVE LAKEMONT BUSINESS PARK, 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 RLTO G RIALTO 923
Parent company
FEDERAL EXPRESS CORPORATION
Street
330 RESOURCE DRIVE LAKEMONT BUSINESS PARK
City
BLOOMINGTON
State
CA
ZIP
92316
On-site location
RESTROOM

What was the outcome?

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

Before the incident

WALKING INTO RESTROOM

What happened

employee walked in to the restroom and there was a little bit of water on the floor and employee slipped and fell

Injury or illness

Sprained Left Low back Fall Wet Floor

Object or substance involved

Wet Floor

Summary line

employee walked in to the restroom and there was a little bit of water on the floor and employee slipped and fell

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
2895
Total hours worked
1995529
EIN
710427007
Establishment ID
1367128
Employer case #
266254

When (timing detail)

Date of incident
Shift started
5:30
Time of incident
7:10
Filing year
2024
Submitted
28FEB2025:01:21:00

More injuries at FedEx RLTO G RIALTO 923

View FedEx RLTO G RIALTO 923's full OSHA safety record →

More injuries in this industry (NAICS 492110)

ERLANGER, KY—

CVG RO

More injuries in CA

Rancho Cucamonga, CA—

087-RCDC

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.