Skip to main content
TruckCodex
Hubs

Crash Record NJ0004786898

FMCSA crash record in Ridgefield Boro on Dec 20, 2023.

Tow-Away Federal Recordable

What happened

On December 20, 2023, FMCSA recorded a tow-away crash with no reported injuries in Ridgefield Boro, New Jersey. The vehicle was operated by CRUISE AMERICA (USDOT 689232). Recorded conditions: 1 / 1 / 1 pavement. FMCSA reference NJ0004786898.

Geographic note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
CRUISE AMERICA
USDOT 689232
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
1
0 injury · 1 tow-away
Days since prior carrier crash
1,015
Last on Mar 10, 2021

Geographic context

How this crash sits in its setting.

Within Ridgefield Boro, New Jersey, 27 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
1
Road surface
1

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 #:
NJ0004786898
Date:
Dec 20, 2023
Time:
1517
State:
New Jersey
City:
Ridgefield Boro
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
CRUISE AMERICA (689232)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
2 5 98 1FDWE3FS9KDC22386 EBPK52 (FL) CRUISE AMERICA 2 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_5036459 Sep 25, 2025 TX Injury 0 1
cr_4947383 Apr 9, 2025 AZ Fatal 1 2
cr_4852218 Nov 18, 2024 TX Injury 0 1
cr_4786866 Jul 3, 2024 MI Tow-Away 0 0
cr_4783548 Jun 28, 2024 GA Injury 0 1
cr_4751891 May 13, 2024 MN Injury 0 5
cr_4142164 Mar 10, 2021 NC Tow-Away 0 0
cr_4032518 Sep 11, 2020 TX Tow-Away 0 0
cr_3540127 Feb 4, 2018 MN Injury 0 2
cr_3258752 Aug 6, 2016 AZ Tow-Away 0 0

Carrier booking & risk tools

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

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

Related records

Vehicle
2019 FORD E-350
NHTSA recalls and complaints for this make/model/year.
Carrier
CRUISE AMERICA
USDOT 689232 · 16 crashes · 0 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 1FDWE3FS9KDC22386
Decode this VIN for make, model, year, and recall data.
State
Crashes in New Jersey
Statewide crash records.
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.