Crash Record CA8552302136

FMCSA crash record in MONTCLAIR on Jun 30, 2023.

Tow-Away Federal Recordable

What happened

On June 30, 2023, FMCSA recorded a tow-away crash with no reported injuries in MONTCLAIR, California. The vehicle was operated by BRISK TRANSPORTATION & COLD STORAGE INC (USDOT 792438). Recorded conditions: 1 / 1 / 1 pavement. Reported by BRISK TRANSPORTATION & COLD STORAGE INC, FMCSA reference CA8552302136.

Geographic note

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

Fatalities

Injuries

Vehicles

Carrier

BRISK TRANSPORTATION & COLD STORAGE INC

USDOT 792438

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 · 2 tow-away

Crashes per 100 power units (24 mo)

6.3

1 crashes · 16 units

Days since prior carrier crash

630

Last on Oct 8, 2021

Vs fleet-size peers

above the median

Cohort median 0.0 · 315,143 carriers

Geographic context

How this crash sits in its setting.

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

Agencies most active in this area:

CITY OF MONTCLAIR · 2 reports
ELEVATED LOGISTICS INC · 1 reports
BLACK HAWK TRUCKING INC · 1 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 #:: CA8552302136
Date:: Jun 30, 2023
Time:: 1030
State:: California
City:: MONTCLAIR
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 3
Carrier (USDOT):: BRISK TRANSPORTATION & COLD STORAGE INC (792438)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	5	3	JALC4W163G7004325	13107Z1 (CA)	BRISK TRANSPORTATION & COLD STORAGE INC	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_5122501	Feb 20, 2026	CA	Tow-Away	0	0
cr_4252610	Oct 8, 2021	CA	Tow-Away	0	0
cr_3538910	Dec 22, 2017	CA	Injury	0	1
cr_3169185	Dec 23, 2015	CA	Injury	0	3
cr_2652681	Dec 13, 2012	CA	Tow-Away	0	0
cr_2640787	Nov 7, 2012	CA	Fatal	1	2
cr_2489434	Oct 3, 2011	CA	Tow-Away	0	0
cr_2443441	Jul 6, 2011	CA	Tow-Away	0	0
cr_2265570	May 14, 2010	CA	Tow-Away	0	0
cr_2023455	Aug 29, 2008	CA	Tow-Away	0	0

Carrier booking & risk tools

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

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

Related records

Vehicle

2016 ISUZU NPR-HD

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

Carrier

BRISK TRANSPORTATION & COLD STORAGE INC

USDOT 792438 · 20 crashes · 114 inspections

Safety

Carrier inspections

Roadside inspection history for this USDOT.

Vehicle

VIN: JALC4W163G7004325

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

State

Crashes in California

Statewide crash records.

Agency

BRISK TRANSPORTATION & COLD STORAGE INC

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.