Skip to main content
TruckCodex
Hubs

Crash Record TN0400138885

FMCSA crash record in Tennessee on Aug 29, 2024.

Tow-Away Federal Recordable

What happened

On August 29, 2024, FMCSA recorded a tow-away crash with no reported injuries in Tennessee. The vehicle was operated by EPES TRANSPORT SYSTEM LLC (USDOT 120195). Recorded conditions: 1 / 1 / 1 pavement. Reported by EPES TRANSPORT SYSTEM LLC, FMCSA reference TN0400138885.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
EPES TRANSPORT SYSTEM LLC
USDOT 120195
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
113
5 fatal · 40 injury
Crashes per 100 power units (24 mo)
4.7
42 crashes · 896 units
Days since prior carrier crash
7
Last on Aug 22, 2024
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,884 carriers

Geographic context

How this crash sits in its setting.

Within Tennessee, 6,798 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 #:
TN0400138885
Date:
Aug 29, 2024
Time:
0617
State:
Tennessee
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
EPES TRANSPORT SYSTEM LLC (120195)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 1FUJGLDR9KLKD3035 NH9706 (NC) EPES TRANSPORT SYSTEM 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_5125213 Mar 9, 2026 NC Injury 0 1
cr_5121193 Feb 27, 2026 MS Tow-Away 0 0
cr_5105348 Feb 15, 2026 NC Tow-Away 0 0
cr_5107843 Feb 10, 2026 GA Tow-Away 0 0
cr_5095329 Jan 26, 2026 AL Tow-Away 0 0
cr_5074017 Dec 2, 2025 GA Injury 0 1
cr_5072975 Nov 25, 2025 VA Tow-Away 0 0
cr_5059878 Nov 10, 2025 NC Tow-Away 0 0
cr_5055371 Oct 31, 2025 LA Injury 0 1
cr_5058146 Oct 9, 2025 NC Injury 0 1

Carrier booking & risk tools

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

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

Related records

Carrier
EPES TRANSPORT SYSTEM LLC
USDOT 120195 · 1,214 crashes · 2,673 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 1FUJGLDR9KLKD3035
Decode this VIN for make, model, year, and recall data.
State
Crashes in Tennessee
Statewide crash records.
Agency
EPES TRANSPORT SYSTEM LLC
Crashes reported by this law-enforcement agency.
Station
I-24
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.