TruckCodex
Hubs

Crash Record VA0210075131

FMCSA crash record in RICHMOND CITY on Jan 6, 2021.

Tow-Away Federal Recordable

What happened

On January 6, 2021, FMCSA recorded a tow-away crash with no reported injuries in RICHMOND CITY, Virginia. The vehicle was operated by UNIVERSAL LOGISTICS OF VIRGINIA LLC (USDOT 3330935). Recorded conditions: 1 / 1 / 1 pavement. Reported by ESTES DEDICATED, FMCSA reference VA0210075131.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
UNIVERSAL LOGISTICS OF VIRGINIA LLC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
13
5 injury · 13 tow-away
Crashes per 100 power units (24 mo)
4.6
24 crashes · 522 units
Days since prior carrier crash
30
Last on Dec 7, 2020
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,847 carriers

Geographic context

How this crash sits in its setting.

Within RICHMOND CITY, Virginia, 90 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 #:
VA0210075131
Date:
Jan 6, 2021
Time:
0645
State:
Virginia
City:
RICHMOND CITY
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
UNIVERSAL LOGISTICS OF VIRGINIA LLC (3330935)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 8 12 1FUJGLBG3FLGK8231 32857PZ (VA) ESTES DEDICATED 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_5108143 Feb 17, 2026 VA Tow-Away 0 0
cr_5116226 Feb 13, 2026 WV Tow-Away 0 0
cr_5071994 Nov 20, 2025 TX Injury 0 2
cr_5052692 Oct 27, 2025 VA Tow-Away 0 0
cr_5047184 Oct 15, 2025 NC Tow-Away 0 0
cr_5032805 Sep 13, 2025 TX Tow-Away 0 0
cr_5032922 Sep 3, 2025 VA Tow-Away 0 0
cr_5037780 Aug 23, 2025 MD Tow-Away 0 0
cr_5036088 Aug 15, 2025 VA Tow-Away 0 0
cr_5032407 Aug 12, 2025 MD Injury 0 1

Related records

Vehicle
2015 FREIGHTLINER Cascadia
NHTSA recalls and complaints for this make/model/year.
Recall
20V214000
EXTERIOR LIGHTING
Recall
19V370000
SERVICE BRAKES, AIR:SUPPLY:RESERVOIR/TANK
Recall
19V093000
STEERING:LINKAGES:TIE ROD ASSEMBLY
Carrier
UNIVERSAL LOGISTICS OF VIRGINIA LLC
USDOT 3330935 · 113 crashes · 984 inspections
Vehicle
VIN: 1FUJGLBG3FLGK8231
Decode this VIN for make, model, year, and recall data.
State
Crashes in Virginia
Statewide crash records.
Agency
ESTES DEDICATED
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.