2,098,129Injury reports 132,232Establishments Most recent incident 2025-12-31
Safety Incidents OSHA Severe Injury Reports · 2015–2025

NASHVILLE, TN —

OSHA Injury Report: DOUBLETREE NASHVILLE

Injury · Job transfer or restriction

At a glance

On , an injury at DOUBLETREE NASHVILLE in 315 4TH AVENUE N, NASHVILLE, TN 37219 resulted in job transfer or restriction. Employee was banquet server in hotels (except casino hotels).

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

Where did this happen?

Establishment
DOUBLETREE NASHVILLE
Parent company
SPIRE HOSPITALITY - EMPLOYER
Street
315 4TH AVENUE N
City
NASHVILLE
State
TN
ZIP
37219
On-site location
Kitchen

What was the outcome?

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

Before the incident

Team member was slicing lemon wheels to add to water glasses at lunch.

What happened

Team member cut the end of his finger while utilizing a mandolin to slice lemons.

Injury or illness

Avulsion of skin of right thumb.

Object or substance involved

Mandolin slicer.

Summary line

Avulsion of skin of thumb

Employee and industry

Job description
Banquet server
SOC code
35-3031 — Waiters and Waitresses
NAICS code
721110 — Hotels (except casino hotels)
NAICS vintage
2012
Avg employees
110
Total hours worked
138214
EIN
363087906
Establishment ID
590978
Employer case #
2

When (timing detail)

Date of incident
Shift started
10:24
Time of incident
11:10
Filing year
2025
Submitted
27FEB26:02:38:00

More injuries at DOUBLETREE NASHVILLE

View DOUBLETREE NASHVILLE's full OSHA safety record →

More injuries in this industry (NAICS 721110)

More injuries in TN

ALCOA, TN—

WM 672

MADISONVILLE, TN—

WM 366

BRISTOL, TN—

WM 620

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.