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

Columbus, OH —

OSHA Injury Report: FedEx Supply Chain Philips Columbus

Injury · Days away from work

At a glance

On , an injury at FedEx Supply Chain Philips Columbus in 9570 Logistics Court, Columbus, OH 43217 resulted in days away from work. Employee was workflow Planner.

Where did this happen?

Establishment
FedEx Supply Chain Philips Columbus
Street
9570 Logistics Court
City
Columbus
State
OH
ZIP
43217
On-site location
Main break room.

What was the outcome?

Outcome
Days away from work (code 2)
Type
Injury (code 1)
Days away from work
2

Before the incident

Getting [REDACTED] lunch bag from the break room at the end of [REDACTED] shift.

What happened

Injured employee was walking past the door when the door opened. The door hit the teammates upper arm and caused a bruise.

Injury or illness

Contusion left arm.

Object or substance involved

Closet door.

Summary line

Injured employee was walking past the door when the door opened. The door hit the teammates upper arm and caused a bruise.

Employee and industry

Job description
Workflow Planner
SOC code
43-5061 — Production, Planning, and Expediting Clerks
NAICS code
493110
NAICS vintage
2022
Avg employees
489
Total hours worked
859701
EIN
251766580
Establishment ID
986659
Employer case #
23_597

When (timing detail)

Date of incident
Shift started
6:00:00.000
Time of incident
18:00:00.000
Filing year
2023
Submitted
23FEB24:16:14:00

More injuries at FedEx Supply Chain Philips Columbus

View FedEx Supply Chain Philips Columbus's full OSHA safety record →

More injuries in this industry (NAICS 493110)

Rancho Cucamonga, CA—

087-RCDC

MATTESON, IL—

WM 6504

COLDWATER, MI—

WM 6043

More injuries in OH

LEWIS CENTER, OH—

WM 2725

EASTLAKE, OH—

WM 1863

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.