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

Lexington, SC —

OSHA Injury Report: Lexington RSC

Injury · Job transfer or restriction

At a glance

On , an injury at Lexington RSC in 170 Longs Pond Road, Lexington, SC 29072 resulted in job transfer or restriction. Employee was order Filler in general Warehousing and Storage.

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

Where did this happen?

Establishment
Lexington RSC
Parent company
Do it Best Corp.
Street
170 Longs Pond Road
City
Lexington
State
SC
ZIP
29072
On-site location
Section E

What was the outcome?

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

Before the incident

Picked a a bag of bird seed in Sec. E

What happened

When picking the bag of bird seed the bag opened and seed flew out and struck eye

Injury or illness

Foreign substance in right eye contacted eye

Object or substance involved

Bird seed foreign substance

Summary line

bird seed struck entered eye from open bag

Employee and industry

Job description
Order Filler
SOC code
53-7065 — Stockers and Order Fillers
NAICS code
493110 — General Warehousing and Storage
NAICS vintage
2012
Avg employees
150
Total hours worked
257607
EIN
350792867
Establishment ID
168031
Employer case #
240903-L-2

When (timing detail)

Date of incident
Shift started
6:00
Time of incident
6:30
Filing year
2024
Submitted
03FEB2025:14:06:00

More injuries at Lexington RSC

View Lexington RSC's full OSHA safety record →

More injuries in this industry (NAICS 493110)

Rancho Cucamonga, CA—

087-RCDC

MATTESON, IL—

WM 6504

COLDWATER, MI—

WM 6043

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.