Skip to main content
TruckCodex
Hubs

Crash Record VA0221685182

FMCSA crash record in SUFFOLK on Jan 21, 2022.

Tow-Away Federal Recordable

What happened

On January 21, 2022, FMCSA recorded a tow-away crash with no reported injuries in SUFFOLK, Virginia. The vehicle was operated by METROPOLITAN TRANSPORT LLC (USDOT 2130303). Recorded conditions: 4 / 4 / 6 pavement. Reported by METROPOLITAN TRANSPORT LLC, FMCSA reference VA0221685182.

Carrier pattern note

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

Geographic note

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

Fatalities
0
Injuries
0
Vehicles
1
Carrier
USDOT 2130303
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
5
0 injury · 5 tow-away
Crashes per 100 power units (24 mo)
18.2
2 crashes · 11 units
Days since prior carrier crash
37
Last on Dec 15, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 315,629 carriers

Geographic context

How this crash sits in its setting.

Within SUFFOLK, Virginia, 107 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
4
Weather
4
Road surface
6

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 #:
VA0221685182
Date:
Jan 21, 2022
Time:
0220
State:
Virginia
City:
SUFFOLK
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
1

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 UNK UNK (UK) METROPOLITAN TRANSPORT LLC 2 No

Crash event

Event sequence description.

1:18:COLLISION INVOLVING FIXED OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4877623 Dec 18, 2024 MD Tow-Away 0 0
cr_5024343 Dec 18, 2024 MD Tow-Away 0 0
cr_4379092 May 5, 2022 PA Injury 0 1
cr_4349515 Apr 7, 2022 PA Tow-Away 0 0
cr_4280205 Dec 15, 2021 MD Tow-Away 0 0
cr_4178435 Jun 2, 2021 VA Tow-Away 0 0
cr_3945295 Feb 12, 2020 MD Tow-Away 0 0
cr_3936343 Feb 2, 2020 NJ Tow-Away 0 0
cr_3573334 Feb 15, 2018 MD Tow-Away 0 0
cr_3491667 Oct 31, 2017 PA Tow-Away 0 0

Carrier booking & risk tools

Check booking and risk signals for USDOT 2130303 — 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.