Crash Record NJ0023186014

FMCSA crash record in NORTH BERGEN TWP on Oct 7, 2023.

Injury Federal Recordable

What happened

On October 7, 2023, FMCSA recorded an injury crash with 2 people hurt in NORTH BERGEN TWP, New Jersey. The vehicle was operated by HO-RO TRUCKING CO INC (USDOT 24199). Recorded conditions: 1 / 2 pavement. Reported by HO-RO TRUCKING CO INC, FMCSA reference NJ0023186014.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

HO-RO TRUCKING CO INC

USDOT 24199

Vehicle Type

Truck

Severity

Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

1 fatal · 8 injury

Crashes per 100 power units (24 mo)

0.0

0 crashes · 86 units

Days since prior carrier crash

Last on Sep 6, 2023

Vs fleet-size peers

above the median

Cohort median 0.0 · 27,059 carriers

Geographic context

How this crash sits in its setting.

Within NORTH BERGEN TWP, New Jersey, 12 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

Contributing factors

What the responding officer recorded.

Light: 1
Weather: —
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 #:: NJ0023186014
Date:: Oct 7, 2023
Time:: 1513
State:: New Jersey
City:: NORTH BERGEN TWP
Fatalities:: 0
Injuries:: 2
Tow-Away:: Yes
HazMat:: No
Vehicles:: 4
Carrier (USDOT):: HO-RO TRUCKING CO INC (24199)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	9	3	1XP4D49XXCD132708	AH26475 (PA)	HO-RO TRUCKING 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	Fatalities	Injuries
cr_4638053	Sep 6, 2023	PA	Tow-Away	0	0
cr_4660893	Mar 15, 2023	NJ	Injury	0	1
cr_4529708	Mar 8, 2023	NY	Injury	0	1
cr_4519992	Jan 21, 2023	PA	Injury	0	1
cr_4433815	Oct 7, 2022	PA	Injury	0	1
cr_4433747	Sep 30, 2022	PA	Injury	0	1
cr_4412262	Aug 19, 2022	NY	Fatal	2	0
cr_4367556	Jun 4, 2022	NY	Tow-Away	0	0
cr_4285556	Dec 29, 2021	PA	Injury	0	8
cr_4260354	Nov 13, 2021	PA	Tow-Away	0	0

Carrier booking & risk tools

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

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

Related records

Carrier

HO-RO TRUCKING CO INC

USDOT 24199 · 106 crashes · 0 inspections

Safety

Carrier inspections

Roadside inspection history for this USDOT.

Vehicle

VIN: 1XP4D49XXCD132708

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

State

Crashes in New Jersey

Statewide crash records.

Agency

HO-RO TRUCKING CO INC

Crashes reported by this law-enforcement agency.

City

Crashes in NORTH BERGEN TWP, 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.