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

NORTH PALM SPRINGS, CA —

OSHA Injury Report: FedEx ZPAL G PALM SPRINGS 922

Other illness · Job transfer or restriction

At a glance

On , an other illness at FedEx ZPAL G PALM SPRINGS 922 in 411 WEST GARNET AVE, NORTH PALM SPRINGS, CA 92258 resulted in job transfer or restriction. Employee was package Handler in courier and Express Delivery Services.

Where did this happen?

Establishment
FedEx ZPAL G PALM SPRINGS 922
Parent company
FEDERAL EXPRESS CORPORATION
Street
411 WEST GARNET AVE
City
NORTH PALM SPRINGS
State
CA
ZIP
92258
On-site location
VAN

What was the outcome?

Outcome
Job transfer or restriction (code 3)
Type
Other illness (code 6)
Days restricted or transferred
180

Before the incident

LAODING

What happened

Employee was loading a package to a van While loading the package he felt a crack in his left collar bone

Injury or illness

Sprained Left Chest Lifting Bodily Motion

Object or substance involved

Bodily Motion

Summary line

Employee was loading a package to a van While loading the package he felt a crack in his left collar bone

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
152
Total hours worked
95666
EIN
710427007
Establishment ID
1367559
Employer case #
126764

When (timing detail)

Date of incident
Shift started
4:00
Time of incident
5:20
Filing year
2024
Submitted
28FEB2025:01:24:00

More injuries at FedEx ZPAL G PALM SPRINGS 922

View FedEx ZPAL G PALM SPRINGS 922'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.