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

JERSEY CITY, NJ —

OSHA Injury Report: Port Liberty Bayonne

Injury · Other recordable case

At a glance

On , an injury at Port Liberty Bayonne in 302 PORT JERSEY BOULEVARD, JERSEY CITY, NJ 7305 resulted in other recordable case. Employee was hustler driver in stevedoring services.

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

Where did this happen?

Establishment
Port Liberty Bayonne
Parent company
Port Liberty Bayonne
Street
302 PORT JERSEY BOULEVARD
City
JERSEY CITY
State
NJ
ZIP
7305
On-site location
V 900

What was the outcome?

Outcome
Other recordable case (code 4)
Type
Injury (code 1)

Before the incident

Stepping on the brake of a hustler

What happened

Employee stated she hit a pot hole and injured both of her knees

Injury or illness

Contusion Bruise of knee both side

Object or substance involved

Vehicles- Off road and industrial vehicles

Summary line

Contusion bruise of knee Both sides-Directly harmed by: Vehicles-Off-road and industrial vehicles-Powered

Employee and industry

Job description
hustler driver
SOC code
53-3032 — Heavy and Tractor-Trailer Truck Drivers
NAICS code
488320 — Stevedoring services
NAICS vintage
2012
Avg employees
360
Total hours worked
2379541
EIN
471709554
Establishment ID
73073
Employer case #
FY25-0007

When (timing detail)

Date of incident
Shift started
7:00
Time of incident
9:30
Filing year
2025
Submitted
27FEB26:19:07:00

More injuries at Port Liberty Bayonne

View Port Liberty Bayonne's full OSHA safety record →

More injuries in this industry (NAICS 488320)

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.