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

Injury · Job transfer or restriction

At a glance

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

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

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
VAN

What was the outcome?

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

Before the incident

COMING OUT OF TRAILER

What happened

Rolled right ankle coming out of truck

Injury or illness

Sprained Right Ankle Slipped Ground

Object or substance involved

Ground

Summary line

Rolled right ankle coming out of truck

Employee and industry

Job description
Seasonal Packag
SOC code
43-5021 — Couriers and Messengers
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 #
261950

When (timing detail)

Date of incident
Shift started
0:01
Time of incident
1:00
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.