TruckCodex
Hubs

Crash Record WA000EB90346

FMCSA crash record in PUYALLUP on Nov 10, 2021.

Tow-Away Federal Recordable

What happened

On November 10, 2021, FMCSA recorded a tow-away crash with no reported injuries in PUYALLUP, Washington. The vehicle was operated by CARDINAL LOGISTICS MANAGEMENT CORPORATION (USDOT 191496). Recorded conditions: 2 / 2 / 2 pavement. Reported by CARDINAL LOGISTICS MANAGEMENT CORPORATION, FMCSA reference WA000EB90346.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
4
Carrier
CARDINAL LOGISTICS MANAGEMENT CORPORATION
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
196
7 fatal · 68 injury
Crashes per 100 power units (24 mo)
3.9
114 crashes · 2,954 units
Days since prior carrier crash
2
Last on Nov 8, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,837 carriers

Geographic context

How this crash sits in its setting.

Within PUYALLUP, Washington, 34 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
2
Weather
2
Road surface
2

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 #:
WA000EB90346
Date:
Nov 10, 2021
Time:
0303
State:
Washington
City:
PUYALLUP
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
4
Carrier (USDOT):
CARDINAL LOGISTICS MANAGEMENT CORPORATION (191496)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 3AKJHLDVXNSNB9270 3167949 (IN) CARDINAL LOGISTICS MANAGEMENT CORPORATION 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_5127348 Mar 25, 2026 VA Injury 0 1
cr_5122205 Mar 5, 2026 TX Tow-Away 0 0
cr_5121757 Feb 27, 2026 GA Tow-Away 0 0
cr_5113732 Feb 20, 2026 IA Tow-Away 0 0
cr_5112778 Feb 11, 2026 GA Tow-Away 0 0
cr_5109639 Feb 10, 2026 TX Tow-Away 0 0
cr_5102411 Feb 5, 2026 VA Injury 0 1
cr_5102749 Feb 3, 2026 GA Tow-Away 0 0
cr_5097933 Jan 23, 2026 OH Tow-Away 0 0
cr_5097326 Jan 15, 2026 CA Injury 0 1

Related records

Carrier
CARDINAL LOGISTICS MANAGEMENT CORPORATION
USDOT 191496 · 1,966 crashes · 5,128 inspections
Vehicle
VIN: 3AKJHLDVXNSNB9270
Decode this VIN for make, model, year, and recall data.
State
Crashes in Washington
Statewide crash records.
Agency
CARDINAL LOGISTICS MANAGEMENT CORPORATION
Crashes reported by this law-enforcement agency.
City
Crashes in PUYALLUP, WA
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.