Skip to main content
TruckCodex
Hubs

Crash Record IN0904468187

FMCSA crash record in EVANSVILLE on Mar 8, 2024.

Injury Federal Recordable

What happened

On March 8, 2024, FMCSA recorded an injury crash with 2 people hurt in EVANSVILLE, Indiana. The vehicle was operated by ROLLING FRITO LAY SALES LP (USDOT 926150). Recorded conditions: 1 / 2 / 2 pavement. Reported by ROLLING FRITO LAY SALES LP, FMCSA reference IN0904468187.

Carrier pattern note

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

Fatalities
0
Injuries
2
Vehicles
2
Carrier
ROLLING FRITO LAY SALES LP
USDOT 926150
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
170
5 fatal · 57 injury
Crashes per 100 power units (24 mo)
0.9
137 crashes · 15,635 units
Days since prior carrier crash
3
Last on Mar 5, 2024
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,881 carriers

Geographic context

How this crash sits in its setting.

Within EVANSVILLE, Indiana, 131 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
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 #:
IN0904468187
Date:
Mar 8, 2024
Time:
0634
State:
Indiana
City:
EVANSVILLE
Fatalities:
0
Injuries:
2
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
ROLLING FRITO LAY SALES LP (926150)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 5 3 3BPPHM6X5NF594970 A446830 (IN) ROLLING FRITO LAY SALES LP 2 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
cmvettr7t017hogssmrfkdj3v Oct 6, 2026 TX Tow-Away 0 0
cmsbbctmr0007pemdtns759bj Jul 27, 2026 OK Tow-Away 0 0
cmsbbctq3002rpemd43yz229z Jul 27, 2026 OK Tow-Away 0 0
cmqkg78ba00jnp8fy9pzncx26 Jun 10, 2026 AL Tow-Away 0 0
cmpezcv9o002lpj79iqiijrty May 15, 2026 NJ Injury 0 1
cmp6e5pjb0011nuyqkvgclbkh May 10, 2026 NJ Injury 0 1
cmo6itlvh00poo1auopaqjp1d Apr 10, 2026 AR Injury 0 1
cr_5123750 Mar 19, 2026 NC Fatal 1 0
cr_5108825 Feb 17, 2026 SD Tow-Away 0 0
cr_5114725 Feb 16, 2026 GA Injury 0 2

Carrier booking & risk tools

Check booking and risk signals for USDOT 926150 — tools open pre-filled.

Book / don't book Insurance check Cancel desk Chameleon check Safety benchmark

Related records

Carrier
ROLLING FRITO LAY SALES LP
USDOT 926150 · 1,364 crashes · 3,039 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 3BPPHM6X5NF594970
Decode this VIN for make, model, year, and recall data.
State
Crashes in Indiana
Statewide crash records.
Agency
ROLLING FRITO LAY SALES LP
Crashes reported by this law-enforcement agency.
City
Crashes in EVANSVILLE, IN
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.