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

Grand Rapids, MN —

OSHA Injury Report: Itasca County - Transportation Department Employees

Injury · Other recordable case

At a glance

On , an injury at Itasca County - Transportation Department Employees in 123 NE 4th Street, Grand Rapids, MN 55744 resulted in other recordable case. Employee was engineering Materials Technician in bridge, tunnel, and highway operations.

Where did this happen?

Establishment
Itasca County - Transportation Department Employees
Parent company
Itasca County
Street
123 NE 4th Street
City
Grand Rapids
State
MN
ZIP
55744
On-site location
Worksite in Itasca County

What was the outcome?

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

Before the incident

Setting out construction stakes on a worksite.

What happened

Employee was setting construction stakes and took a tree branch to the right eye causing a corneal abrasion.

Injury or illness

Right eye corneal abrasion.

Object or substance involved

Tree branch.

Summary line

Corneal abrasion to right eye from a tree branch scratch.

Employee and industry

Job description
Engineering Materials Technician
SOC code
9999 — Uncoded
NAICS code
488490 — Bridge, tunnel, and highway operations
NAICS vintage
2022
Avg employees
85
Total hours worked
142507
EIN
416005810
Establishment ID
382666
Employer case #
1

When (timing detail)

Date of incident
Shift started
6:30:00.000
Time of incident
10:50:00.000
Filing year
2023
Submitted
01FEB24:22:15:00

More injuries at Itasca County - Transportation Department Employees

View Itasca County - Transportation Department Employees's full OSHA safety record →

More injuries in this industry (NAICS 488490)

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.