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

Greenwood, SC —

OSHA Injury Report: VELUX Greenwood - Greenwood,SC

Injury · Job transfer or restriction

At a glance

On , an injury at VELUX Greenwood - Greenwood,SC in PO Box 5001, Greenwood, SC, 29648, Greenwood, SC 29648 resulted in job transfer or restriction. Employee was security Guard in window units, wood and covered wood, manufacturing.

Where did this happen?

Establishment
VELUX Greenwood - Greenwood,SC
Parent company
VELUX Greenwood LLC
Street
PO Box 5001, Greenwood, SC, 29648
City
Greenwood
State
SC
ZIP
29648
On-site location
DC PIV Hill

What was the outcome?

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

Before the incident

walking down hill to check PIV for sprinkler system at [REDACTED]

What happened

The employee walked up the hill at the DC to check PIV. Once checked the employee began to walk down the hill. The hill has grass and was wet. The employee slipped and landed on his rear end.

Injury or illness

lower muscle back strain

Object or substance involved

wet grass on hill

Summary line

lower muscle back strain from slip and trip

Employee and industry

Job description
Security Guard
SOC code
33-9032 — Security Guards
NAICS code
321911 — Window units, wood and covered wood, manufacturing
NAICS vintage
2022
Avg employees
520
Total hours worked
968134
EIN
570681681
Establishment ID
1256084
Employer case #
1

When (timing detail)

Date of incident
Shift started
15:00
Time of incident
19:10
Filing year
2025
Submitted
26JAN26:16:25:00

More injuries at VELUX Greenwood - Greenwood,SC

View VELUX Greenwood - Greenwood,SC's full OSHA safety record →

More injuries in this industry (NAICS 321911)

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.