Crash Record TN0009938040

FMCSA crash record in Tennessee on Sep 3, 2009.

Injury

What happened

On September 3, 2009, FMCSA recorded an injury crash with one person hurt in Tennessee. The vehicle was operated by MAINSTREAM TRANSPORTATION INC (USDOT 391543). FMCSA reference TN0009938040.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
Carrier
MAINSTREAM TRANSPORTATION INC
Vehicle Type
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
9
3 injury · 9 tow-away
Crashes per 100 power units (24 mo)
3.2
2 crashes · 62 units
Days since prior carrier crash
28
Last on Aug 6, 2009
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,632 carriers

Geographic context

How this crash sits in its setting.

Within Tennessee, 7,491 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

Crash details

Key facts from the FMCSA crash record.

Report #:
TN0009938040
Date:
Sep 3, 2009
Time:
1845
State:
Tennessee
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5050821 Oct 30, 2025 TN Tow-Away 0 0
cr_5023088 Sep 5, 2025 AR Injury 0 1
cr_4734488 Apr 19, 2024 TN Fatal 1 0
cr_4655713 Nov 21, 2023 AR Tow-Away 0 0
cr_4344565 Mar 17, 2022 MS Tow-Away 0 0
cr_4208643 Aug 3, 2021 MS Tow-Away 0 0
cr_4224145 Jul 28, 2021 GA Injury 0 1
cr_4021913 Dec 12, 2018 AR Tow-Away 0 0
cr_3685469 Nov 6, 2018 AR Injury 0 2
cr_3653908 Jun 12, 2018 AL Tow-Away 0 0

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.