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

Charlotte, NC —

OSHA Injury Report: Hilton Charlotte Center City

Injury · Days away from work

At a glance

On , an injury at Hilton Charlotte Center City in 222 E. Third Street, Charlotte, NC 28202 resulted in days away from work. Employee was food and Beverage Cashier in hotels (except casino hotels).

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

Where did this happen?

Establishment
Hilton Charlotte Center City
Parent company
Charlotte N.C. Hotel Corporation
Street
222 E. Third Street
City
Charlotte
State
NC
ZIP
28202
On-site location
Restaurant/Bar area

What was the outcome?

Outcome
Days away from work (code 2)
Type
Injury (code 1)
Days away from work
2

Before the incident

Cutting fruit garnishes

What happened

She cut her left ring and pinky fingers with a fruit peeler

Injury or illness

Cut to left ring and pinky fingers

Object or substance involved

fruit peeler

Summary line

cut to left ring and pinky fingers fruit peeler

Employee and industry

Job description
Food and Beverage Cashier
SOC code
2612155 — Food Service Managers
NAICS code
721110 — Hotels (except casino hotels)
NAICS vintage
2012
Avg employees
100
Total hours worked
173078
EIN
432081016
Establishment ID
441852
Employer case #
2

When (timing detail)

Date of incident
Shift started
16:00
Time of incident
17:00
Filing year
2025
Submitted
25FEB26:23:20:00

More injuries at Hilton Charlotte Center City

View Hilton Charlotte Center City's full OSHA safety record →

More injuries in this industry (NAICS 721110)

More injuries in NC

FAYETTEVILLE, NC—

WM 8218

GREENSBORO, NC—

WM 6402

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.