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

MYRTLE BEACH, SC —

OSHA Injury Report: FedEx ZMYB G MYRTLE BEACH HD 3260

Injury · Days away from work

At a glance

On , an injury at FedEx ZMYB G MYRTLE BEACH HD 3260 in 395 FANTASY HARBOUR BLVD LAKEMONT BUSINESS PARK, MYRTLE BEACH, SC 29579 resulted in days away from work. Employee was package Handler in courier and Express Delivery Services.

Where did this happen?

Establishment
FedEx ZMYB G MYRTLE BEACH HD 3260
Parent company
FEDERAL EXPRESS CORPORATION
Street
395 FANTASY HARBOUR BLVD LAKEMONT BUSINESS PARK
City
MYRTLE BEACH
State
SC
ZIP
29579
On-site location
WAREHOUSE

What was the outcome?

Outcome
Days away from work (code 2)
Type
Injury (code 1)
Days away from work
113
Days restricted or transferred
46

Before the incident

UNLOADING TRAILER

What happened

unloading trailer and a forklift fork fell on his index finger causing a laceration

Injury or illness

Lacerated Left Finger s Struck by object Forklift

Object or substance involved

Forklift

Summary line

unloading trailer and a forklift fork fell on his index finger causing a laceration

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
162
Total hours worked
181265
EIN
710427007
Establishment ID
1367775
Employer case #
136708

When (timing detail)

Date of incident
Shift started
5:45
Time of incident
6:02
Filing year
2024
Submitted
28FEB2025:01:25:00

More injuries at FedEx ZMYB G MYRTLE BEACH HD 3260

View FedEx ZMYB G MYRTLE BEACH HD 3260's full OSHA safety record →

More injuries in this industry (NAICS 492110)

ERLANGER, KY—

CVG RO

More injuries in SC

GAFFNEY, SC—

WM 638

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.