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

Scottsdale, AZ —

OSHA Injury Report: JW Marriott Camelback Inn Resort and Spa

Injury · Other recordable case

At a glance

On , an injury at JW Marriott Camelback Inn Resort and Spa in 5402 E Lincoln Dr, Scottsdale, AZ 85253 resulted in other recordable case. Employee was housekeeper in resort hotels without casinos.

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

Where did this happen?

Establishment
JW Marriott Camelback Inn Resort and Spa
Parent company
Marriott International
Street
5402 E Lincoln Dr
City
Scottsdale
State
AZ
ZIP
85253
On-site location
guest room 591

What was the outcome?

Outcome
Other recordable case (code 4)
Type
Injury (code 1)

Before the incident

cleaning shelf in guest room bathroom

What happened

hit hand against wall while cleaning shelf

Injury or illness

injury of left thumb from hitting hand on wall

Object or substance involved

wall

Summary line

injury of left thumb from hand hitting wall

Employee and industry

Job description
housekeeper
SOC code
37-2012 — Maids and Housekeeping Cleaners
NAICS code
721110 — Resort hotels without casinos
NAICS vintage
2022
Avg employees
590
Total hours worked
834023
Establishment ID
1431146
Employer case #
13

When (timing detail)

Date of incident
Time of incident
14:00
Filing year
2025
Submitted
22JAN26:19:28:00

More injuries at JW Marriott Camelback Inn Resort and Spa

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

More injuries in this industry (NAICS 721110)

More injuries in AZ

SHOW LOW, AZ—

WM 1230

PRESCOTT VALLEY, AZ—

WM 3730

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.