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

SUMTER, SC —

OSHA Injury Report: Pilgrim's sumter Fresh Processing

Other illness · Days away from work

At a glance

On , an other illness at Pilgrim's sumter Fresh Processing in 2050 HIGHWAY 15 SOUTH, SUMTER, SC 29150 resulted in days away from work. Employee was baggerparts in poultry slaughtering, dressing, and packing.

Where did this happen?

Establishment
Pilgrim's sumter Fresh Processing
Parent company
Pilgrim's Sumter Fresh Processing
Street
2050 HIGHWAY 15 SOUTH
City
SUMTER
State
SC
ZIP
29150
On-site location
Debone

What was the outcome?

Outcome
Days away from work (code 2)
Type
Other illness (code 6)
Days away from work
3

Before the incident

In [REDACTED] and moved to a line to help move boxes

What happened

In [REDACTED] and moved to a line to help move boxes was supposed to push the boxes down the line but the line started to back up so started lifting boxes to speed things along and developed right rib chest pain.

Injury or illness

Strain Sprain right thorax

Object or substance involved

Repetitive lifting

Summary line

Strain sprain right [REDACTED] from repetitive lifting

Employee and industry

Job description
Baggerparts
SOC code
00-9900 — Insufficient Information - NIOSH
NAICS code
311615 — Poultry slaughtering, dressing, and packing
NAICS vintage
2012
Avg employees
976
Total hours worked
1580865
EIN
751285071
Establishment ID
1045750
Employer case #
139975

When (timing detail)

Date of incident
Shift started
17:15
Time of incident
1:45
Filing year
2025
Submitted
14JAN26:19:12:00

More injuries at Pilgrim's sumter Fresh Processing

View Pilgrim's sumter Fresh Processing's full OSHA safety record →

More injuries in this industry (NAICS 311615)

More injuries in SC

GAFFNEY, SC—

WM 638

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.