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

Staples, MN —

OSHA Injury Report: Voyager Industries, Inc.- Staples

Injury · Job transfer or restriction

At a glance

On , an injury at Voyager Industries, Inc.- Staples in 501 Prairie Ave NW, Staples, MN 56479 resulted in job transfer or restriction. Employee was assembler in travel trailers, recreational, manufacturing.

Where did this happen?

Establishment
Voyager Industries, Inc.- Staples
Parent company
Voyager Industries, Inc.
Street
501 Prairie Ave NW
City
Staples
State
MN
ZIP
56479
On-site location
Yetti Bay 2

What was the outcome?

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

Before the incident

Lifting an aluminum door out of the pallet storage for a fish house

What happened

employee lifted upwards and backwards at the same time and the door got caught in the slot of the pallet so it gave resistance to the employee pulling and they felt pain in their lower back

Injury or illness

strained back

Object or substance involved

lifting aluminum door

Summary line

Strain to lower back from lifting aluminum door

Employee and industry

Job description
Assembler
SOC code
51-2099 — Assemblers and Fabricators, All Other
NAICS code
336214 — Travel trailers, recreational, manufacturing
NAICS vintage
2012
Avg employees
14
Total hours worked
30215
Establishment ID
960455
Employer case #
2

When (timing detail)

Date of incident
Shift started
5:00
Time of incident
7:30
Filing year
2025
Submitted
03MAR26:14:29:00

More injuries at Voyager Industries, Inc.- Staples

View Voyager Industries, Inc.- Staples's full OSHA safety record →

More injuries in this industry (NAICS 336214)

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 2025. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.