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

LANSING, MI —

OSHA Injury Report: FedEx ZLNS G LANSING 489

Injury · Job transfer or restriction

At a glance

On , an injury at FedEx ZLNS G LANSING 489 in 2290 S CANAL ROAD, LANSING, MI 48917 resulted in job transfer or restriction. Employee was package Handler in courier and Express Delivery Services.

Watch FedEx Zlns G Lansing 489 — free Get an email when a new federal OSHA severe-injury report for FedEx Zlns G Lansing 489 is published. One employer, no account, unsubscribe in one click.

Where did this happen?

Establishment
FedEx ZLNS G LANSING 489
Parent company
FEDERAL EXPRESS CORPORATION
Street
2290 S CANAL ROAD
City
LANSING
State
MI
ZIP
48917
On-site location
TRAILER UNLOAD

What was the outcome?

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

Before the incident

SCANNING

What happened

EE was scanning on the LP door when a LP fell into her back

Injury or illness

Bruised Bilateral Low back Struck by object Package

Object or substance involved

Package

Summary line

EE was scanning on the LP door when a LP fell into her back

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
211
Total hours worked
139862
EIN
710427007
Establishment ID
1367469
Employer case #
126520

When (timing detail)

Date of incident
Shift started
2:30
Time of incident
5:20
Filing year
2024
Submitted
28FEB2025:01:23:00

More injuries at FedEx ZLNS G LANSING 489

View FedEx ZLNS G LANSING 489's full OSHA safety record →

More injuries in this industry (NAICS 492110)

ERLANGER, KY—

CVG RO

More injuries in MI

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.