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

Sandy Springs, SC —

OSHA Injury Report: US2 Sandy Springs Facility

Injury · Other recordable case

At a glance

On , an injury at US2 Sandy Springs Facility in Hwy 76, Sandy Springs, SC 296770308 resulted in other recordable case. Employee was nZTS Maintenance in motor vehicle tires manufacturing.

Where did this happen?

Establishment
US2 Sandy Springs Facility
Parent company
Michelin North America
Street
Hwy 76
City
Sandy Springs
State
SC
ZIP
296770308
On-site location
ZP Textile

What was the outcome?

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

Before the incident

Trouble shooting a prox switch in ZP Textile

What happened

As the maintenance employee was trouble shooting a moving part engaged pressing left thumb against the frame of the equipment causing a laceration to left thumb

Injury or illness

Laceration to left thumb

Object or substance involved

The moving part that engaged as employee was trouble shooting creating a pinch point between the part and frame of the machine

Summary line

Employee was trouble shooting when a moving part engaged pressing left thumb against the frame of the equipment

Employee and industry

Job description
NZTS Maintenance
SOC code
49-9041 — Industrial Machinery Mechanics
NAICS code
326211 — Motor vehicle tires manufacturing
NAICS vintage
2012
Avg employees
870
Total hours worked
1652800
Establishment ID
344188
Employer case #
2025-ZP-O

When (timing detail)

Date of incident
Shift started
7:00
Time of incident
7:30
Filing year
2025
Submitted
12JAN26:17:37:00

More injuries at US2 Sandy Springs Facility

View US2 Sandy Springs Facility's full OSHA safety record →

More injuries in this industry (NAICS 326211)

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.