Crash Record CA3607001021

FMCSA crash record in ONTARIO on Oct 23, 2024.

Tow-Away Federal Recordable

What happened

On October 23, 2024, FMCSA recorded a tow-away crash with no reported injuries in ONTARIO, California. The vehicle was operated by NFI INTERACTIVE LOGISTICS LLC (USDOT 1486168). Recorded conditions: 1 / 1 / 1 pavement. Reported by NFI INTERACTIVE LOGISTICS LLC, FMCSA reference CA3607001021.

Carrier pattern note

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

Geographic note

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

Fatalities

Injuries

Vehicles

Carrier

NFI INTERACTIVE LOGISTICS LLC

USDOT 1486168

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

276

7 fatal · 102 injury

Crashes per 100 power units (24 mo)

5.6

186 crashes · 3,294 units

Days since prior carrier crash

Last on Oct 13, 2024

Vs fleet-size peers

above the median

Cohort median 0.0 · 3,881 carriers

Geographic context

How this crash sits in its setting.

Within ONTARIO, California, 233 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

UNITED PARCEL SERVICE INC · 5 reports
J B HUNT TRANSPORT INC · 3 reports
INDIVIDUAL · 2 reports

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 #:: CA3607001021
Date:: Oct 23, 2024
Time:: 0738
State:: California
City:: ONTARIO
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: NFI INTERACTIVE LOGISTICS LLC (1486168)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	5	3	1FDWE3FS0CDA64599	59015C2 (CA)	NFI INTERACTIVE LOGISTICS LLC	2	No

Crash event

Event sequence description.

1:13:COLLISION INVOLVING MOTOR VEHICLE IN TRANSPORT

Other crashes by this carrier

10 additional crash record(s) on file.

Record	Date	State	Severity	Fatalities	Injuries
cmvettpuq003jogssvdgcyium	Oct 13, 2026	TN	Tow-Away	0	0
cmuz83jpk002rogz658qso1dl	Oct 1, 2026	OH	Injury	0	1
cmsw88s3d002jpev3b62watgs	Aug 10, 2026	MI	Tow-Away	0	0
cmshdfe6r0005pefyl70ah8y3	Aug 1, 2026	MN	Fatal	1	0
cmqg6ahs20085p48do46euiwy	Jun 9, 2026	NJ	Injury	0	1
cmp0olg4d0009nuqw4xslqf4r	May 7, 2026	WV	Tow-Away	0	0
cr_5126784	Mar 25, 2026	OH	Injury	0	1
cr_5122725	Mar 16, 2026	OH	Tow-Away	0	0
cr_5118670	Mar 10, 2026	OH	Tow-Away	0	0
cr_5112342	Feb 23, 2026	OH	Tow-Away	0	0

Carrier booking & risk tools

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

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

Related records

Vehicle

2012 FORD E-350

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

Recall

16V350000

EQUIPMENT ADAPTIVE/MOBILITY

Recall

15V779000

EQUIPMENT ADAPTIVE/MOBILITY

Recall

15V763000

EQUIPMENT ADAPTIVE/MOBILITY

Carrier

NFI INTERACTIVE LOGISTICS LLC

USDOT 1486168 · 1,500 crashes · 5,171 inspections

Safety

Carrier inspections

Roadside inspection history for this USDOT.

Vehicle

VIN: 1FDWE3FS0CDA64599

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

State

Crashes in California

Statewide crash records.

Agency

NFI INTERACTIVE LOGISTICS LLC

Crashes reported by this law-enforcement agency.

City

Crashes in ONTARIO, CA

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.