Crash Record WI0000125367

FMCSA crash record in MILWAUKEE on Apr 23, 2025.

Tow-Away Federal Recordable

What happened

On April 23, 2025, FMCSA recorded a tow-away crash with no reported injuries in MILWAUKEE, Wisconsin. The vehicle was operated by FEDERAL EXPRESS CORPORATION (USDOT 86876). Recorded conditions: 1 / 1 / 1 pavement. Reported by FEDEX EXPRESS FEDEX, FMCSA reference WI0000125367.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
FEDERAL EXPRESS CORPORATION
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
1,695
35 fatal · 596 injury
Crashes per 100 power units (24 mo)
1.8
2,509 crashes · 138,481 units
Days since prior carrier crash
1
Last on Apr 22, 2025
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,837 carriers

Geographic context

How this crash sits in its setting.

Within MILWAUKEE, Wisconsin, 302 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 #:
WI0000125367
Date:
Apr 23, 2025
Time:
1550
State:
Wisconsin
City:
MILWAUKEE
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 9 3 1XKYDP9X8PJ256766 PC27670 (IN) FEDEX EXPRESS FEDEX 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
cmtfchmfj0009pmjnybpu3leu Aug 26, 2026 OK Tow-Away 0 0
cmtdwm2p5000ppmb9mlqlgnkh Aug 24, 2026 NJ Tow-Away 0 0
cmtazy7j7001bpmln8osd34ic Aug 20, 2026 OH Injury 0 1
cmt5ony23005fpmdm8265vd2x Aug 17, 2026 NJ Tow-Away 0 0
cmt1jo11q0059pevkcl1t1d6w Aug 14, 2026 MI Injury 0 1
cmsw88ryr000lpev3egctjyzj Aug 10, 2026 MN Injury 0 1
cmsw88s7c0079pev3a4ctniiz Aug 10, 2026 MN Tow-Away 0 0
cmsw88s6h005npev3ymzld9nb Aug 10, 2026 NC Tow-Away 0 0
cmsw88s7b0075pev3m5ye25bk Aug 8, 2026 KY Tow-Away 0 0
cmsw88s8y008dpev3v4g6k4e2 Aug 8, 2026 AZ Injury 0 2

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.