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

Jersey City, NJ —

OSHA Injury Report: Jersey City NJ Action Hauling

Injury · Days away from work

At a glance

On , an injury at Jersey City NJ Action Hauling in 264 Broadway, Jersey City, NJ 7306 resulted in days away from work. Employee was commercial RL DriverMSW in waste Management.

Where did this happen?

Establishment
Jersey City NJ Action Hauling
Parent company
Interstate Waste Services
Street
264 Broadway
City
Jersey City
State
NJ
ZIP
7306
On-site location
Customer Location

What was the outcome?

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

Before the incident

Moving Container

What happened

Driver was guiding a container with his hand while another employee was pushing it from behind. The container was pushed too quickly and struck the driver 's right ankle resulting in a contusion to right heel

Injury or illness

Bruise Contusion Striking Against Stepping On Struck By Right ankle

Object or substance involved

Container

Summary line

Employee received a contusion to right foot that got caught on the edge of a container being pushed

Employee and industry

Job description
Commercial RL DriverMSW
SOC code
53-3032 — Heavy and Tractor-Trailer Truck Drivers
NAICS code
562111 — Waste Management
NAICS vintage
2022
Avg employees
235
Total hours worked
596684
EIN
134000316
Establishment ID
1332991
Employer case #
TK28814

When (timing detail)

Date of incident
Shift started
20:00
Time of incident
7:50
Filing year
2025
Submitted
24FEB26:13:31:00

More injuries at Jersey City NJ Action Hauling

View Jersey City NJ Action Hauling's full OSHA safety record →

More injuries in this industry (NAICS 562111)

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.