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

Fountain Inn, SC —

OSHA Injury Report: Rich Products Fountain Inn

Injury · Job transfer or restriction

At a glance

On , an injury at Rich Products Fountain Inn in 1405 South Main St., Fountain Inn, SC 29644 resulted in job transfer or restriction. Employee was quality Tech in commercial bakeries.

Watch Rich Products Fountain Inn — free Get an email when a new federal OSHA severe-injury report for Rich Products Fountain Inn is published. One employer, no account, unsubscribe in one click.

Where did this happen?

Establishment
Rich Products Fountain Inn
Parent company
Rich Products Corporations
Street
1405 South Main St.
City
Fountain Inn
State
SC
ZIP
29644
On-site location
L3 Liquifier

What was the outcome?

Outcome
Job transfer or restriction (code 3)
Type
Injury (code 1)
Days restricted or transferred
14

Before the incident

checking lot numbers on pallets of ingredients

What happened

Assoc. slipped on the floor and fell

Injury or illness

cervicalgia & low back pain

Object or substance involved

floor

Summary line

Strain to the right shoulder from having the smock caught on a drive shaft of the box former

Employee and industry

Job description
Quality Tech
SOC code
51-9061 — Inspectors, Testers, Sorters, Samplers, and Weighers
NAICS code
311812 — Commercial bakeries
NAICS vintage
2012
Avg employees
192
Total hours worked
431384
EIN
160903761
Establishment ID
297864
Employer case #
5

When (timing detail)

Date of incident
Shift started
5:00
Time of incident
5:13
Filing year
2024
Submitted
01MAR2025:01:48:00

More injuries at Rich Products Fountain Inn

View Rich Products Fountain Inn's full OSHA safety record →

More injuries in this industry (NAICS 311812)

More injuries in SC

GAFFNEY, SC—

WM 638

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.