TruckCodex
Hubs

Crash Record KS2023E26222

FMCSA crash record in LENEXA on Jul 28, 2023.

Tow-Away Federal Recordable

What happened

On July 28, 2023, FMCSA recorded a tow-away crash with no reported injuries in LENEXA, Kansas. The vehicle was operated by SANTA FE TOW SERVICE INC (USDOT 99313). Recorded conditions: 1 / 1 / 1 pavement. Reported by Santa Fe Tow Service INC, FMCSA reference KS2023E26222.

Carrier pattern note

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

Geographic note

This crash is part of an active corridor: 48 crashes occurred in the same city in the past 24 months.

Fatalities
0
Injuries
0
Vehicles
2
Carrier
SANTA FE TOW 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)
4
1 injury · 4 tow-away
Crashes per 100 power units (24 mo)
9.6
5 crashes · 52 units
Days since prior carrier crash
444
Last on May 10, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,833 carriers

Geographic context

How this crash sits in its setting.

Within LENEXA, Kansas, 48 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 #:
KS2023E26222
Date:
Jul 28, 2023
Time:
1758
State:
Kansas
City:
LENEXA
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
SANTA FE TOW SERVICE INC (99313)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 6 98 1NPXX4TX5JD449140 B639140 (KS) Santa Fe Tow Service 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
cmsmuqwyu0005pexo64hp0rr5 Aug 6, 2026 OK Injury 0 1
cr_5086263 Jan 8, 2026 KS Tow-Away 0 0
cr_5084522 Jan 2, 2026 OK Tow-Away 0 0
cr_4880653 Jan 19, 2025 KY Tow-Away 0 0
cr_4887023 Dec 18, 2024 KS Tow-Away 0 0
cr_4747549 May 7, 2024 MO Tow-Away 0 0
cr_4649107 Oct 10, 2023 MO Injury 0 1
cr_4360874 May 10, 2022 MO Tow-Away 0 0
cr_4321643 Jan 18, 2022 KS Injury 0 1
cr_4244135 Oct 18, 2021 KS Tow-Away 0 0

Related records

Vehicle
2018 PETERBILT 389
NHTSA recalls and complaints for this make/model/year.
Recall
22V277000
STEERING:CRITICAL FASTENERS
Recall
20V199000
ELECTRONIC STABILITY CONTROL (ESC)
Recall
20V130000
ELECTRICAL SYSTEM:12V/24V/48V BATTERY:CABLES
Carrier
SANTA FE TOW SERVICE INC
USDOT 99313 · 65 crashes · 38 inspections
Vehicle
VIN: 1NPXX4TX5JD449140
Decode this VIN for make, model, year, and recall data.
State
Crashes in Kansas
Statewide crash records.
Agency
Santa Fe Tow Service 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.