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

Irvine, CA —

OSHA Injury Report: Trader Joe's 0210 Irvine

Injury · Other recordable case

At a glance

On , an injury at Trader Joe's 0210 Irvine in 6222 Irvine Blvd., Irvine, CA 92620 resulted in other recordable case. Employee was crew in grocery Store.

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

Where did this happen?

Establishment
Trader Joe's 0210 Irvine
Parent company
Trader Joe's
Street
6222 Irvine Blvd.
City
Irvine
State
CA
ZIP
92620
On-site location
Sales Floor

What was the outcome?

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

Before the incident

He was being trained on how to work the frozen section and was trimming a box.

What happened

cut finger with box cutter

Injury or illness

Laceration Left Index Finger

Object or substance involved

Box Cutter

Summary line

[REDACTED] was training in the frozen section and was trimming a box. While he was cutting the box his hand was in the way and cut his finger.

Employee and industry

Job description
Crew
SOC code
35-3023 — Fast Food and Counter Workers
NAICS code
445110 — Grocery Store
NAICS vintage
2022
Avg employees
101
Total hours worked
146704
EIN
951987958
Establishment ID
323132
Employer case #
5

When (timing detail)

Date of incident
Shift started
14:00:00.000
Time of incident
15:30:00.000
Filing year
2023
Submitted
02MAR24:01:51:00

More injuries at Trader Joe's 0210 Irvine

View Trader Joe's 0210 Irvine'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 2023. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.