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

SAN LEANDRO, CA —

OSHA Injury Report: FedEx ZOAK G OAKLAND 946

Injury · Job transfer or restriction

At a glance

On , an injury at FedEx ZOAK G OAKLAND 946 in 1400 BUSINESS CENTER DRIVE LAKEMONT BUSINESS PARK, SAN LEANDRO, CA 94577 resulted in job transfer or restriction. Employee was sort Manager in courier and Express Delivery Services.

Where did this happen?

Establishment
FedEx ZOAK G OAKLAND 946
Parent company
FEDERAL EXPRESS CORPORATION
Street
1400 BUSINESS CENTER DRIVE LAKEMONT BUSINESS PARK
City
SAN LEANDRO
State
CA
ZIP
94577
On-site location
TRAILER UNLOAD

What was the outcome?

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

Before the incident

UNLOADING

What happened

EE was assisting in unloading a preload trailer when he attempted to pick up a large box and his back gave out

Injury or illness

Strained Bilateral Low back Lifting Package

Object or substance involved

Package

Summary line

EE was assisting in unloading a preload trailer when he attempted to pick up a large box and his back gave out

Employee and industry

Job description
Sort Manager
SOC code
Nov-71 — Transportation, Storage, and Distribution Managers
NAICS code
492110 — Courier and Express Delivery Services
NAICS vintage
2022
Avg employees
119
Total hours worked
72122
EIN
710427007
Establishment ID
1367544
Employer case #
264097

When (timing detail)

Date of incident
Shift started
5:00
Time of incident
7:15
Filing year
2024
Submitted
28FEB2025:01:23:00

More injuries at FedEx ZOAK G OAKLAND 946

View FedEx ZOAK G OAKLAND 946'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.