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

SOUTH SAN FRANCISCO, CA —

OSHA Injury Report: FedEx 405 VICTORY AVE

Injury · Days away from work

At a glance

On , an injury at FedEx 405 VICTORY AVE in 405 VICTORY AVE, SOUTH SAN FRANCISCO, CA 94080 resulted in days away from work. Employee was cOURIER DOT CDL in transportation Air Cargo.

Where did this happen?

Establishment
FedEx 405 VICTORY AVE
Parent company
FEDEX EXPRESS
Street
405 VICTORY AVE
City
SOUTH SAN FRANCISCO
State
CA
ZIP
94080
On-site location
DGO WAREHOUSE

What was the outcome?

Outcome
Days away from work (code 2)
Type
Injury (code 1)
Days away from work
10
Days restricted or transferred
7

Before the incident

PUSHING;CARGO HEAVYWT W O ASSISTANCE;VEHICLE-STRAIGHT TRUCK-[REDACTED]

What happened

WHILE INSIDE A FEDEX TRUCK EMPLOYEE INJURED PULLED LOWER BACK WHILE PUSHING A 80LBS 24X24X36 WOODEN BOX WITHOUT ASSISTANCE.

Injury or illness

BACK (LOWER);NO SLIP TRIP FALL OR OTHER SPECIFIC ACCIDENT;SPRAINED

Object or substance involved

CARGO HEAVYWT W O ASSISTANCE;VEHICLE-STRAIGHT TRUCK-S2

Summary line

SPRAINEDSTIFFNESS;BACK (LOWER);NO SLIP TRIP FALL OR OTHER SPECIFIC ACCIDENT;

Employee and industry

Job description
COURIER DOT CDL
SOC code
43-5021 — Couriers and Messengers
NAICS code
492110 — Transportation Air Cargo
NAICS vintage
2022
Avg employees
134
Total hours worked
224930
EIN
710427007
Establishment ID
1153702
Employer case #
677536

When (timing detail)

Date of incident
Shift started
7:00:00.000
Time of incident
7:30:00.000
Filing year
2023
Submitted
23FEB24:15:46:00

More injuries at FedEx 405 VICTORY AVE

View FedEx 405 VICTORY AVE'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 2023. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.