Skip to main content
TruckCodex
Hubs

Crash Record VA0221505166

FMCSA crash record in RICHMOND CITY on May 25, 2022.

Tow-Away Federal Recordable

What happened

On May 25, 2022, FMCSA recorded a tow-away crash with no reported injuries in RICHMOND CITY, Virginia. The vehicle was operated by VISTAR TRANSPORTATION LLC (USDOT 333153). Recorded conditions: 1 / 1 / 1 pavement. Reported by VISTAR, FMCSA reference VA0221505166.

Carrier pattern note

This is the carrier's 25 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: 86 crashes occurred in the same city in the past 24 months.

Fatalities
0
Injuries
0
Vehicles
2
Carrier
VISTAR TRANSPORTATION LLC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
25
6 injury · 23 tow-away
Crashes per 100 power units (24 mo)
2.1
21 crashes · 995 units
Days since prior carrier crash
8
Last on May 17, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,855 carriers

Geographic context

How this crash sits in its setting.

Within RICHMOND CITY, Virginia, 86 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 #:
VA0221505166
Date:
May 25, 2022
Time:
0808
State:
Virginia
City:
RICHMOND CITY
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
VISTAR TRANSPORTATION LLC (333153)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 8 98 3AKJHTDV8NDNB8025 PAU8945 (VA) VISTAR 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
cmop8v806002zmzuiksz6ksfh Apr 27, 2026 MI Tow-Away 0 0
cr_5123222 Mar 16, 2026 AL Injury 0 3
cr_5126825 Mar 16, 2026 MO Tow-Away 0 0
cr_5111186 Jan 27, 2026 MI Tow-Away 0 0
cr_5087797 Jan 12, 2026 IA Tow-Away 0 0
cr_5123466 Nov 5, 2025 KS Tow-Away 0 0
cr_5026018 Sep 12, 2025 FL Tow-Away 0 0
cr_5019347 Jul 29, 2025 CA Tow-Away 0 0
cr_5013156 Jul 15, 2025 VA Tow-Away 0 0
cr_4988817 Jun 25, 2025 AZ Tow-Away 0 0

Related records

Vehicle
2022 FREIGHTLINER Cascadia
NHTSA recalls and complaints for this make/model/year.
Recall
26V583000
SERVICE BRAKES, AIR:ANTILOCK
Recall
23V299000
ELECTRONIC STABILITY CONTROL (ESC)
Recall
23V238000
STEERING:LINKAGES:TIE ROD ASSEMBLY
Carrier
VISTAR TRANSPORTATION LLC
USDOT 333153 · 171 crashes · 889 inspections
Vehicle
VIN: 3AKJHTDV8NDNB8025
Decode this VIN for make, model, year, and recall data.
State
Crashes in Virginia
Statewide crash records.
Agency
VISTAR
Crashes reported by this law-enforcement agency.
City
Crashes in RICHMOND CITY, VA
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.