Crash Record MO0000095560

FMCSA crash record in NON-CITY OR UNINCORPORATE on Feb 2, 2022.

Tow-Away Federal Recordable

What happened

On February 2, 2022, FMCSA recorded a tow-away crash with no reported injuries in NON-CITY OR UNINCORPORATE, Missouri. The vehicle was operated by LIBERTY FRUIT CO INC (USDOT 372767). Recorded conditions: 2 / 4 / 4 pavement. Reported by LIBERTY FRUIT COMPANY INC, FMCSA reference MO0000095560.

Geographic note

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

Fatalities

Injuries

Vehicles

Carrier

LIBERTY FRUIT CO INC

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

1 injury · 3 tow-away

Crashes per 100 power units (24 mo)

0.0

0 crashes · 62 units

Days since prior carrier crash

417

Last on Dec 12, 2020

Vs fleet-size peers

above the median

Cohort median 0.0 · 26,697 carriers

Geographic context

How this crash sits in its setting.

Within NON-CITY OR UNINCORPORATE, Missouri, 3,912 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: 2
Weather: 4
Road surface: 4

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 #:: MO0000095560
Date:: Feb 2, 2022
Time:: 0500
State:: Missouri
City:: NON-CITY OR UNINCORPORATE
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 1
Carrier (USDOT):: LIBERTY FRUIT CO INC (372767)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	9	3	1XKYD49X3KJ342977	179119 (KS)	LIBERTY FRUIT COMPANY INC	3	No

Crash event

Event sequence description.

1:98:OTHER;2:98:OTHER: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	Injuries
cr_4757787	May 25, 2024	AR	Tow-Away	0
cr_4524719	Mar 6, 2023	KS	Injury	1
cr_4712477	Dec 15, 2022	NE	Injury	1
cr_4107873	Dec 12, 2020	IA	Tow-Away	0
cr_4072616	Dec 7, 2020	AR	Injury	1
cr_3832399	Aug 13, 2019	IA	Injury	1
cr_3795628	May 23, 2019	MO	Tow-Away	0
cr_3714346	Dec 28, 2018	MO	Injury	1
cr_3633387	Jul 24, 2018	MO	Injury	1
cr_3557694	Mar 4, 2018	MO	Tow-Away	0

Related records

Vehicle

2019 KENWORTH T680

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

LIBERTY FRUIT CO INC

USDOT 372767 · 84 crashes · 0 inspections

Vehicle

VIN: 1XKYD49X3KJ342977

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

State

Crashes in Missouri

Statewide crash records.

Agency

LIBERTY FRUIT COMPANY 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.