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

Lincolnton, NC —

OSHA Injury Report: Lincolnton Rehabilitation Center

Injury · Days away from work

At a glance

On , an injury at Lincolnton Rehabilitation Center in 1410 East Gaston Street, Lincolnton, NC 28092 resulted in days away from work. Employee was cook in skilled nursing facilities.

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

Where did this happen?

Establishment
Lincolnton Rehabilitation Center
Parent company
Sovereign Carolina Holdings, LLC
Street
1410 East Gaston Street
City
Lincolnton
State
NC
ZIP
28092
On-site location
Kitchen

What was the outcome?

Outcome
Days away from work (code 2)
Type
Injury (code 1)
Days away from work
2
Days restricted or transferred
6

Before the incident

Preparing meals

What happened

Employee felt pain in low back while transferring a large bucket of soup

Injury or illness

Low back strain

Object or substance involved

Bucket of soup

Summary line

Employee felt pain in low back while transferring a large bucket of soup

Employee and industry

Job description
Cook
SOC code
35-2012 — Cooks, Institution and Cafeteria
NAICS code
623110 — Skilled nursing facilities
NAICS vintage
2022
Avg employees
126
Total hours worked
196467
EIN
465031455
Establishment ID
168429
Employer case #
R2023054

When (timing detail)

Date of incident
Filing year
2023
Submitted
29FEB24:18:59:00

More injuries at Lincolnton Rehabilitation Center

View Lincolnton Rehabilitation Center's full OSHA safety record →

More injuries in this industry (NAICS 623110)

More injuries in NC

FAYETTEVILLE, NC—

WM 8218

GREENSBORO, NC—

WM 6402

Source

Data from OSHA ITA Form 300/301 electronic submissions, filing year 2023. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.