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

Park City, UT —

OSHA Injury Report: WG Park City Resort & Spa - UT03

Injury · Job transfer or restriction

At a glance

On , an injury at WG Park City Resort & Spa - UT03 in 3000 The Canyons Resorts Drive, Park City, UT 84098 resulted in job transfer or restriction. Employee was inventory Clerk in hotels (except casino hotels) with golf courses, tennis courts, and/or other health spa facilities (i.e., resorts).

Where did this happen?

Establishment
WG Park City Resort & Spa - UT03
Parent company
Westgate Resorts
Street
3000 The Canyons Resorts Drive
City
Park City
State
UT
ZIP
84098
On-site location
Sidewalk

What was the outcome?

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

Before the incident

Working with a pallet [REDACTED] moving supplies.

What happened

Reported while twisting he felt a pop in his right elbow.

Injury or illness

Right full thickness biceps rupture

Object or substance involved

Pallet Jack

Summary line

Right elbow pain working with [REDACTED].

Employee and industry

Job description
Inventory Clerk
SOC code
39-3091 — Amusement and Recreation Attendants
NAICS code
721110 — Hotels (except casino hotels) with golf courses, tennis courts, and/or other health spa facilities (i.e., resorts)
NAICS vintage
2022
Avg employees
221
Total hours worked
327577
EIN
593350936
Establishment ID
290366
Employer case #
23-511-357

When (timing detail)

Date of incident
Shift started
8:00:00.000
Time of incident
12:00:00.000
Filing year
2023
Submitted
09FEB24:18:49:00

More injuries at WG Park City Resort & Spa - UT03

View WG Park City Resort & Spa - UT03's full OSHA safety record →

More injuries in this industry (NAICS 721110)

More injuries in UT

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.