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

Ontario, CA —

OSHA Injury Report: OrePac Building Products - Ontario

Injury · Days away from work

At a glance

On , an injury at OrePac Building Products - Ontario in 2401 E Philadelphia, Ontario, CA 91761 resulted in days away from work. Employee was building Products Merchandiser in lumber (e.g., dressed, finished, rough) merchant wholesalers.

Where did this happen?

Establishment
OrePac Building Products - Ontario
Parent company
OrePac Holding Company
Street
2401 E Philadelphia
City
Ontario
State
CA
ZIP
91761
On-site location
Customer Location - Sand Diego

What was the outcome?

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

Before the incident

restocking molding

What happened

Building Products Merchandiser was restocking molding lifting and turning allot and he started having pain from his left hip down through the back of his left leg.

Injury or illness

Sprain Strain (Hip - Left) Sprain Strain (Lower Back)

Object or substance involved

molding

Summary line

Sprain Strain (Hip - Left) Sprain Strain (Lower Back) while lifting

Employee and industry

Job description
Building Products Merchandiser
SOC code
9999 — Uncoded
NAICS code
423310 — Lumber (e.g., dressed, finished, rough) merchant wholesalers
NAICS vintage
2022
Avg employees
121
Total hours worked
258924
EIN
930670556
Establishment ID
866067
Employer case #
23_443

When (timing detail)

Date of incident
Shift started
7:30:00.000
Time of incident
20:00:00.000
Submitted
02MAR24:20:48:00

More injuries at OrePac Building Products - Ontario

View OrePac Building Products - Ontario's full OSHA safety record →

More injuries in this industry (NAICS 423310)

More injuries in CA

Rancho Cucamonga, CA—

087-RCDC

Source

Data from OSHA ITA Form 300/301 electronic submissions, filing year unspecified. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.