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

Carteret, NJ —

OSHA Injury Report: LTL (10) - Metro - Carteret (001)

Injury · Job transfer or restriction

At a glance

On , an injury at LTL (10) - Metro - Carteret (001) in 5000 Industrial Drive, Carteret, NJ 7008 resulted in job transfer or restriction. Employee was p and D Driver in general Freight.

Where did this happen?

Establishment
LTL (10) - Metro - Carteret (001)
Parent company
A. Duie Pyle
Street
5000 Industrial Drive
City
Carteret
State
NJ
ZIP
7008
On-site location
Trailer - ADP

What was the outcome?

Outcome
Job transfer or restriction (code 3)
Type
Injury (code 1)
Days restricted or transferred
7

Before the incident

Climbing up trailer to close the doors.

What happened

Driver climbed up to close trailer door and stopped on the edge of the trailer and felt left heel buckle.

Injury or illness

Climbing up to close the trailer doors and stopped on the edge of the trailer and felt pain in the left heel.

Object or substance involved

Edge of trailer

Summary line

Driver climbed up to close trailer door and stopped on the edge of the trailer and felt left heel buckle.

Employee and industry

Job description
P and D Driver
SOC code
53-3032 — Heavy and Tractor-Trailer Truck Drivers
NAICS code
484110 — General Freight
NAICS vintage
2022
Avg employees
163
Total hours worked
357135
EIN
231417983
Establishment ID
1533902
Employer case #
WC2025112

When (timing detail)

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

More injuries at LTL (10) - Metro - Carteret (001)

View LTL (10) - Metro - Carteret (001)'s full OSHA safety record →

More injuries in this industry (NAICS 484110)

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.