Safety Incidents OSHA Severe Injury Reports · 2015–2025
2,098,129Injury reports 132,232Establishments Most recent incident 2025-12-31

Norco, CA —

OSHA Injury Report: Guy Yocom Construction, Inc.

Injury · Days away from work

At a glance

On , an injury at Guy Yocom Construction, Inc. in 3299 Horseless Carriage Lane ST H, Norco, CA 92860 resulted in days away from work. Employee was laborer in retaining wall (except anchored earth), poured concrete, construction.

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

Where did this happen?

Establishment
Guy Yocom Construction, Inc.
Parent company
Guy Yocom Construcion, Inc.
Street
3299 Horseless Carriage Lane ST H
City
Norco
State
CA
ZIP
92860
On-site location
Santa Rosa Project

What was the outcome?

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

Before the incident

walking on concrete

What happened

Worker walking on concrete when he stepped on rebar and twisted right ankle.

Injury or illness

Twisted right ankle

Object or substance involved

rebar

Summary line

Twisted right ankle walking on concrete

Employee and industry

Job description
Laborer
SOC code
47-2061 — Construction Laborers
NAICS code
238110 — Retaining wall (except anchored earth), poured concrete, construction
NAICS vintage
2012
Avg employees
795
Total hours worked
1691493
Establishment ID
394211
Employer case #
5

When (timing detail)

Date of incident
Shift started
6:30
Time of incident
7:30
Filing year
2025
Submitted
28JAN26:15:20:00

More injuries at Guy Yocom Construction, Inc.

View Guy Yocom Construction, Inc.'s full OSHA safety record →

More injuries in this industry (NAICS 238110)

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.