Skip to main content
TruckCodex
Hubs

Crash Record TN0400122768

FMCSA crash record in Tennessee on Jul 25, 2024.

Injury Federal Recordable

What happened

On July 25, 2024, FMCSA recorded an injury crash with one person hurt in Tennessee. The vehicle was operated by MBL DEDICATED LLC (USDOT 1894931). Recorded conditions: 6 / 1 / 1 pavement. Reported by MBL DEDICATED LLC, FMCSA reference TN0400122768.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
2
Carrier
MBL DEDICATED LLC
USDOT 1894931
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
6
2 injury · 6 tow-away
Crashes per 100 power units (24 mo)
14.3
3 crashes · 21 units
Days since prior carrier crash
146
Last on Mar 1, 2024
Vs fleet-size peers
above the median
Cohort median 0.0 · 314,932 carriers

Geographic context

How this crash sits in its setting.

Within Tennessee, 7,015 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
6
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 #:
TN0400122768
Date:
Jul 25, 2024
Time:
1905
State:
Tennessee
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
MBL DEDICATED LLC (1894931)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 4V4NC9EH6RN655123 1185990 (AL) MBL DEDICATED LLC 3 No

Crash event

Event sequence description.

1: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_5112590 Feb 16, 2026 VA Tow-Away 0 0
cr_5063145 Oct 23, 2025 IN Injury 0 1
cr_5018151 Jul 9, 2025 MO Tow-Away 0 0
cr_4707381 Mar 1, 2024 KY Tow-Away 0 0
cr_4709973 Feb 16, 2024 MO Tow-Away 0 0
cr_4694792 Jan 31, 2024 MA Tow-Away 0 0
cr_4595772 Jul 27, 2023 TN Injury 0 1
cr_4450250 Nov 7, 2022 TN Tow-Away 0 0
cr_4351401 May 3, 2022 MI Tow-Away 0 0
cr_3939627 Feb 24, 2020 AL Injury 0 1

Carrier booking & risk tools

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

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

Related records

Vehicle
2024 VOLVO TRUCK VNL
NHTSA recalls and complaints for this make/model/year.
Carrier
MBL DEDICATED LLC
USDOT 1894931 · 18 crashes · 111 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 4V4NC9EH6RN655123
Decode this VIN for make, model, year, and recall data.
State
Crashes in Tennessee
Statewide crash records.
Agency
MBL DEDICATED LLC
Crashes reported by this law-enforcement agency.
Station
I-75
Weigh / inspection station matching this crash location.
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.