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

Folsom, CA —

OSHA Injury Report: 10447 Folsom

Injury · Other recordable case

At a glance

On , an injury at 10447 Folsom in 270 Palladio Parkway, Folsom, CA 95630 resulted in other recordable case. Employee was s Grocery Service Team Member.

Where did this happen?

Establishment
10447 Folsom
Street
270 Palladio Parkway
City
Folsom
State
CA
ZIP
95630
On-site location
Grocery

What was the outcome?

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

Before the incident

Lifting a case of canned tomatos.

What happened

TM was lifting a case of tomato cans from the bottom level of a small two compartment shopping cart and felt something in her back. She reported it 2 weeks after the incident happened and had been treating with a chiropractor during that time.

Injury or illness

Strain Sprain Multiple Injuries

Object or substance involved

Box barrel container

Summary line

TM was lifting a case of tomato cans from the bottom level of a small two compartment shopping cart and felt something in her back. She reported it 2 weeks after the incident happened and had been treating with a chiropractor during that time.

Employee and industry

Job description
S Grocery Service Team Member
SOC code
9999 — Uncoded
NAICS code
445110
NAICS vintage
2012
Avg employees
160
Total hours worked
245465
EIN
742489930
Establishment ID
715800
Employer case #
0005772233

When (timing detail)

Date of incident
Shift started
13:00
Time of incident
12:00
Filing year
2024
Submitted
01MAR2025:19:41:00

More injuries at 10447 Folsom

View 10447 Folsom'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 2024. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.