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

Houston, TX —

OSHA Injury Report: Four Seasons Hotel, Houston

Injury · Days away from work

At a glance

On , an injury at Four Seasons Hotel, Houston in 1300 Lamar Street, Houston, TX 77010 resulted in days away from work. Employee was cook in hotels (except casino hotels).

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

Where did this happen?

Establishment
Four Seasons Hotel, Houston
Parent company
Four Seasosn Hotel- Houston
Street
1300 Lamar Street
City
Houston
State
TX
ZIP
77010
On-site location
City Street, corner of Lamar & Dallas

What was the outcome?

Outcome
Days away from work (code 2)
Type
Injury (code 1)
Days away from work
9

Before the incident

Arriving to work

What happened

Walking to work stepped on man hole cover and employee fell in

Injury or illness

Contusion scrapes

Object or substance involved

City man-hole in front of hotel

Summary line

Employee fell into man-hole injuring right knee

Employee and industry

Job description
Cook
SOC code
35-2014 — Cooks, Restaurant
NAICS code
721110 — Hotels (except casino hotels)
NAICS vintage
2012
Avg employees
358
Total hours worked
617686
EIN
760000808
Establishment ID
445429
Employer case #
4

When (timing detail)

Date of incident
Time of incident
15:15
Filing year
2025
Submitted
02FEB26:21:41:00

More injuries at Four Seasons Hotel, Houston

View Four Seasons Hotel, Houston's full OSHA safety record →

More injuries in this industry (NAICS 721110)

More injuries in TX

AMARILLO, TX—

WM 4464

VICTORIA, TX—

WM 4194

FORT WORTH, TX—

WM 3005

ARLINGTON, TX—

WM 2977

SAN ANTONIO, TX—

WM 1803

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.