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: Greystone Construction

Injury · Days away from work

At a glance

On , an injury at Greystone Construction in 2995 Winners Circle Drive, Suite 200, Shakopee, MN 55379 resulted in days away from work. Employee was framer in commercial building construction general contractors.

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

Where did this happen?

Establishment
Greystone Construction
Parent company
Greystone Construction
Street
2995 Winners Circle Drive, Suite 200
City
Shakopee
State
MN
ZIP
55379
On-site location
at the jobsite.

What was the outcome?

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

Before the incident

He was on a boom lift installing a wooden beam .

What happened

The wooden beam felt off place and caught his hand in between the boom guardrail and the beam.

Injury or illness

Injury.

Object or substance involved

The wooden beam.

Summary line

smashed his hand with a beam.

Employee and industry

Job description
Framer
SOC code
47-2031 — Carpenters
NAICS code
236220 — Commercial building construction general contractors
NAICS vintage
2022
Avg employees
140
Total hours worked
313061
EIN
411585072
Establishment ID
1274203
Employer case #
2

When (timing detail)

Date of incident
Shift started
6:00
Time of incident
14:00
Filing year
2024
Submitted
28JAN2025:17:54:00

More injuries at Greystone Construction

View Greystone Construction's full OSHA safety record →

More injuries in this industry (NAICS 236220)

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.