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

Lindon, UT —

OSHA Injury Report: Lindon UT

Injury · Days away from work

At a glance

On , an injury at Lindon UT in 1085 West 400 North, Lindon, UT 84042 resulted in days away from work. Employee was chemical Process Tank Technician.

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

Where did this happen?

Establishment
Lindon UT
Parent company
Valmont Industries
Street
1085 West 400 North
City
Lindon
State
UT
ZIP
84042
On-site location
Inside Building - 3103, Maintenance

What was the outcome?

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

Before the incident

Putting away pallets of nickel powder

What happened

On [REDACTED] near the time of [REDACTED] [REDACTED] was in the Kettle Control room putting away two 250 lbs. barrels of nickel powder (16 diameter x 19 high).

Injury or illness

Fracture (Thigh - Right)

Object or substance involved

Pulling

Summary line

On [REDACTED] near the time of [REDACTED] [REDACTED] was in the Kettle Control room putting away two 250 lbs. barrels of nickel powder (16 diameter x 19 high).

Employee and industry

Job description
Chemical Process Tank Technician
SOC code
19-4031 — Chemical Technicians
NAICS code
332812
NAICS vintage
2012
Avg employees
51
Total hours worked
105839
EIN
470351813
Establishment ID
626563
Employer case #
25_4386

When (timing detail)

Date of incident
Shift started
13:00
Time of incident
19:51
Filing year
2025
Submitted
19FEB26:17:52:00

More injuries at Lindon UT

View Lindon UT's full OSHA safety record →

More injuries in this industry (NAICS 332812)

New Carlisle, MI—

Edcoat

More injuries in UT

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.