Crash Record MO0000101861

FMCSA crash record in NON-CITY OR UNINCORPORATE on Mar 18, 2023.

Tow-Away Federal Recordable

What happened

On March 18, 2023, FMCSA recorded a tow-away crash with no reported injuries in NON-CITY OR UNINCORPORATE, Missouri. The vehicle was operated by VAMAR INC (USDOT 3145664). Recorded conditions: 1 / 9 / 1 pavement. Reported by VAMAR INC, FMCSA reference MO0000101861.

Carrier pattern note

This is the carrier's 55 crashes in the past 24 months — above the typical pattern (median 0) for fleets of 1–5 power units.

Geographic note

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

Fatalities

Injuries

Vehicles

Carrier

VAMAR INC

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

3 fatal · 13 injury

Crashes per 100 power units (24 mo)

1300.0

13 crashes · 1 units

Days since prior carrier crash

Last on Mar 7, 2023

Vs fleet-size peers

above the median

Cohort median 0.0 · 3,564,214 carriers

Geographic context

How this crash sits in its setting.

Within NON-CITY OR UNINCORPORATE, Missouri, 3,767 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 · 14 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 #:: MO0000101861
Date:: Mar 18, 2023
Time:: 1000
State:: Missouri
City:: NON-CITY OR UNINCORPORATE
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 1
Carrier (USDOT):: VAMAR INC (3145664)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	9	3	3AKJHHDR6KSKC2363	JD27IT (FL)	VAMAR INC	3	No

Crash event

Event sequence description.

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

Other crashes by this carrier

10 additional crash record(s) on file.

Record	Date	State	Severity	Injuries
cr_4920375	Feb 20, 2025	IN	Tow-Away	0
cr_4897559	Feb 4, 2025	OR	Tow-Away	0
cr_4887001	Jan 31, 2025	TN	Tow-Away	0
cr_4882648	Jan 15, 2025	TX	Tow-Away	0
cr_4875343	Jan 11, 2025	AZ	Tow-Away	0
cr_4877649	Jan 10, 2025	AR	Tow-Away	0
cr_4861110	Dec 14, 2024	IA	Tow-Away	0
cr_4865662	Dec 9, 2024	KS	Tow-Away	0
cr_4896899	Dec 3, 2024	MD	Tow-Away	0
cr_4847112	Oct 27, 2024	NV	Injury	1

Related records

Vehicle

2019 FREIGHTLINER Cascadia

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

Recall

23V105000

STEERING:LINKAGES:DRAG:LINK:CONNECTION

Recall

23V073000

ELECTRONIC STABILITY CONTROL (ESC)

USDOT 3145664 · 99 crashes · 969 inspections

Vehicle

VIN: 3AKJHHDR6KSKC2363

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

State

Crashes in Missouri

Statewide crash records.

Agency

VAMAR 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.