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

Washington, DC —

OSHA Injury Report: Grand Hyatt Washington

Injury · Other recordable case

At a glance

On , an injury at Grand Hyatt Washington in 1000 H Street NW, Washington, DC 20001 resulted in other recordable case. Employee was sTEWARD in wASGH.

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

Where did this happen?

Establishment
Grand Hyatt Washington
Parent company
Hyatt Corporation
Street
1000 H Street NW
City
Washington
State
DC
ZIP
20001
On-site location
1B Restaurant Kitchen

What was the outcome?

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

Before the incident

Working at the pot wash area cleaning pot and utensils

What happened

INDIVIDUAL WERE WORKING AT THEIR POT STATION WHERE A COOK PLACED A POT OR PAN CONTAINING HOT WATER WITH EGGS INSIDE. WHEN THE

Injury or illness

Skin Injury - Burn(Heat)

Object or substance involved

Hot water

Summary line

INDIVIDUAL WERE WORKING AT THEIR POT STATION WHERE A COOK PLACED A POT OR PAN CONTAINING HOT WATER WITH EGGS INSIDE. WHEN THE

Employee and industry

Job description
STEWARD
SOC code
35-1012 — First-Line Supervisors of Food Preparation and Serving Workers
NAICS code
721110 — WASGH
NAICS vintage
2012
Avg employees
294
Total hours worked
476792
EIN
941649123
Establishment ID
1062684
Employer case #
202543117

When (timing detail)

Date of incident
Shift started
6:00
Time of incident
10:23
Filing year
2025
Submitted
06FEB26:22:12:00

More injuries at Grand Hyatt Washington

View Grand Hyatt Washington's full OSHA safety record →

More injuries in this industry (NAICS 721110)

More injuries in DC

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.