Crash Record CA8552302449

FMCSA crash record in MONTCLAIR on Jul 28, 2023.

Tow-Away Federal Recordable

What happened

On July 28, 2023, FMCSA recorded a tow-away crash with no reported injuries in MONTCLAIR, California. The vehicle was operated by A F F TRANS LLC (USDOT 1730271). Recorded conditions: 3 / 1 pavement. Reported by A F F TRANS LLC, FMCSA reference CA8552302449.

Carrier pattern note

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

Geographic note

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

Fatalities

Injuries

Vehicles

Carrier

A F F TRANS LLC

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 · 7 injury

Crashes per 100 power units (24 mo)

4.0

13 crashes · 324 units

Days since prior carrier crash

Last on Jul 22, 2023

Vs fleet-size peers

above the median

Cohort median 0.0 · 26,632 carriers

Geographic context

How this crash sits in its setting.

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

Agencies most active in this area:

CITY OF MONTCLAIR · 2 reports
CHAFFEY JOINT UNION HIGH SCHOOL DISTRICT · 1 reports
BLACK HAWK TRUCKING INC · 1 reports

Contributing factors

What the responding officer recorded.

Light: 3
Weather: —
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 #:: CA8552302449
Date:: Jul 28, 2023
Time:: 2303
State:: California
City:: MONTCLAIR
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 3
Carrier (USDOT):: A F F TRANS LLC (1730271)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	9	3	4V4NC9EH4RN635338	3416485 (PA)	A F F TRANS LLC	3	No

Crash event

Event sequence description.

2:21:COLLISION INVOLVING UNKNOWN MOVABLE OBJECT;3:18:COLLISION INVOLVING FIXED OBJECT;1:6:NONCOLLISION:EXPLOSION OR FIRE

Other crashes by this carrier

10 additional crash record(s) on file.

Record	Date	State	Severity	Injuries
cr_5032261	Sep 23, 2025	TN	Tow-Away	0
cr_4998299	Jun 13, 2025	KY	Tow-Away	0
cr_4931898	Apr 24, 2025	OK	Injury	1
cr_4924962	Apr 2, 2025	AR	Tow-Away	0
cr_4924588	Mar 19, 2025	KS	Tow-Away	0
cr_4888484	Feb 6, 2025	TN	Tow-Away	0
cr_4880409	Jan 14, 2025	IL	Tow-Away	0
cr_4882532	Jan 10, 2025	MO	Injury	2
cr_4872281	Jan 6, 2025	FL	Injury	1
cr_4879939	Jan 3, 2025	IN	Tow-Away	0

Related records

Vehicle

2024 VOLVO TRUCK VNL

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

Carrier

A F F TRANS LLC

USDOT 1730271 · 77 crashes · 637 inspections

Vehicle

VIN: 4V4NC9EH4RN635338

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

State

Crashes in California

Statewide crash records.

Agency

A F F TRANS LLC

Crashes reported by this law-enforcement agency.

City

Crashes in MONTCLAIR, 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.