Skip to main content
TruckCodex
Hubs

Crash Record IA2501466093

FMCSA crash record in CEDAR FALLS on Jan 7, 2025.

Tow-Away Federal Recordable

What happened

On January 7, 2025, FMCSA recorded a tow-away crash with no reported injuries in CEDAR FALLS, Iowa. The vehicle was operated by FEDERAL EXPRESS CORPORATION (USDOT 86876). Recorded conditions: 1 / 1 / 1 pavement. Reported by FEDEX EXPRESS FEDEX, FMCSA reference IA2501466093.

Carrier pattern note

This is the carrier's 1292 crashes in the past 24 months — above the typical pattern (median 0) for fleets of 500+ power units.

Fatalities
0
Injuries
0
Vehicles
2
Carrier
USDOT 86876
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
1,292
24 fatal · 458 injury
Crashes per 100 power units (24 mo)
1.7
2,310 crashes · 138,481 units
Days since prior carrier crash
1
Last on Jan 6, 2025
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,888 carriers

Geographic context

How this crash sits in its setting.

Within CEDAR FALLS, Iowa, 17 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 #:
IA2501466093
Date:
Jan 7, 2025
Time:
1545
State:
Iowa
City:
CEDAR FALLS
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 5 12 WDAPF4CD4KN011725 KBB417 (IA) FEDEX EXPRESS FEDEX 2 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
cmvxr8j2z004do30eqywanhhe Oct 27, 2026 NJ Tow-Away 0 0
cmvt6yx8x0003o3tvp2e3v1s2 Oct 25, 2026 WA Tow-Away 0 0
cmvuo5tbh0029o3dx845whh0i Oct 24, 2026 MI Injury 0 1
cmvnd7c6d003ho3b54ocfy0a4 Oct 20, 2026 TN Injury 0 1
cmvj4mhg4001po3kfe474fc6s Oct 16, 2026 MN Injury 0 1
cmvj4mhfy001ho3kf7ex4vrpb Oct 16, 2026 MN Injury 0 1
cmvj4mhds000lo3kfitjxiprw Oct 16, 2026 MN Injury 0 2
cmvettq6p00ovogss9j97hnzq Oct 8, 2026 PA Tow-Away 0 0
cmvettq8200rlogssdvc095vn Oct 8, 2026 VA Tow-Away 0 0
cmvettr4e011pogssgektx93h Oct 6, 2026 NE Tow-Away 0 0

Carrier booking & risk tools

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