FMCSA crash record in NON-CITY OR UNINCORPORATE on Aug 8, 2023.
InjuryFederal Recordable
What happened
On August 8, 2023, FMCSA recorded an injury crash with one person hurt in NON-CITY OR UNINCORPORATE, Missouri. The vehicle was operated by EMERGENCY MANAGEMENT SYSTEMS AND TRANSPORT LLC (USDOT 3543155). Recorded conditions: 2 / 1 / 1 pavement. Reported by EMERGENCY MANAGEMENT SYSTEMS AND TRANSPORT LLC, FMCSA reference MO0000103733.
Carrier pattern note
This is the carrier's 4 crashes in the past 24 months — above the typical pattern (median 0) for fleets of 6–50 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
1
Carrier
EMERGENCY MANAGEMENT SYSTEMS AND TRANSPORT LLC
Vehicle Type
Truck
Severity
Injury
This carrier's crash pattern
Derived from the carrier's full crash history.
Carrier crashes (24 mo)
4
3 injury · 4 tow-away
Crashes per 100 power units (24 mo)
3.3
1 crashes · 30 units
Days since prior carrier crash
203
Last on Jan 17, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 312,424 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.
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.