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 ZWNG G WINGATE HD 3267

Injury · Days away from work

At a glance

On , an injury at FedEx ZWNG G WINGATE HD 3267 in 6020 AIRPORT DRIVE LAKEMONT BUSINESS PARK, CHARLOTTE, NC 28208 resulted in days away from work. Employee was package Handler in courier and Express Delivery Services.

Where did this happen?

Establishment
FedEx ZWNG G WINGATE HD 3267
Parent company
FEDERAL EXPRESS CORPORATION
Street
6020 AIRPORT DRIVE LAKEMONT BUSINESS PARK
City
CHARLOTTE
State
NC
ZIP
28208
On-site location
TRAILER LOAD

What was the outcome?

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

Before the incident

LOADING

What happened

Package Handler was loading a trailer with a box that had a staple hanging out of it and it cut the top of his right hand

Injury or illness

Lacerated Right Hand Lifting Box

Object or substance involved

Box

Summary line

Package Handler was loading a trailer with a box that had a staple hanging out of it and it cut the top of his right hand

Employee and industry

Job description
Package Handler
SOC code
53-7062 — Laborers and Freight, Stock, and Material Movers, Hand
NAICS code
492110 — Courier and Express Delivery Services
NAICS vintage
2022
Avg employees
184
Total hours worked
106853
EIN
710427007
Establishment ID
1367722
Employer case #
259130

When (timing detail)

Date of incident
Shift started
15:30
Time of incident
19:15
Filing year
2024
Submitted
28FEB2025:01:24:00

More injuries at FedEx ZWNG G WINGATE HD 3267

View FedEx ZWNG G WINGATE HD 3267'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.