Skip to main content
TruckCodex
Hubs

Crash Record MO0000104839

FMCSA crash record in KANSAS CITY on Oct 11, 2023.

Tow-Away Federal Recordable

What happened

On October 11, 2023, FMCSA recorded a tow-away crash with no reported injuries in KANSAS CITY, Missouri. The vehicle was operated by LONE STAR TRANSPORTATION LLC (USDOT 320691). Recorded conditions: 1 / 9 / 1 pavement. Reported by LONE STAR TRANSPORTATION LLC, FMCSA reference MO0000104839.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
1
Carrier
LONE STAR TRANSPORTATION LLC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
38
10 injury · 36 tow-away
Crashes per 100 power units (24 mo)
7.2
29 crashes · 404 units
Days since prior carrier crash
2
Last on Oct 9, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,879 carriers

Geographic context

How this crash sits in its setting.

Within KANSAS CITY, Missouri, 718 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
9
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 #:
MO0000104839
Date:
Oct 11, 2023
Time:
1447
State:
Missouri
City:
KANSAS CITY
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
1
Carrier (USDOT):
LONE STAR TRANSPORTATION LLC (320691)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 8 12 1XKZD49X2JJ208920 DA55DR (MO) LONE STAR TRANSPORTATION LLC 3 No

Crash event

Event sequence description.

1:98:OTHER;2:98:OTHER;3:6:NONCOLLISION:EXPLOSION OR FIRE;4:18:COLLISION INVOLVING FIXED OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5127901 Mar 20, 2026 TX Injury 0 1
cr_5098998 Jan 24, 2026 MO Tow-Away 0 0
cr_5081439 Dec 19, 2025 NC Injury 0 1
cr_5072226 Nov 18, 2025 TX Tow-Away 0 0
cr_5077246 Nov 18, 2025 TX Injury 0 1
cr_5072184 Nov 10, 2025 TX Tow-Away 0 0
cr_5095152 Nov 3, 2025 IL Tow-Away 0 0
cr_5053817 Oct 11, 2025 TX Injury 0 1
cr_5019780 Aug 21, 2025 OK Tow-Away 0 0
cr_5041632 Aug 19, 2025 TX Tow-Away 0 0

Related records

Vehicle
2018 KENWORTH T880
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
LONE STAR TRANSPORTATION LLC
USDOT 320691 · 766 crashes · 2,939 inspections
Vehicle
VIN: 1XKZD49X2JJ208920
Decode this VIN for make, model, year, and recall data.
State
Crashes in Missouri
Statewide crash records.
Agency
LONE STAR TRANSPORTATION LLC
Crashes reported by this law-enforcement agency.
City
Crashes in KANSAS CITY, MO
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.