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

MERCED, CA —

OSHA Injury Report: California Department of Transportation Facility 320

Injury · Other recordable case

At a glance

On , an injury at California Department of Transportation Facility 320 in 1801 MOTEL DRIVE, MERCED, CA 95340 resulted in other recordable case. Employee was cT Equipment Operator II in repair highway road street bridge or airport runway.

Where did this happen?

Establishment
California Department of Transportation Facility 320
Parent company
Facility 320
Street
1801 MOTEL DRIVE
City
MERCED
State
CA
ZIP
95340
On-site location
Freeway Ramp

What was the outcome?

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

Before the incident

Employee was performing duties at EE was holding branch for the chainsaw operator when the chainsaw moved up and cut his forearm..

What happened

Incident occurred: EE was holding branch for the chainsaw operator when the chainsaw moved up and cut his forearm.

Injury or illness

Employee sustained an injury during the incident.

Object or substance involved

Chainsaw involved in the incident.

Summary line

EE was holding branch for the chainsaw operator when the chainsaw moved up and cut his forearm.

Employee and industry

Job description
CT Equipment Operator II
SOC code
47-2073 — Operating Engineers and Other Construction Equipment Operators
NAICS code
237310 — Repair highway road street bridge or airport runway
NAICS vintage
2012
Avg employees
939
Total hours worked
1878000
EIN
946001347
Establishment ID
731588
Employer case #
PII-10-25

When (timing detail)

Date of incident
Time of incident
10:00
Filing year
2025
Submitted
11FEB26:22:34:00

More injuries in this industry (NAICS 237310)

More injuries in CA

Rancho Cucamonga, CA—

087-RCDC

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.