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

Shakopee, MN —

OSHA Injury Report: High Five Erectors II, Inc.

Injury · Other recordable case

At a glance

On , an injury at High Five Erectors II, Inc. in 3005 4th Avenue East, Shakopee, MN 55379 resulted in other recordable case. Employee was iron Worker in iron work, structural, contractors.

Watch High Five Erectors II, Inc. — free Get an email when a new federal OSHA severe-injury report for High Five Erectors II, Inc. is published. One employer, no account, unsubscribe in one click.

Where did this happen?

Establishment
High Five Erectors II, Inc.
Parent company
High Five Erectors II, Inc.
Street
3005 4th Avenue East
City
Shakopee
State
MN
ZIP
55379
On-site location
Jobsite @ 828 Greenway Ave. Oakdale MN

What was the outcome?

Outcome
Other recordable case (code 4)
Type
Injury (code 1)

Before the incident

grinding metal

What happened

Employee was grinding a piece of metal and a small metal shaving got into his left eye.

Injury or illness

left eye foreign body

Object or substance involved

metal shaving

Summary line

left eye foreign body (metal shaving)

Employee and industry

Job description
Iron Worker
SOC code
47-2221 — Structural Iron and Steel Workers
NAICS code
238120 — Iron work, structural, contractors
NAICS vintage
2022
Avg employees
30
Total hours worked
59875
EIN
455118710
Establishment ID
504062
Employer case #
2

When (timing detail)

Date of incident
Shift started
6:00:00.000
Time of incident
13:30:00.000
Filing year
2023
Submitted
01MAR24:16:46:00

More injuries at High Five Erectors II, Inc.

View High Five Erectors II, Inc.'s full OSHA safety record →

More injuries in this industry (NAICS 238120)

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