BURLINGAME, CA —
OSHA Injury Report: 13869 ES SAN FRANCISCO-AIRPORT-WATERFRONT CA
Injury · Job transfer or restriction
At a glance
On , an injury at 13869 ES SAN FRANCISCO-AIRPORT-WATERFRONT CA in BURLINGAME, CA 94010 resulted in job transfer or restriction. Employee was attendant Room in hotels.
Where did this happen?
- Establishment
- 13869 ES SAN FRANCISCO-AIRPORT-WATERFRONT CA
- Parent company
- Hilton Worldwide Holdings Inc. ES SAN FRANCISCO-AIRPORT-WATERFRONT CA
- Street
- 150 ANZA BLVD
- City
- BURLINGAME
- State
- CA
- ZIP
- 94010
- On-site location
- GUEST ROOM SHOWER
What was the outcome?
- Outcome
- Job transfer or restriction (code 3)
- Type
- Injury (code 1)
- Days restricted or transferred
- 24
Before the incident
CLEANING THE SHOWER
What happened
EE was cleaning the shower with a sponge which was very soapy and sponge slipped out of her grasp and when she went to grab it EE hurt her Rt elbow and the right side of her neck Incident happened around [REDACTED] however EE did not report incide
Injury or illness
Strained Right Upper arm Repetitive motion Overexertion while reaching for sp
Object or substance involved
Overexertion while reaching for sponge
Summary line
EE was cleaning the shower with a sponge which was very soapy and sponge slipped out of her grasp and when she went to grab it EE hurt her Rt elbow and the right side of her neck Incident happened around [REDACTED] however EE did not report incide
Employee and industry
- Job description
- Attendant Room
- SOC code
- 37-2012 — Maids and Housekeeping Cleaners
- NAICS code
- 721110 — Hotels
- NAICS vintage
- 2022
- Avg employees
- 113
- Total hours worked
- 162994
- EIN
- 842077863
- Establishment ID
- 1337429
- Employer case #
- 45517
When (timing detail)
- Date of incident
- Shift started
- 8:30
- Time of incident
- 10:30
- Filing year
- 2024
- Submitted
- 28FEB2025:00:31:00
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.