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

MEMPHIS, TN —

OSHA Injury Report: FedEx 5025 TUGGLE RD

Injury · Other recordable case

At a glance

On , an injury at FedEx 5025 TUGGLE RD in 5025 TUGGLE RD, MEMPHIS, TN 38118 resulted in other recordable case. Employee was cIL MATERIAL HANDLER in transportation Air Cargo.

Where did this happen?

Establishment
FedEx 5025 TUGGLE RD
Parent company
FEDEX EXPRESS
Street
5025 TUGGLE RD
City
MEMPHIS
State
TN
ZIP
38118
On-site location
WAREHSE LOGISTICS ORDER PICKER

What was the outcome?

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

Before the incident

HANDLING;OBJECT- SHARP;HAND TOOLS - NOT POWERED

What happened

[REDACTED] WAS CUTTING A BOX USING THE PROPER TECHNIQUE CUTTING AWAY FROM HER BODY THE BLADE GOT STUCK AND AS SHE PULLED IT THE BLADE WENT ACROSS HER THUMB AND CUT INTO HER THUMB AND FINGER NAIL

Injury or illness

FINGER (THUMB RIGHT);CAUGHT BETWEEN;CUT OR LACERATION

Object or substance involved

OBJECT- SHARP;HAND TOOLS - NOT POWERED

Summary line

CUT OR LACERATION;FINGER (THUMB RIGHT);CAUGHT BETWEEN;

Employee and industry

Job description
CIL MATERIAL HANDLER
SOC code
53-7062 — Laborers and Freight, Stock, and Material Movers, Hand
NAICS code
492110 — Transportation Air Cargo
NAICS vintage
2022
Avg employees
265
Total hours worked
530736
EIN
710427007
Establishment ID
1153014
Employer case #
669882

When (timing detail)

Date of incident
Shift started
7:30:00.000
Time of incident
13:20:00.000
Filing year
2023
Submitted
23FEB24:15:47:00

More injuries at FedEx 5025 TUGGLE RD

View FedEx 5025 TUGGLE RD's full OSHA safety record →

More injuries in this industry (NAICS 492110)

ERLANGER, KY—

CVG RO

More injuries in TN

ALCOA, TN—

WM 672

MADISONVILLE, TN—

WM 366

BRISTOL, TN—

WM 620

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.