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

San Francisco, CA —

OSHA Injury Report: Grand Hyatt San Francisco

Injury · Other recordable case

At a glance

On , an injury at Grand Hyatt San Francisco in 345 Stockton Street, San Francisco, CA 94108 resulted in other recordable case. Employee was sECURITY OFFICER in sFOUS.

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

Where did this happen?

Establishment
Grand Hyatt San Francisco
Parent company
Hyatt Corporation
Street
345 Stockton Street
City
San Francisco
State
CA
ZIP
94108
On-site location
On the 19th floor stairwell 1A

What was the outcome?

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

Before the incident

patrolling

What happened

EE STATES PATROLLING WHEN BALCONY DOOR SLAMMED SHUT IN WIND INJURING AND SWELLING RIGHT INDEX FINGER.

Injury or illness

Bone Joint Injury - Crush

Object or substance involved

emergency door

Summary line

EE STATES PATROLLING WHEN BALCONY DOOR SLAMMED SHUT IN WIND INJURING AND SWELLING RIGHT INDEX FINGER.

Employee and industry

Job description
SECURITY OFFICER
SOC code
33-9031 — Gambling Surveillance Officers and Gambling Investigators
NAICS code
721110 — SFOUS
NAICS vintage
2012
Avg employees
265
Total hours worked
413100
EIN
941649123
Establishment ID
1062899
Employer case #
878778

When (timing detail)

Date of incident
Shift started
15:00
Time of incident
17:17
Filing year
2025
Submitted
06FEB26:22:12:00

More injuries at Grand Hyatt San Francisco

View Grand Hyatt San Francisco's full OSHA safety record →

More injuries in this industry (NAICS 721110)

More injuries in CA

Rancho Cucamonga, CA—

087-RCDC

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.