Crash Record MO0000109039

FMCSA crash record in NON-CITY OR UNINCORPORATE on Jul 16, 2024.

Injury Federal Recordable

What happened

On July 16, 2024, FMCSA recorded an injury crash with 2 people hurt in NON-CITY OR UNINCORPORATE, Missouri. The vehicle was operated by LESTER VENTURES INC (USDOT 2782302). Recorded conditions: 1 / 9 / 1 pavement. Reported by LESTER VENTURES INC, FMCSA reference MO0000109039.

Geographic note

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

Fatalities

Injuries

Vehicles

Carrier

LESTER VENTURES INC

Vehicle Type

Truck

Severity

Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

1 injury · 1 tow-away

Crashes per 100 power units (24 mo)

33.3

1 crashes · 3 units

Prior carrier crash

—

No earlier crash on file

Vs fleet-size peers

above the median

Cohort median 0.0 · 3,554,620 carriers

Geographic context

How this crash sits in its setting.

Within NON-CITY OR UNINCORPORATE, Missouri, 3,938 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

FEDEX EXPRESS FEDEX · 17 reports
FEDERAL EXPRESS CORPORATION · 15 reports
ESTES EXPRESS LINES · 7 reports

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 #:: MO0000109039
Date:: Jul 16, 2024
Time:: 1650
State:: Missouri
City:: NON-CITY OR UNINCORPORATE
Fatalities:: 0
Injuries:: 2
Tow-Away:: Yes
HazMat:: No
Vehicles:: 3
Carrier (USDOT):: LESTER VENTURES INC (2782302)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	5	5	3C7WRNEL2LG214880	41J2ND (MO)	LESTER VENTURES INC	3	No

Crash event

Event sequence description.

1:98:OTHER:OTHER;2:98:OTHER;3:20:COLLISION INVOLVING OTHER MOVABLE OBJECT

Other crashes by this carrier

1 additional crash record(s) on file.

Record	Date	State	Severity	Fatalities	Injuries
cr_4815644	Sep 11, 2024	MO	Tow-Away	0	0

Related records

Vehicle

2020 RAM 5500

NHTSA recalls and complaints for this make/model/year.

Recall

22V759000

SERVICE BRAKES, HYDRAULIC:FOUNDATION COMPONENTS:HOSES, LINES/PIPING, AND FITTINGS

Recall

22V035000

VISIBILITY:WINDSHIELD WIPER/WASHER:LINKAGES

Recall

21V880000

FUEL SYSTEM, DIESEL:DELIVERY:FUEL PUMP

Carrier

LESTER VENTURES INC

USDOT 2782302 · 2 crashes · 4 inspections

Vehicle

VIN: 3C7WRNEL2LG214880

Decode this VIN for make, model, year, and recall data.

State

Crashes in Missouri

Statewide crash records.

Agency

LESTER VENTURES INC

Crashes reported by this law-enforcement agency.

City

Crashes in NON-CITY OR UNINCORPORATE, 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.