Crash Record NJ0005391358

FMCSA crash record in RIDGEFIELD BORO on Jan 25, 2023.

Tow-Away Federal Recordable

What happened

On January 25, 2023, FMCSA recorded a tow-away crash with no reported injuries in RIDGEFIELD BORO, New Jersey. The vehicle was operated by BAYONNE TRUCKING INC (USDOT 3003668). Recorded conditions: 1 / 2 / 2 pavement. Reported by BAYONNE TRUCKING INC, FMCSA reference NJ0005391358.

Carrier pattern note

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

Geographic note

This crash is part of an active corridor: 31 crashes occurred in the same city in the past 24 months.

Fatalities

Injuries

Vehicles

Carrier

BAYONNE TRUCKING INC

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

0 injury · 4 tow-away

Crashes per 100 power units (24 mo)

0.0

0 crashes · 13 units

Days since prior carrier crash

374

Last on Jan 16, 2022

Vs fleet-size peers

above the median

Cohort median 0.0 · 312,424 carriers

Geographic context

How this crash sits in its setting.

Within RIDGEFIELD BORO, New Jersey, 31 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

UNKNOWN · 7 reports
NJ TRANSIT CORPORATION · 2 reports
FARMLIND PRODUCE LLC · 1 reports

Contributing factors

What the responding officer recorded.

Light: 1
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 #:: NJ0005391358
Date:: Jan 25, 2023
Time:: 1632
State:: New Jersey
City:: RIDGEFIELD BORO
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: BAYONNE TRUCKING INC (3003668)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	9	3	1XPHDU9X27N692384	AU378H (NJ)	BAYONNE TRUCKING INC	3	No

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT

Other crashes by this carrier

9 additional crash record(s) on file.

Record	Date	State	Severity	Injuries
cr_4291654	Jan 16, 2022	PA	Tow-Away	0
cr_4269763	Nov 22, 2021	MD	Tow-Away	0
cr_4150167	May 9, 2021	NY	Tow-Away	0
cr_3980053	May 29, 2020	NY	Tow-Away	0
cr_3793745	May 29, 2019	IN	Tow-Away	0
cr_3791583	May 1, 2019	MI	Injury	1
cr_3750410	Feb 8, 2019	PA	Tow-Away	0
cr_3690541	Nov 15, 2018	NY	Tow-Away	0
cr_3573257	Feb 19, 2018	MD	Injury	1

Related records

Vehicle

2007 PETERBILT 386

NHTSA recalls and complaints for this make/model/year.

Recall

13V593000

EQUIPMENT:OTHER:LABELS

Recall

11V127000

FUEL SYSTEM, OTHER:STORAGE:TANK ASSEMBLY

Recall

10V634000

POWER TRAIN:AXLE ASSEMBLY

Carrier

BAYONNE TRUCKING INC

USDOT 3003668 · 10 crashes · 0 inspections

Vehicle

VIN: 1XPHDU9X27N692384

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

State

Crashes in New Jersey

Statewide crash records.

Agency

BAYONNE TRUCKING INC

Crashes reported by this law-enforcement agency.

City

Crashes in RIDGEFIELD BORO, NJ

All crashes on file for this city.

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.