Crash Record KS2022E24691

FMCSA crash record in LENEXA on Nov 9, 2022.

Tow-Away Federal Recordable

What happened

On November 9, 2022, FMCSA recorded a tow-away crash with no reported injuries in LENEXA, Kansas. The vehicle was operated by ABF FREIGHT SYSTEM INC (USDOT 82866). Recorded conditions: 1 / 1 / 1 pavement. Reported by ABF FREIGHT SYSTEM INC, FMCSA reference KS2022E24691.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

ABF FREIGHT SYSTEM INC

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

321

7 fatal · 85 injury

Crashes per 100 power units (24 mo)

6.1

279 crashes · 4,604 units

Days since prior carrier crash

Last on Nov 7, 2022

Vs fleet-size peers

above the median

Cohort median 0.0 · 3,838 carriers

Geographic context

How this crash sits in its setting.

Within LENEXA, Kansas, 51 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

UNITED PARCEL SERVICE INC · 3 reports
FEDEX EXPRESS FEDEX · 3 reports
DS BUS LINES INC · 2 reports

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 #:: KS2022E24691
Date:: Nov 9, 2022
Time:: 1240
State:: Kansas
City:: LENEXA
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: ABF FREIGHT SYSTEM INC (82866)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	9	3	1M1AW01X9HM009878	2XZ106 (OK)	ABF FREIGHT SYSTEM INC	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
cmrd638nt0005p8pqwvdto80b	Jul 2, 2026	NC	Tow-Away	0	0
cmqvwant0002rp8iurrw6jlh2	Jun 22, 2026	NV	Tow-Away	0	0
cmoxtyom8002pnu5l4fl2qtq6	May 4, 2026	TN	Fatal	1	0
cmogoa8gd003pnvt8zmdanx7u	Apr 21, 2026	IA	Injury	0	1
cmo6itl3t0049o1auw1nkkrmd	Apr 12, 2026	TN	Injury	0	1
cmo6itl95008lo1au4lwl6k7c	Apr 11, 2026	NC	Injury	0	1
cmo6itlql00lfo1au2ekt7zw9	Apr 8, 2026	MO	Tow-Away	0	0
cmny3yh6n015xk38vo8e0q50u	Apr 1, 2026	OH	Tow-Away	0	0
cr_5127327	Mar 27, 2026	TN	Tow-Away	0	0
cr_5125457	Mar 24, 2026	TN	Tow-Away	0	0

Related records

Carrier

ABF FREIGHT SYSTEM INC

USDOT 82866 · 4,875 crashes · 4,094 inspections

Vehicle

VIN: 1M1AW01X9HM009878

Decode this VIN for make, model, year, and recall data.

State

Crashes in Kansas

Statewide crash records.

Agency

ABF FREIGHT SYSTEM INC

Crashes reported by this law-enforcement agency.

City

Crashes in LENEXA, KS

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.