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

Studio City, CA —

OSHA Injury Report: Trader Joe's 0122 Studio City

Injury · Other recordable case

At a glance

On , an injury at Trader Joe's 0122 Studio City in 11976 Ventura Blvd., Studio City, CA 91604 resulted in other recordable case. Employee was crew in grocery Store.

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

Where did this happen?

Establishment
Trader Joe's 0122 Studio City
Parent company
Trader Joe's
Street
11976 Ventura Blvd.
City
Studio City
State
CA
ZIP
91604
On-site location
Backroom

What was the outcome?

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

Before the incident

The Crew Member was working with and handling pallets.

What happened

He was lifting a case of soda water when he felt a pop in his left back side.

Injury or illness

Strain

Object or substance involved

Overexertion

Summary line

He was lifting a case of soda water when he felt a pop in his left back side. Back Strain Overexertion.

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
108
Total hours worked
157793
EIN
951987958
Establishment ID
323065
Employer case #
6

When (timing detail)

Date of incident
Shift started
15:00
Time of incident
20:10
Filing year
2025
Submitted
16FEB26:22:57:00

More injuries at Trader Joe's 0122 Studio City

View Trader Joe's 0122 Studio City'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.