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

EATONTOWN, NJ —

OSHA Injury Report: FedEx 210 INDUSTRIAL WAY W

Other illness · Job transfer or restriction

At a glance

On , an other illness at FedEx 210 INDUSTRIAL WAY W in 210 INDUSTRIAL WAY W, EATONTOWN, NJ 07724 resulted in job transfer or restriction. Employee was cOURIER SWING DRVR DOT in transportation Air Cargo.

Where did this happen?

Establishment
FedEx 210 INDUSTRIAL WAY W
Parent company
FEDEX EXPRESS
Street
210 INDUSTRIAL WAY W
City
EATONTOWN
State
NJ
ZIP
07724
On-site location
OFF PREMISES CUST LOC LOADING DOCK

What was the outcome?

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

Before the incident

LIFTING;PACKAGE

What happened

EMPLOYEE WAS PICKING UP A BOX FROM THE TOP SHELF IN HIS TRUCK WHEN HE FELT A SHARP PAIN IN HIS LEFT SHOULDER.

Injury or illness

POSSIBLE MUSCULOSKELETAL DISORDER;SHOULDER (LEFT);NO SLIP TRIP FALL OR OTHER SPECIFIC ACCIDENT;THROBBING

Object or substance involved

PACKAGE

Summary line

THROBBING;SHOULDER (LEFT);NO SLIP TRIP FALL OR OTHER SPECIFIC ACCIDENT;

Employee and industry

Job description
COURIER SWING DRVR DOT
SOC code
43-5021 — Couriers and Messengers
NAICS code
492110 — Transportation Air Cargo
NAICS vintage
2022
Avg employees
101
Total hours worked
170139
EIN
710427007
Establishment ID
1153530
Employer case #
679792

When (timing detail)

Date of incident
Shift started
8:00:00.000
Time of incident
13:40:00.000
Filing year
2023
Submitted
23FEB24:15:42:00

More injuries at FedEx 210 INDUSTRIAL WAY W

View FedEx 210 INDUSTRIAL WAY W's full OSHA safety record →

More injuries in this industry (NAICS 492110)

ERLANGER, KY—

CVG RO

More injuries in NJ

SECAUCUS, NJ—

WM 3520

RIVERDALE, NJ—

WM 3443

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.