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 · Other recordable case

At a glance

On , an injury at Guy Yocom Construction, Inc. in 3299 Horseless Carriage Lane ST H, Norco, CA 92860 resulted in other recordable case. 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
Fullerton Project near wall forms

What was the outcome?

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

Before the incident

Lifting a wall form

What happened

Worker was team lifting a form and felt pain in lower back

Injury or illness

Strain lower back

Object or substance involved

Wall Form

Summary line

Lifting wooden form and felt pain in his lower back

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
952
Total hours worked
1998720
Establishment ID
394211
Employer case #
17

When (timing detail)

Date of incident
Shift started
6:00
Time of incident
7:00
Filing year
2024
Submitted
27FEB2025:17:33: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 2024. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.