TruckCodex
Hubs

Crash Record KS2021E21250

FMCSA crash record in LENEXA on Mar 25, 2021.

Tow-Away Federal Recordable

What happened

On March 25, 2021, FMCSA recorded a tow-away crash with no reported injuries in LENEXA, Kansas. The vehicle was operated by UNITED PARCEL SERVICE INC (USDOT 21800). Recorded conditions: 5 / 2 / 2 pavement. Reported by UPS, FMCSA reference KS2021E21250.

Carrier pattern note

This is the carrier's 2908 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
0
Injuries
0
Vehicles
2
Carrier
UNITED PARCEL SERVICE INC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
2,908
70 fatal · 1083 injury
Crashes per 100 power units (24 mo)
1.7
1,865 crashes · 112,321 units
Days since prior carrier crash
1
Last on Mar 24, 2021
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:

Contributing factors

What the responding officer recorded.

Light
5
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 #:
KS2021E21250
Date:
Mar 25, 2021
Time:
0659
State:
Kansas
City:
LENEXA
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
UNITED PARCEL SERVICE INC (21800)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 1NKYD39X6JJ191488 2543861 (IN) UPS 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
cmt5onxzn001bpmdmhgets6gl Aug 18, 2026 WA Tow-Away 0 0
cmt1jo1360061pevkj3jflftt Aug 14, 2026 FL Tow-Away 0 0
cmsw88sbd00bbpev3krucoz20 Aug 8, 2026 PA Tow-Away 0 0
cmscs00180017peturqwgv4y0 Jul 28, 2026 WI Tow-Away 0 0
cmrx2ea3z000npequz3q1blww Jul 17, 2026 OH Tow-Away 0 0
cmrss3uwc000fpefbpnxy28j8 Jul 16, 2026 NJ Tow-Away 0 0
cmrrbu4yx000dpebfj6sd1yvw Jul 15, 2026 PA Tow-Away 0 0
cmrfwlwi0000zmlhry0t0sjyy Jul 6, 2026 WI Tow-Away 0 0
cmr7aydgs002pp8qshe4guwd6 Jun 30, 2026 OK Tow-Away 0 0
cmr7aydhz005dp8qsgy28stx6 Jun 29, 2026 AL Injury 0 1

Related records

Vehicle
2018 KENWORTH T680
NHTSA recalls and complaints for this make/model/year.
Recall
24V145000
SERVICE BRAKES, AIR:SUPPLY:RESERVOIR/TANK
Recall
22V277000
STEERING:CRITICAL FASTENERS
Recall
21V00N000
ELECTRICAL SYSTEM:WIRING
Carrier
UNITED PARCEL SERVICE INC
USDOT 21800 · 28,017 crashes · 32,139 inspections
Vehicle
VIN: 1NKYD39X6JJ191488
Decode this VIN for make, model, year, and recall data.
State
Crashes in Kansas
Statewide crash records.
Agency
UPS
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.