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: 134 LANSING MI

Injury · Days away from work

At a glance

On , an injury at 134 LANSING MI in 3307 S CREYTS RD, LANSING, MI 48917 resulted in days away from work. Employee was wAREHOUSE HANDLER in general Warehousing and Storage.

Where did this happen?

Establishment
134 LANSING MI
Parent company
FHI LLC
Street
3307 S CREYTS RD
City
LANSING
State
MI
ZIP
48917
On-site location
WAREHOUSE

What was the outcome?

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

Before the incident

UNLOADING PRODUCT

What happened

EMPLOYEE WAS ENTERING A PALLET WHEN THE EQUIPMENT BECAME STUCK AS HE ATTEMPTED TO PULL ON THE PALLET TO DISLODGE IT HIS FOOT SLIPPED AND BECAME WEDGED UNDER THE REAR OF THE EQUIPMENT

Injury or illness

LOWER EXTREMITIES TOE S CAUGHT IN BETWEEN Injury

Object or substance involved

EQUIPMENT

Summary line

EMPLOYEE WAS ENTERING A PALLET WHEN THE EQUIPMENT BECAME STUCK AS HE ATTEMPTED TO PULL ON THE PALLET TO DISLODGE IT HIS FOOT SLIPPED AND BECAME WEDGED UNDER THE REAR OF THE EQUIPMENT

Employee and industry

Job description
WAREHOUSE HANDLER
SOC code
53-7062 — Laborers and Freight, Stock, and Material Movers, Hand
NAICS code
493110 — General Warehousing and Storage
NAICS vintage
2012
Avg employees
290
Total hours worked
519880
EIN
562174318
Establishment ID
1026693
Employer case #
F8M5645

When (timing detail)

Date of incident
Shift started
0:18
Time of incident
9:00
Filing year
2025
Submitted
03MAR26:21:34:00

More injuries at 134 LANSING MI

View 134 LANSING MI's full OSHA safety record →

More injuries in this industry (NAICS 493110)

Rancho Cucamonga, CA—

087-RCDC

MATTESON, IL—

WM 6504

COLDWATER, MI—

WM 6043

More injuries in MI

Source

Data from OSHA ITA Form 300/301 electronic submissions, filing year 2025. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.