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

COLORADO SPRINGS, CO —

OSHA Injury Report: FedEx ZCSP G COLORADO SPRINGS 809

Injury · Other recordable case

At a glance

On , an injury at FedEx ZCSP G COLORADO SPRINGS 809 in 125 TROY HILL ROAD, COLORADO SPRINGS, CO 80916 resulted in other recordable case. Employee was seasonal Packag in courier and Express Delivery Services.

Where did this happen?

Establishment
FedEx ZCSP G COLORADO SPRINGS 809
Parent company
FEDERAL EXPRESS CORPORATION
Street
125 TROY HILL ROAD
City
COLORADO SPRINGS
State
CO
ZIP
80916
On-site location
TRAILER LOAD

What was the outcome?

Outcome
Other recordable case (code 4)
Type
Injury (code 1)

Before the incident

KNEELING TO LOAD A TRAILER

What happened

EE was loading a trailer and while kneeling down to tend to other packages and hit his knee EE sustained a knee contusion Medical treatment sought

Injury or illness

Strained Left Knee Struck by object being handled Packages

Object or substance involved

Packages

Summary line

EE was loading a trailer and while kneeling down to tend to other packages and hit his knee EE sustained a knee contusion Medical treatment sought

Employee and industry

Job description
Seasonal Packag
SOC code
43-5021 — Couriers and Messengers
NAICS code
492110 — Courier and Express Delivery Services
NAICS vintage
2022
Avg employees
347
Total hours worked
362162
EIN
710427007
Establishment ID
1367747
Employer case #
265738

When (timing detail)

Date of incident
Shift started
16:30
Time of incident
21:00
Filing year
2024
Submitted
28FEB2025:01:25:00

More injuries at FedEx ZCSP G COLORADO SPRINGS 809

View FedEx ZCSP G COLORADO SPRINGS 809's full OSHA safety record →

More injuries in this industry (NAICS 492110)

ERLANGER, KY—

CVG RO

More injuries in CO

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.