Crash Record NJ0022113081

FMCSA crash record in RAHWAY CITY on Jun 9, 2022.

Tow-Away Federal Recordable

What happened

On June 9, 2022, FMCSA recorded a tow-away crash with no reported injuries in RAHWAY CITY, New Jersey. The vehicle was operated by SAMUEL CORALUZZO COMPANY INC (USDOT 156123). Recorded conditions: 3 / 2 / 2 pavement. Reported by SAMUEL CORALUZZO CO INC, FMCSA reference NJ0022113081.

Carrier pattern note

This is the carrier's 52 crashes in the past 24 months — above the typical pattern (median 0) for fleets of 51–500 power units.

Fatalities

Injuries

Vehicles

Carrier

SAMUEL CORALUZZO COMPANY INC

USDOT 156123

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

1 fatal · 19 injury

Crashes per 100 power units (24 mo)

4.5

21 crashes · 464 units

Days since prior carrier crash

Last on May 31, 2022

Vs fleet-size peers

above the median

Cohort median 0.0 · 27,296 carriers

Geographic context

How this crash sits in its setting.

Within RAHWAY CITY, New Jersey, 11 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

DBT XPRESS LLC · 1 reports
DELIA EXPRESS TRUCKING LLC · 1 reports
CITY OF RAHWAY · 1 reports

Contributing factors

What the responding officer recorded.

Light: 3
Weather: 2
Road surface: 2

Conditions are mixed. The data does not assign causation; this section reports only what was recorded by the responding officer.

Crash details

Key facts from the FMCSA crash record.

Report #:: NJ0022113081
Date:: Jun 9, 2022
Time:: 0446
State:: New Jersey
City:: RAHWAY CITY
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: SAMUEL CORALUZZO COMPANY INC (156123)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	8	5	1M1AN2EY87M001271	NJ43209 (NJ)	SAMUEL CORALUZZO CO INC	3	No

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record	Date	State	Severity	Injuries
cr_5103679	Jan 3, 2026	FL	Injury	1
cr_5105031	Dec 31, 2025	MD	Tow-Away	0
cr_5048265	Oct 24, 2025	VA	Injury	1
cr_5100935	Oct 8, 2025	FL	Tow-Away	0
cr_5077532	Aug 17, 2025	VA	Tow-Away	0
cr_5025343	Aug 1, 2025	FL	Tow-Away	0
cr_5021619	Jul 29, 2025	PA	Injury	1
cr_4999828	Jun 29, 2025	MD	Tow-Away	0
cr_5013230	Jun 15, 2025	VA	Tow-Away	0
cr_4956072	Jun 5, 2025	VA	Tow-Away	0

Carrier booking & risk tools

Check booking and risk signals for USDOT 156123 — tools open pre-filled.

Book / don't book Insurance check Cancel desk Chameleon check Safety benchmark

Related records

Carrier

SAMUEL CORALUZZO COMPANY INC

USDOT 156123 · 441 crashes · 2,023 inspections

Safety

Carrier inspections

Roadside inspection history for this USDOT.

Vehicle

VIN: 1M1AN2EY87M001271

Decode this VIN for make, model, year, and recall data.

State

Crashes in New Jersey

Statewide crash records.

Agency

SAMUEL CORALUZZO CO INC

Crashes reported by this law-enforcement agency.

City

Crashes in RAHWAY CITY, NJ

All crashes on file for this city.

Station

US 1

Weigh / inspection station matching this crash location.

Index

All Crash Records

Browse FMCSA commercial vehicle crash records.

Database

Roadside Inspections

Inspection history and violation details.

Database

NHTSA Recalls

Active recall campaigns.

Frequently asked questions about FMCSA crash records

What does this crash report tell me about the carrier? ▾

An individual FMCSA crash record tells you that a commercial vehicle operated by this carrier was involved in a reportable crash on the date listed, along with the severity (fatalities / injuries / tow-away) and the responding agency. A single crash record does not tell you whether the carrier was at fault, whether the driver was cited, or how the crash affected the carrier's safety scores. To evaluate the carrier, compare the full multi-year crash history against the carrier's fleet size, miles driven, and cohort peers.

Was this crash the carrier's fault? ▾

FMCSA crash records do not assign fault. Fault attribution requires reviewing the police report, any litigation outcome, and FMCSA's preventability determination if one was requested. If you need a fault determination, request the underlying state police crash report (PAR) — the carrier or its insurer can pull this through standard channels.

How does this crash affect the carrier's safety scores? ▾

Crash records feed FMCSA's Crash Indicator BASIC inside the Safety Measurement System (SMS). Each FMCSA-reportable crash counts for two years from the crash date and is weighted by severity (fatal / injury / tow-only). The Crash Indicator score is normalized against the carrier's power-unit count and exposure, so larger fleets need more crashes to score the same percentile as smaller ones. Non-reportable crashes do not enter the score.

Will this crash show up on the carrier's CSA SMS scores? ▾

If the federal_recordable flag on this record is true, yes — it will appear in the carrier's Crash Indicator BASIC for two years from the crash date. Crashes flagged state-only (state_recordable) are visible on the public crash file but do not enter the federal score.

How do I check the carrier's full crash history? ▾

Click through to the carrier profile (the USDOT link near the top of this page). The carrier's profile lists every crash on file, severity counts, and links into the SMS detail when an MC docket is on record. You can also visit FMCSA's SAFER and SMS portals directly using the carrier's USDOT number.

What if details look wrong — how do I correct an FMCSA crash record? ▾

FMCSA's DataQs system handles corrections to crash records. Either the carrier or an interested third party can file a Request for Data Review (RDR) with supporting documentation (police report, court records, witness statements). Corrections are processed by the originating state agency and propagate to the federal file within roughly 60–120 days when accepted.