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 Orthopedic Hospital

Injury · Days away from work

At a glance

On , an injury at NYU Langone Orthopedic Hospital in 301 E 17th Street, New York, NY 10003 resulted in days away from work. Employee was patient Care Technician in general medical and surgical hospitals.

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

Where did this happen?

Establishment
NYU Langone Orthopedic Hospital
Parent company
NYU Langone Hospitals
Street
301 E 17th Street
City
New York
State
NY
ZIP
10003
On-site location
LOH 10th floor room 1013

What was the outcome?

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

Before the incident

Transferring pulling patient over from stretcher to bed

What happened

Pulling the patient felt pain to my L shoulder

Injury or illness

strain sprain L shoulder

Object or substance involved

patient

Summary line

Pulling the patient felt pain to my L shoulder

Employee and industry

Job description
Patient Care Technician
SOC code
31-1131 — Nursing Assistants
NAICS code
622110 — General medical and surgical hospitals
NAICS vintage
2012
Avg employees
1674
Total hours worked
2069580
EIN
133971298
Establishment ID
659684
Employer case #
102468094

When (timing detail)

Date of incident
Shift started
15:00
Time of incident
19:00
Filing year
2025
Submitted
02MAR26:04:51:00

More injuries at NYU Langone Orthopedic Hospital

View NYU Langone Orthopedic 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.