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

Rancho Cucamonga, CA —

OSHA Injury Report: Trader Joe's 0217 Rancho Cucamonga

Injury · Days away from work

At a glance

On , an injury at Trader Joe's 0217 Rancho Cucamonga in 6401 Haven Ave., Rancho Cucamonga, CA 91737 resulted in days away from work. Employee was crew in grocery Store.

Watch Trader Joe's 0217 Rancho Cucamonga — free Get an email when a new federal OSHA severe-injury report for Trader Joe's 0217 Rancho Cucamonga is published. One employer, no account, unsubscribe in one click.

Where did this happen?

Establishment
Trader Joe's 0217 Rancho Cucamonga
Parent company
Trader Joe's
Street
6401 Haven Ave.
City
Rancho Cucamonga
State
CA
ZIP
91737
On-site location
Sales Floor

What was the outcome?

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

Before the incident

Emptying the trash can.

What happened

Crew Member cut her finger on her left hand with the box cutter.

Injury or illness

Laceration

Object or substance involved

Box cutter

Summary line

Crew Member cut her finger on her left hand with the box cutter. Finger Laceration Box cutter.

Employee and industry

Job description
Crew
SOC code
35-3023 — Fast Food and Counter Workers
NAICS code
445110 — Grocery Store
NAICS vintage
2012
Avg employees
122
Total hours worked
167172
EIN
951987958
Establishment ID
323139
Employer case #
6

When (timing detail)

Date of incident
Shift started
14:00
Time of incident
21:40
Filing year
2025
Submitted
16FEB26:22:57:00

More injuries at Trader Joe's 0217 Rancho Cucamonga

View Trader Joe's 0217 Rancho Cucamonga's full OSHA safety record →

More injuries in this industry (NAICS 445110)

AMARILLO, TX—

WM 4464

ALBUQUERQUE, NM—

WM 3385

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.