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

Atlanta, GA —

OSHA Injury Report: Grand Hyatt Atlanta in Buckhead

Injury · Other recordable case

At a glance

On , an injury at Grand Hyatt Atlanta in Buckhead in 3300 Peachtree Road NE, Atlanta, GA 30305 resulted in other recordable case. Employee was cook in aTLGH.

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

Where did this happen?

Establishment
Grand Hyatt Atlanta in Buckhead
Parent company
Hyatt Corporation
Street
3300 Peachtree Road NE
City
Atlanta
State
GA
ZIP
30305
On-site location
Kitchen

What was the outcome?

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

Before the incident

Cutting melon.

What happened

EE states while preparing food cutting fruit finger resting on cutting board knife struck L 4th finger causing cut bleeding.

Injury or illness

Skin Injury - Cut laceration puncture

Object or substance involved

Serrated Knife

Summary line

EE states while preparing food cutting fruit finger resting on cutting board knife struck L 4th finger causing cut bleeding.

Employee and industry

Job description
Cook
SOC code
35-2019 — Cooks, All Other
NAICS code
721110 — ATLGH
NAICS vintage
2012
Avg employees
121
Total hours worked
195519
EIN
941649123
Establishment ID
1062573
Employer case #
00719826

When (timing detail)

Date of incident
Shift started
6:17
Time of incident
8:30
Filing year
2024
Submitted
03FEB2025:21:13:00

More injuries at Grand Hyatt Atlanta in Buckhead

View Grand Hyatt Atlanta in Buckhead's full OSHA safety record →

More injuries in this industry (NAICS 721110)

More injuries in GA

EASTANOLLEE, GA—

WM 1122

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.