Crash Record MO0000100708

FMCSA crash record in NON-CITY OR UNINCORPORATE on Dec 1, 2022.

Tow-Away Federal Recordable

What happened

On December 1, 2022, FMCSA recorded a tow-away crash with no reported injuries in NON-CITY OR UNINCORPORATE, Missouri. The vehicle was operated by NUCO2 SUPPLY LLC (USDOT 578807). Recorded conditions: 2 / 1 / 1 pavement. Reported by NUCO2 SUPPLY LLC, FMCSA reference MO0000100708.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

NUCO2 SUPPLY LLC

USDOT 578807

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

2 fatal · 5 injury

Crashes per 100 power units (24 mo)

1.0

7 crashes · 677 units

Days since prior carrier crash

Last on Oct 27, 2022

Vs fleet-size peers

above the median

Cohort median 0.0 · 3,888 carriers

Geographic context

How this crash sits in its setting.

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

Agencies most active in this area:

FEDERAL EXPRESS CORPORATION · 14 reports
FEDEX EXPRESS FEDEX · 12 reports
ESTES EXPRESS LINES · 7 reports

Contributing factors

What the responding officer recorded.

Light: 2
Weather: 1
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 #:: MO0000100708
Date:: Dec 1, 2022
Time:: 1920
State:: Missouri
City:: NON-CITY OR UNINCORPORATE
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 1
Carrier (USDOT):: NUCO2 SUPPLY LLC (578807)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	5	4	3ALACXCY9HDJB9996	2562740 (IN)	NUCO2 SUPPLY LLC	3	Yes

Crash event

Event sequence description.

1:98:OTHER:OTHER;4:98:OTHER:OTHER;3:98:OTHER: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_5103693	Dec 31, 2025	FL	Injury	1
cr_5073487	Nov 10, 2025	AL	Tow-Away	0
cr_5039225	Sep 24, 2025	MO	Injury	2
cr_5005684	Jun 6, 2025	OK	Injury	2
cr_4992819	May 26, 2025	GA	Tow-Away	0
cr_4922233	Mar 22, 2025	CO	Tow-Away	0
cr_4928994	Mar 4, 2025	GA	Injury	1
cr_4807298	Sep 4, 2024	FL	Injury	1
cr_4912756	Jul 19, 2024	MD	Tow-Away	0
cr_4745548	Mar 13, 2024	VA	Injury	1

Carrier booking & risk tools

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

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

Related records

Vehicle

2017 FREIGHTLINER M2

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

SERVICE BRAKES, AIR:SUPPLY:RESERVOIR/TANK

Carrier

NUCO2 SUPPLY LLC

USDOT 578807 · 225 crashes · 1,629 inspections

Safety

Carrier inspections

Roadside inspection history for this USDOT.

Vehicle

VIN: 3ALACXCY9HDJB9996

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

State

Crashes in Missouri

Statewide crash records.

Agency

NUCO2 SUPPLY LLC

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.