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

Long Lake, MN —

OSHA Injury Report: Lake Engineering 2085

Injury · Days away from work

At a glance

On , an injury at Lake Engineering 2085 in 2085 Daniels ST P.O. Box 787, Long Lake, MN 55356 resulted in days away from work. Employee was inspector in machine shops.

Where did this happen?

Establishment
Lake Engineering 2085
Parent company
Lake Engineering Inc.
Street
2085 Daniels ST P.O. Box 787
City
Long Lake
State
MN
ZIP
55356
On-site location
West side parking lot

What was the outcome?

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

Before the incident

Employee was walking from his car to the employee entrance to start his shift

What happened

[REDACTED] there was severe fog all over the twin cities which settled and became black ice in our parking lot. The employee 's feet slipped out from underneath him due to the icy conditions causing him to land hard on his right shoulder followed by his head hitting the blacktop

Injury or illness

Torn Rotator Cuff

Object or substance involved

Icy parking lot

Summary line

Torn Rotator Cuff

Employee and industry

Job description
Inspector
SOC code
51-9061 — Inspectors, Testers, Sorters, Samplers, and Weighers
NAICS code
332710 — Machine shops
NAICS vintage
2012
Avg employees
38
Total hours worked
69780
EIN
410881396
Establishment ID
450014
Employer case #
2024-2

When (timing detail)

Date of incident
Shift started
3:59
Time of incident
3:59
Filing year
2024
Submitted
07MAR2025:15:31:00

More injuries at Lake Engineering 2085

View Lake Engineering 2085's full OSHA safety record →

More injuries in this industry (NAICS 332710)

Marana, AZ—

Tucson

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.