Skip to main content
TruckCodex
Hubs

Crash Record MO0000112816

FMCSA crash record in BLUE SPRINGS on Mar 21, 2025.

Tow-Away Federal Recordable

What happened

On March 21, 2025, FMCSA recorded a tow-away crash with no reported injuries in BLUE SPRINGS, Missouri. The vehicle was operated by TRANSERVICE LOGISTICS INC (USDOT 620402). Recorded conditions: 1 / 9 / 1 pavement. FMCSA reference MO0000112816.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
USDOT 620402
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
46
1 fatal · 14 injury
Crashes per 100 power units (24 mo)
3.0
21 crashes · 695 units
Days since prior carrier crash
30
Last on Feb 19, 2025
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,878 carriers

Geographic context

How this crash sits in its setting.

Within BLUE SPRINGS, Missouri, 49 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 #:
MO0000112816
Date:
Mar 21, 2025
Time:
1058
State:
Missouri
City:
BLUE SPRINGS
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
2 7 3 3HSDZAPR0RN664490 3453104 (IN) TRANSERVICE LOGISTICS INC 3 No

Crash event

Event sequence description.

1:98:OTHER;2:98:OTHER:OTHER;3: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_5110120 Feb 13, 2026 KY Injury 0 2
cr_5086579 Jan 2, 2026 OH Injury 0 1
cr_5088569 Dec 5, 2025 NY Tow-Away 0 0
cr_5005148 Jul 29, 2025 OH Tow-Away 0 0
cr_4954957 May 6, 2025 GA Injury 0 1
cr_4937468 May 2, 2025 KY Tow-Away 0 0
cr_4949881 Apr 26, 2025 KY Injury 0 1
cr_4941392 Apr 11, 2025 GA Injury 0 2
cr_4942448 Feb 19, 2025 MA Tow-Away 0 0
cr_4928542 Feb 15, 2025 GA Injury 0 1

Carrier booking & risk tools

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

Related records

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.