Safety Incidents OSHA Severe Injury Reports · 2015–2025
2,098,129Injury reports 132,232Establishments Most recent incident 2025-12-31

Golden Oak, FL —

OSHA Injury Report: Four Seasons Resort Orlando

Injury · Days away from work

At a glance

On , an injury at Four Seasons Resort Orlando in 10100 Dream Tree Boulevard, Golden Oak, FL 32836 resulted in days away from work. Employee was veranda Cook.

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

Where did this happen?

Establishment
Four Seasons Resort Orlando
Parent company
Four Seasons Resort Orlando
Street
10100 Dream Tree Boulevard
City
Golden Oak
State
FL
ZIP
32836
On-site location
Junior Banquet Kitchen

What was the outcome?

Outcome
Days away from work (code 2)
Type
Injury (code 1)
Days away from work
61
Days restricted or transferred
14

Before the incident

Cutting vegtables

What happened

Employee was cutting vegetables and severed the tip of their thumb.

Injury or illness

[Type: Laceration] [Part: Thumb (left side)]

Object or substance involved

Knife

Summary line

[Type: Laceration] [Part: Thumb (left side)] [Source: Knife]

Employee and industry

Job description
Veranda Cook
SOC code
35-2014 — Cooks, Restaurant
NAICS code
721110
NAICS vintage
2022
Avg employees
790
Total hours worked
1264608
Establishment ID
1454929
Employer case #
2025-121

When (timing detail)

Date of incident
Filing year
2025
Submitted
03FEB26:15:57:00

More injuries at Four Seasons Resort Orlando

View Four Seasons Resort Orlando's full OSHA safety record →

More injuries in this industry (NAICS 721110)

More injuries in FL

BROOKSVILLE, FL—

WM 4818

WEST PALM BEACH, FL—

WM 4446

PENSACOLA, FL—

WM 3785

MELBOURNE, FL—

WM 3538

POMPANO BEACH, FL—

WM 2962

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.