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

CHARLOTTE, NC —

OSHA Injury Report: FedEx NCRS G NORTH CHARLOTTE RSF 275

Injury · Job transfer or restriction

At a glance

On , an injury at FedEx NCRS G NORTH CHARLOTTE RSF 275 in 4906 GIBBON RD, CHARLOTTE, NC 28269 resulted in job transfer or restriction. Employee was packaging in courier and Express Delivery Services.

Where did this happen?

Establishment
FedEx NCRS G NORTH CHARLOTTE RSF 275
Parent company
FEDERAL EXPRESS CORPORATION
Street
4906 GIBBON RD
City
CHARLOTTE
State
NC
ZIP
28269
On-site location
JOBSITE

What was the outcome?

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

Before the incident

REACHING FOR BOX

What happened

A package hit her knee after reaching down a metal shoot States that the package was moving out of fast rate and hit her knee

Injury or illness

Bruised Left Knee Struck by object Box

Object or substance involved

Box

Summary line

A package hit her knee after reaching down a metal shoot States that the package was moving out of fast rate and hit her knee

Employee and industry

Job description
Packaging
SOC code
53-7064 — Packers and Packagers, Hand
NAICS code
492110 — Courier and Express Delivery Services
NAICS vintage
2022
Avg employees
807
Total hours worked
466945
EIN
710427007
Establishment ID
1367095
Employer case #
267011

When (timing detail)

Date of incident
Shift started
12:00
Time of incident
15:20
Filing year
2024
Submitted
28FEB2025:01:20:00

More injuries at FedEx NCRS G NORTH CHARLOTTE RSF 275

View FedEx NCRS G NORTH CHARLOTTE RSF 275's full OSHA safety record →

More injuries in this industry (NAICS 492110)

ERLANGER, KY—

CVG RO

More injuries in NC

FAYETTEVILLE, NC—

WM 8218

GREENSBORO, NC—

WM 6402

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.