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

ROGERS, MN —

OSHA Injury Report: FedEx ZMPG G MAPLE GROVE 553

Other illness · Job transfer or restriction

At a glance

On , an other illness at FedEx ZMPG G MAPLE GROVE 553 in 19705 ROGERS DRIVE, ROGERS, MN 55374 resulted in job transfer or restriction. Employee was package Handler in courier and Express Delivery Services.

Where did this happen?

Establishment
FedEx ZMPG G MAPLE GROVE 553
Parent company
FEDERAL EXPRESS CORPORATION
Street
19705 ROGERS DRIVE
City
ROGERS
State
MN
ZIP
55374
On-site location
TRAILER LOAD

What was the outcome?

Outcome
Job transfer or restriction (code 3)
Type
Other illness (code 6)
Days restricted or transferred
58

Before the incident

LOADING A TRAILER

What happened

Package handler was loading in a trailer While loading he started to feel sharppain in his left wrist

Injury or illness

Sprained Left Wrist Repetitive Motion Packages

Object or substance involved

Packages

Summary line

Package handler was loading in a trailer While loading he started to feel sharppain in his left wrist

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
554
Total hours worked
370280
EIN
710427007
Establishment ID
1367504
Employer case #
267838

When (timing detail)

Date of incident
Shift started
10:30
Time of incident
13:30
Filing year
2024
Submitted
28FEB2025:01:23:00

More injuries at FedEx ZMPG G MAPLE GROVE 553

View FedEx ZMPG G MAPLE GROVE 553's full OSHA safety record →

More injuries in this industry (NAICS 492110)

ERLANGER, KY—

CVG RO

More injuries in MN

BROOKLYN PARK, MN—

WM 1864

OAK PARK HEIGHTS, MN—

WM 1861

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.