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

Litchfield, MN —

OSHA Injury Report: Litchfield, MN

Injury · Other recordable case

At a glance

On , an injury at Litchfield, MN in 520 Polydome Dr., Litchfield, MN 55355 resulted in other recordable case. Employee was manufacturing Technician I in construction-type tractors and attachments manufacturing.

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

Where did this happen?

Establishment
Litchfield, MN
Parent company
Bobcat
Street
520 Polydome Dr.
City
Litchfield
State
MN
ZIP
55355
On-site location
FO3-Bay4

What was the outcome?

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

Before the incident

While touching up robot piece of weld slag got caught in operators eye

What happened

EE was touching up a robot and sparked the weld and got slag in his eye

Injury or illness

Foreign Body

Object or substance involved

Weld Slag

Summary line

Foreign Body to Eye caused by Weld Slag

Employee and industry

Job description
Manufacturing Technician I
SOC code
17-3026 — Industrial Engineering Technologists and Technicians
NAICS code
333120 — Construction-type tractors and attachments manufacturing
NAICS vintage
2022
Avg employees
293
Total hours worked
587766
EIN
380425350
Establishment ID
1182373
Employer case #
IN-202503

When (timing detail)

Date of incident
Shift started
6:00
Time of incident
14:00
Filing year
2025
Submitted
26JAN26:16:15:00

More injuries at Litchfield, MN

View Litchfield, MN's full OSHA safety record →

More injuries in this industry (NAICS 333120)

Elizabethtown, KY—

Etown

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.