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

LEBANON, TN —

OSHA Injury Report: FedEx LERS G LEBANON RSF 378

Injury · Job transfer or restriction

At a glance

On , an injury at FedEx LERS G LEBANON RSF 378 in 1050 RICHARD PETTY WAY, LEBANON, TN 37090 resulted in job transfer or restriction. Employee was package Handler in courier and Express Delivery Services.

Where did this happen?

Establishment
FedEx LERS G LEBANON RSF 378
Parent company
FEDERAL EXPRESS CORPORATION
Street
1050 RICHARD PETTY WAY
City
LEBANON
State
TN
ZIP
37090
On-site location
TRAILER UNLOAD

What was the outcome?

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

Before the incident

UNLOADING

What happened

EE was unloading the bottom of trailer Went to lift a package and hit his thumb on the side of the rollers

Injury or illness

Bruised Right Thumb Cut punctured scraped Roller

Object or substance involved

Roller

Summary line

EE was unloading the bottom of trailer Went to lift a package and hit his thumb on the side of the rollers

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
409
Total hours worked
251707
EIN
710427007
Establishment ID
1367081
Employer case #
142875

When (timing detail)

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

More injuries at FedEx LERS G LEBANON RSF 378

View FedEx LERS G LEBANON RSF 378'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 2024. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.