Skip to main content
TruckCodex
Hubs

Crash Record TN0400055833

FMCSA crash record in NASHVILLE on Feb 13, 2024.

Tow-Away Federal Recordable

What happened

On February 13, 2024, FMCSA recorded a tow-away crash with no reported injuries in NASHVILLE, Tennessee. The vehicle was operated by ELECTRONIC EXPRESS INC (USDOT 2171242). Recorded conditions: 1 / 1 / 1 pavement. Reported by ELECTRONIC EXPRESS INC, FMCSA reference TN0400055833.

Geographic note

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

Fatalities
0
Injuries
0
Vehicles
1
Carrier
ELECTRONIC EXPRESS INC
USDOT 2171242
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
2
1 injury · 2 tow-away
Crashes per 100 power units (24 mo)
0.0
0 crashes · 14 units
Days since prior carrier crash
144
Last on Sep 22, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 316,148 carriers

Geographic context

How this crash sits in its setting.

Within NASHVILLE, Tennessee, 843 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
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 #:
TN0400055833
Date:
Feb 13, 2024
Time:
1123
State:
Tennessee
City:
NASHVILLE
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
1
Carrier (USDOT):
ELECTRONIC EXPRESS INC (2171242)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 5 3 1FVACWDT2CHBJ5523 H411395 (TN) ELECTRONIC EXPRESS INC 2 No

Crash event

Event sequence description.

1:18:COLLISION INVOLVING FIXED OBJECT

Other crashes by this carrier

9 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4627821 Sep 22, 2023 AL Injury 0 2
cr_4022580 Aug 18, 2020 TN Tow-Away 0 0
cr_4035551 Jul 20, 2020 GA Injury 0 1
cr_3966747 Apr 30, 2020 TN Tow-Away 0 0
cr_3715285 Jan 5, 2019 TN Injury 0 2
cr_3367979 Mar 7, 2017 TN Tow-Away 0 0
cr_2939800 Oct 21, 2014 TN Tow-Away 0 0
cr_2586013 Jul 18, 2012 TN Tow-Away 0 0
cr_2470878 Oct 4, 2011 TN Tow-Away 0 0

Carrier booking & risk tools

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

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

Related records

Vehicle
2012 FREIGHTLINER M2
NHTSA recalls and complaints for this make/model/year.
Recall
19V370000
SERVICE BRAKES, AIR:SUPPLY:RESERVOIR/TANK
Recall
15V343000
ENGINE AND ENGINE COOLING:ENGINE
Recall
15V220000
EXTERIOR LIGHTING:BRAKE LIGHTS:SWITCH
Carrier
ELECTRONIC EXPRESS INC
USDOT 2171242 · 10 crashes · 12 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 1FVACWDT2CHBJ5523
Decode this VIN for make, model, year, and recall data.
State
Crashes in Tennessee
Statewide crash records.
Agency
ELECTRONIC EXPRESS INC
Crashes reported by this law-enforcement agency.
City
Crashes in NASHVILLE, TN
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.