TruckCodex
Hubs

Crash Record MO0000100207

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

Injury Federal Recordable

What happened

On December 7, 2022, FMCSA recorded an injury crash with one person hurt in NON-CITY OR UNINCORPORATE, Missouri. The vehicle was operated by SYNAGRO CENTRAL LLC (USDOT 629180). Recorded conditions: 1 / 5 / 2 pavement. Reported by SYNAGRO CENTRAL LLC, FMCSA reference MO0000100207.

Carrier pattern note

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

Geographic note

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

Fatalities
0
Injuries
1
Vehicles
2
Carrier
SYNAGRO CENTRAL LLC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
5
4 injury · 5 tow-away
Crashes per 100 power units (24 mo)
1.1
1 crashes · 93 units
Days since prior carrier crash
29
Last on Nov 8, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,602 carriers

Geographic context

How this crash sits in its setting.

Within NON-CITY OR UNINCORPORATE, Missouri, 3,956 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
5
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 #:
MO0000100207
Date:
Dec 7, 2022
Time:
0910
State:
Missouri
City:
NON-CITY OR UNINCORPORATE
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
SYNAGRO CENTRAL LLC (629180)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 6 4 1NPXX4EX6KD613333 P1131216 (IL) SYNAGRO CENTRAL LLC 3 No

Crash event

Event sequence description.

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

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4935786 Apr 28, 2025 NC Injury 0 1
cr_4769253 Jun 17, 2024 OH Injury 0 2
cr_4639962 Oct 18, 2023 IA Tow-Away 0 0
cr_4504232 Jan 17, 2023 MO Injury 0 1
cr_4486463 Jan 5, 2023 IA Tow-Away 0 0
cr_4467404 Dec 7, 2022 VA Injury 0 2
cr_4454133 Nov 8, 2022 NC Injury 0 1
cr_4460467 Nov 3, 2022 NC Tow-Away 0 0
cr_4475921 Oct 17, 2022 AR Injury 0 1
cr_4046345 Sep 11, 2020 IL Tow-Away 0 0

Related records

Vehicle
2019 PETERBILT 389
NHTSA recalls and complaints for this make/model/year.
Recall
22V277000
STEERING:CRITICAL FASTENERS
Recall
21V906000
ELECTRICAL SYSTEM:SOFTWARE
Recall
20V199000
ELECTRONIC STABILITY CONTROL (ESC)
Carrier
SYNAGRO CENTRAL LLC
USDOT 629180 · 39 crashes · 73 inspections
Vehicle
VIN: 1NPXX4EX6KD613333
Decode this VIN for make, model, year, and recall data.
State
Crashes in Missouri
Statewide crash records.
Agency
SYNAGRO CENTRAL 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.