2,042,423Injury reports 130,778Establishments Most recent incident 2025-12-31
Safety Incidents OSHA Severe Injury Reports · 2015–2025

Perth Amboy, NJ —

OSHA Injury Report: Raritan Bay Medical Center

Injury · Days away from work

At a glance

On , an injury at Raritan Bay Medical Center in 530 New Brunswick Avenue, Perth Amboy, NJ 8861 resulted in days away from work. Employee was transportation Aide in general Medical and Surgical Hospitals.

Where did this happen?

Establishment
Raritan Bay Medical Center
Parent company
HMH Hospitals Corporation
Street
530 New Brunswick Avenue
City
Perth Amboy
State
NJ
ZIP
8861
On-site location
Transport Break Room

What was the outcome?

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

Before the incident

Sitting in the break room waiting to be call to transport a patient

What happened

Team Member was sitting on a rolling chair she stretched back and the chair flipped backwards Team Member hit her head on the wall and falling hitting her back on the floor

Injury or illness

Contusion of head Sprain cervical spine Sprain lumbar spine

Object or substance involved

floor

Summary line

Contusion of head Sprain cervical spine Sprain lumbar spine floor

Employee and industry

Job description
Transportation Aide
SOC code
31-1131 — Nursing Assistants
NAICS code
622110 — General Medical and Surgical Hospitals
NAICS vintage
2022
Avg employees
1360
Total hours worked
1980292
EIN
221487576
Establishment ID
1515070
Employer case #
25-62900

When (timing detail)

Date of incident
Shift started
23:00
Time of incident
6:00
Filing year
2025
Submitted
27FEB26:17:07:00

More injuries at Raritan Bay Medical Center

View Raritan Bay Medical Center's full OSHA safety record →

More injuries in this industry (NAICS 622110)

More injuries in NJ

SECAUCUS, NJ—

WM 3520

RIVERDALE, NJ—

WM 3443

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.