Skip to main content
TruckCodex
Hubs

Crash Record MO0000113216

FMCSA crash record in NON-CITY OR UNINCORPORATE on Jan 2, 2025.

Injury Federal Recordable Bus

What happened

On January 2, 2025, FMCSA recorded an injury crash with 2 people hurt in NON-CITY OR UNINCORPORATE, Missouri. The vehicle was operated by BI-STATE DEVELOPMENT. Recorded conditions: 1 / 9 / 1 pavement. FMCSA reference MO0000113216.

Geographic note

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

Fatalities
0
Injuries
2
Vehicles
2
Carrier
BI-STATE DEVELOPMENT
Vehicle Type
Bus
Severity
Injury

Geographic context

How this crash sits in its setting.

Within NON-CITY OR UNINCORPORATE, Missouri, 3,418 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
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 #:
MO0000113216
Date:
Jan 2, 2025
Time:
1507
State:
Missouri
City:
NON-CITY OR UNINCORPORATE
Fatalities:
0
Injuries:
2
Tow-Away:
No
HazMat:
No
Vehicles:
2
Carrier (as reported):
BI-STATE DEVELOPMENT

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
2 3 1 1FDES9PM1KKA63706 4713 (MO) BI-STATE DEVELOPMENT 2 No

Crash event

Event sequence description.

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

Related records

Vehicle
2019 FORD Transit
NHTSA recalls and complaints for this make/model/year.
Recall
25V876000
EQUIPMENT ADAPTIVE/MOBILITY
Recall
25V572000
BACK OVER PREVENTION
Recall
25V442000
BACK OVER PREVENTION
Vehicle
VIN: 1FDES9PM1KKA63706
Decode this VIN for make, model, year, and recall data.
State
Crashes in Missouri
Statewide crash records.
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.