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

Scottsdale, AR —

OSHA Injury Report: JW Marriott Camelback Inn Resort & Spa

Injury · Days away from work

At a glance

On , an injury at JW Marriott Camelback Inn Resort & Spa in 5402 E Lincoln Dr, Scottsdale, AR 85253 resulted in days away from work. Employee was server in resort hotels without casinos.

Watch JW Marriott Camelback Inn Resort & Spa — free Get an email when a new federal OSHA severe-injury report for JW Marriott Camelback Inn Resort & Spa is published. One employer, no account, unsubscribe in one click.

Where did this happen?

Establishment
JW Marriott Camelback Inn Resort & Spa
Parent company
Marriott Int
Street
5402 E Lincoln Dr
City
Scottsdale
State
AR
ZIP
85253
On-site location
Rita's kitchen

What was the outcome?

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

Before the incident

Serving tables

What happened

As the associate was walking through the swinging doors her finger got stuck in between the frame and the moving door

Injury or illness

Avulsion of nail of left little finger

Object or substance involved

swinging door

Summary line

Avulsion of nail of left little finger

Employee and industry

Job description
Server
SOC code
35-3041 — Food Servers, Nonrestaurant
NAICS code
721110 — Resort hotels without casinos
NAICS vintage
2022
Avg employees
606
Total hours worked
1019679
Establishment ID
1279614
Employer case #
6

When (timing detail)

Date of incident
Time of incident
10:00
Filing year
2024
Submitted
31JAN2025:15:52:00

More injuries at JW Marriott Camelback Inn Resort & Spa

View JW Marriott Camelback Inn Resort & Spa's full OSHA safety record →

More injuries in this industry (NAICS 721110)

More injuries in AR

SPRINGDALE, AR—

WM 2742

Source

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