Crash Record MT2350196368

FMCSA crash record in Montana on Oct 17, 2023.

Tow-Away Federal Recordable

What happened

On October 17, 2023, FMCSA recorded a tow-away crash with no reported injuries in Montana. The vehicle was operated by BFS ASSET HOLDINGS LLC (USDOT 325981). Recorded conditions: 1 / 1 / 1 pavement. Reported by BFS ASSET HOLDINGS LLC, FMCSA reference MT2350196368.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

BFS ASSET HOLDINGS LLC

USDOT 325981

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

2 fatal · 31 injury

Crashes per 100 power units (24 mo)

1.8

81 crashes · 4,524 units

Days since prior carrier crash

Last on Oct 11, 2023

Vs fleet-size peers

above the median

Cohort median 0.0 · 3,888 carriers

Geographic context

How this crash sits in its setting.

Within Montana, 1,102 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 #:: MT2350196368
Date:: Oct 17, 2023
Time:: 0750
State:: Montana
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 1
Carrier (USDOT):: BFS ASSET HOLDINGS LLC (325981)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	7	5	1XPTD49X3ED215265	263432B (MT)	BFS ASSET HOLDINGS LLC	3	No

Crash event

Event sequence description.

1:19:COLLISION WITH WORK ZONE MAINTENANCE EQUIPMENT

Other crashes by this carrier

10 additional crash record(s) on file.

Record	Date	State	Severity	Injuries
cmvettpui0037ogssoowg3mg0	Oct 13, 2026	MN	Tow-Away	0
cmodru13j0011nvfd9982sdo5	Apr 21, 2026	TN	Tow-Away	0
cmoax1cmi006nnvsyeh13op3c	Apr 15, 2026	WA	Tow-Away	0
cr_5123572	Mar 10, 2026	TX	Injury	1
cr_5115791	Feb 24, 2026	TX	Injury	1
cr_5111400	Feb 16, 2026	GA	Tow-Away	0
cr_5103737	Feb 6, 2026	GA	Injury	1
cr_5102089	Feb 4, 2026	GA	Injury	2
cr_5126173	Jan 28, 2026	WI	Tow-Away	0
cr_5091645	Jan 19, 2026	MT	Tow-Away	0

Carrier booking & risk tools

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

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

Related records

Carrier

BFS ASSET HOLDINGS LLC

USDOT 325981 · 461 crashes · 3,980 inspections

Safety

Carrier inspections

Roadside inspection history for this USDOT.

Vehicle

VIN: 1XPTD49X3ED215265

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

State

Crashes in Montana

Statewide crash records.

Agency

BFS ASSET HOLDINGS LLC

Crashes reported by this law-enforcement agency.

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.