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

Glastonbury, CT —

OSHA Injury Report: Trader Joe's 0586 Glastonbury

Injury · Days away from work

At a glance

On , an injury at Trader Joe's 0586 Glastonbury in 400 Hebron Ave., Glastonbury, CT 06033 resulted in days away from work. Employee was crew in grocery Store.

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

Where did this happen?

Establishment
Trader Joe's 0586 Glastonbury
Parent company
Trader Joe's
Street
400 Hebron Ave.
City
Glastonbury
State
CT
ZIP
06033
On-site location
Sales Floor

What was the outcome?

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

Before the incident

Working the grocery section.

What happened

Sore left foot.

Injury or illness

Inflammation Left Foot

Object or substance involved

Case

Summary line

The cart of grocery was stacked too high and when [REDACTED] went to pick up one of the boxes from the cart a full case of fire roasted tomatoes hit her foot leading her to limp in pain.

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
48
Total hours worked
106291
EIN
43294200
Establishment ID
1177929
Employer case #
1

When (timing detail)

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

More injuries at Trader Joe's 0586 Glastonbury

View Trader Joe's 0586 Glastonbury's full OSHA safety record →

More injuries in this industry (NAICS 445110)

AMARILLO, TX—

WM 4464

ALBUQUERQUE, NM—

WM 3385

More injuries in CT

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.