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

New York, NY —

OSHA Injury Report: NYU Langone Hospital

Injury · Days away from work

At a glance

On , an injury at NYU Langone Hospital in 560 1st Ave, New York, NY 10016 resulted in days away from work. Employee was building Service Attendant in general medical and surgical hospitals.

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

Where did this happen?

Establishment
NYU Langone Hospital
Parent company
NYU Langone Hospitals
Street
560 1st Ave
City
New York
State
NY
ZIP
10016
On-site location
Th 6 OR ? room 13

What was the outcome?

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

Before the incident

Cleaning turnover the OR room

What happened

I was cleaning the OR bed bending down and I tripped and slept and sprained my ankle

Injury or illness

strain sprain L foot

Object or substance involved

floor

Summary line

I was cleaning the OR bed bending down and I tripped and slept and sprained my ankle

Employee and industry

Job description
Building Service Attendant
SOC code
37-2011 — Janitors and Cleaners, Except Maids and Housekeeping Cleaners
NAICS code
622110 — General medical and surgical hospitals
NAICS vintage
2012
Avg employees
14560
Total hours worked
19567881
EIN
133971298
Establishment ID
659642
Employer case #
105898560

When (timing detail)

Date of incident
Shift started
15:00
Time of incident
18:00
Filing year
2025
Submitted
02MAR26:21:13:00

More injuries at NYU Langone Hospital

View NYU Langone Hospital's full OSHA safety record →

More injuries in this industry (NAICS 622110)

More injuries in NY

KINGSTON, NY—

WM 6201

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.