Skip to main content
TruckCodex
Hubs

Crash Record CO2025002122

FMCSA crash record in BRIGHTON on Dec 5, 2025.

Tow-Away Federal Recordable

What happened

On December 5, 2025, FMCSA recorded a tow-away crash with no reported injuries in BRIGHTON, Colorado. The vehicle was operated by ARC THRIFT STORES (USDOT 1126937). Recorded conditions: 1 / 1 / 1 pavement. FMCSA reference CO2025002122.

Geographic note

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

Fatalities
0
Injuries
0
Vehicles
4
Carrier
USDOT 1126937
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
2
0 injury · 2 tow-away
Crashes per 100 power units (24 mo)
3.1
1 crashes · 32 units
Days since prior carrier crash
710
Last on Dec 26, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 315,858 carriers

Geographic context

How this crash sits in its setting.

Within BRIGHTON, Colorado, 26 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 #:
CO2025002122
Date:
Dec 5, 2025
Time:
0909
State:
Colorado
City:
BRIGHTON
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
4
Carrier (USDOT):
ARC THRIFT STORES (1126937)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
2 5 3 5PVNJ8JV8H4S63725 UQN347 (CO) ARC THRIFT STORES 3 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_4783219 Dec 26, 2023 CO Tow-Away 0 0
cr_3769868 Jan 24, 2019 CO Tow-Away 0 0
cr_3082368 Jun 15, 2015 CO Tow-Away 0 0
cr_3082363 Jun 12, 2015 CO Tow-Away 0 0
cr_2873874 May 14, 2014 CO Tow-Away 0 0
cr_2821928 Dec 10, 2013 CO Tow-Away 0 0
cr_2579488 May 18, 2012 CO Tow-Away 0 0
cr_2054913 Nov 3, 2008 CO Tow-Away 0 0
cr_1964330 Apr 10, 2008 CO Tow-Away 0 0
cr_1778319 Feb 13, 2007 CO Tow-Away 0 0

Carrier booking & risk tools

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

Related records

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.