TruckCodex
Hubs

Crash Record KS2023E25232

FMCSA crash record in LENEXA on Jan 27, 2023.

Tow-Away Federal Recordable

What happened

On January 27, 2023, FMCSA recorded a tow-away crash with no reported injuries in LENEXA, Kansas. The vehicle was operated by ESTES EXPRESS LINES (USDOT 121018). Recorded conditions: 3 / 1 / 1 pavement. Reported by ESTES EXPRESS LINES, FMCSA reference KS2023E25232.

Carrier pattern note

This is the carrier's 578 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
ESTES EXPRESS LINES
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
578
21 fatal · 180 injury
Crashes per 100 power units (24 mo)
4.9
477 crashes · 9,805 units
Days since prior carrier crash
1
Last on Jan 26, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,837 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
3
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 #:
KS2023E25232
Date:
Jan 27, 2023
Time:
0045
State:
Kansas
City:
LENEXA
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
ESTES EXPRESS LINES (121018)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 10 8 3HSDZAPRXNN050606 NP2273 (NC) ESTES EXPRESS LINES 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
cmsw88s6a0057pev3r146967x Aug 10, 2026 NC Injury 0 1
cmshdfe76000bpefy6qhcvfp2 Jul 31, 2026 OH Injury 0 1
cms8hio0p000fpeo5t4hsliwe Jul 26, 2026 NC Tow-Away 0 0
cms1c436x004fpee88ssjbxgy Jul 20, 2026 NJ Tow-Away 0 0
cmrn1fc43000dpez58l7k4248 Jul 11, 2026 NC Injury 0 1
cmqg6ahmm000bp48dbin0k41p Jun 11, 2026 TN Tow-Away 0 0
cmqesjpmp003vp4us3qim7lgf Jun 9, 2026 PA Tow-Away 0 0
cmqesjq9z007vp4usqu0w4d2r Jun 8, 2026 IA Injury 0 1
cmqafcgfk001nqun6uzsspf2b Jun 5, 2026 OH Injury 0 1
cmq3bahrv002hpbhen1ott920 Jun 2, 2026 MI Tow-Away 0 0

Related records

Vehicle
2022 INTERNATIONAL LT625
NHTSA recalls and complaints for this make/model/year.
Carrier
ESTES EXPRESS LINES
USDOT 121018 · 6,285 crashes · 8,160 inspections
Vehicle
VIN: 3HSDZAPRXNN050606
Decode this VIN for make, model, year, and recall data.
State
Crashes in Kansas
Statewide crash records.
Agency
ESTES EXPRESS LINES
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.