Skip to main content
TruckCodex
Hubs

Crash Record MO0000110407

FMCSA crash record in GRANDVIEW on Oct 22, 2024.

Injury Federal Recordable

What happened

On October 22, 2024, FMCSA recorded an injury crash with 3 people hurt in GRANDVIEW, Missouri. The vehicle was operated by RUSH TRUCK LEASING INC (USDOT 333690). Recorded conditions: 1 / 1 pavement. Reported by RUSH TRUCK LEASING INC, FMCSA reference MO0000110407.

Carrier pattern note

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

Fatalities
0
Injuries
3
Vehicles
1
Carrier
RUSH TRUCK LEASING INC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
52
1 fatal · 16 injury
Crashes per 100 power units (24 mo)
0.6
45 crashes · 7,074 units
Days since prior carrier crash
27
Last on Sep 25, 2024
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,857 carriers

Geographic context

How this crash sits in its setting.

Within GRANDVIEW, Missouri, 26 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
—
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 #:
MO0000110407
Date:
Oct 22, 2024
Time:
1441
State:
Missouri
City:
GRANDVIEW
Fatalities:
0
Injuries:
3
Tow-Away:
Yes
HazMat:
No
Vehicles:
1
Carrier (USDOT):
RUSH TRUCK LEASING INC (333690)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 6 9 2NP3LJ0X0PM856394 NOTREQ (UK) RUSH TRUCK LEASING INC 3 No

Crash event

Event sequence description.

1:98:OTHER:OTHER;2:17:COLLISION INVOLVING ANIMAL

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5122536 Mar 18, 2026 DC Tow-Away 0 0
cr_5119955 Mar 12, 2026 WY Injury 0 1
cr_5115292 Feb 23, 2026 TX Tow-Away 0 0
cr_5117019 Feb 20, 2026 NV Tow-Away 0 0
cr_5088027 Dec 29, 2025 TX Injury 0 1
cr_5090757 Dec 9, 2025 FL Injury 0 1
cr_5073138 Dec 2, 2025 WV Tow-Away 0 0
cr_5069852 Nov 29, 2025 NC Tow-Away 0 0
cr_5076216 Nov 26, 2025 OH Tow-Away 0 0
cr_5067681 Nov 13, 2025 IL Tow-Away 0 0

Related records

Vehicle
2023 PETERBILT 348
NHTSA recalls and complaints for this make/model/year.
Recall
24V915000
ELECTRICAL SYSTEM
Recall
22V782000
STEERING:LINKAGES:TIE ROD ASSEMBLY
Recall
22V631000
ENGINE AND ENGINE COOLING:ENGINE:ENGINE CONTROL MODULE (ECU/ECM)
Carrier
RUSH TRUCK LEASING INC
USDOT 333690 · 348 crashes · 400 inspections
Vehicle
VIN: 2NP3LJ0X0PM856394
Decode this VIN for make, model, year, and recall data.
State
Crashes in Missouri
Statewide crash records.
Agency
RUSH TRUCK LEASING INC
Crashes reported by this law-enforcement agency.
City
Crashes in GRANDVIEW, 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.