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

Easley, SC —

OSHA Injury Report: Yokohama Industries Americas South Carolina, LLC

Injury · Job transfer or restriction

At a glance

On , an injury at Yokohama Industries Americas South Carolina, LLC in 109 Gillespie Drive, Easley, SC 29640 resulted in job transfer or restriction. Employee was team Member in automotive, truck and bus steering assemblies and parts manufacturing.

Where did this happen?

Establishment
Yokohama Industries Americas South Carolina, LLC
Parent company
Yokohama Industries America Inc.
Street
109 Gillespie Drive
City
Easley
State
SC
ZIP
29640
On-site location
Coupling Assembly (CA) EF-005/RB10/11/12

What was the outcome?

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

Before the incident

Working with the robot machines in [REDACTED].

What happened

Developed pain in his right shoulder due to tendonitis and repetitive motion.

Injury or illness

Tendonitis in his right shoulder.

Object or substance involved

Repetitive motion.

Summary line

Right Shoulder pain due to tendonitis

Employee and industry

Job description
Team Member
SOC code
00-9900 — Insufficient Information - NIOSH
NAICS code
336330 — Automotive, truck and bus steering assemblies and parts manufacturing
NAICS vintage
2012
Avg employees
372
Total hours worked
708582
EIN
264722473
Establishment ID
953268
Employer case #
L288

When (timing detail)

Date of incident
Shift started
5:00
Time of incident
12:00
Filing year
2025
Submitted
28JAN26:12:56:00

More injuries at Yokohama Industries Americas South Carolina, LLC

View Yokohama Industries Americas South Carolina, LLC's full OSHA safety record →

More injuries in this industry (NAICS 336330)

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.