Crash Record TN0300113740

FMCSA crash record in Tennessee on Mar 5, 2013.

Injury

What happened

On March 5, 2013, FMCSA recorded an injury crash with one person hurt in Tennessee. The vehicle was operated by SILICA TRANSPORT INC (USDOT 11284). FMCSA reference TN0300113740.

Fatalities
0
Injuries
1
Vehicles
Carrier
SILICA TRANSPORT INC
Vehicle Type
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
3
1 injury · 2 tow-away
Crashes per 100 power units (24 mo)
9.1
4 crashes · 44 units
Days since prior carrier crash
83
Last on Dec 12, 2012
Vs fleet-size peers
above the median
Cohort median 0.0 · 312,259 carriers

Geographic context

How this crash sits in its setting.

Within Tennessee, 7,512 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 #:
TN0300113740
Date:
Mar 5, 2013
Time:
1312
State:
Tennessee
Fatalities:
0
Injuries:
1
Tow-Away:
No
HazMat:
No
Carrier (USDOT):
SILICA TRANSPORT INC (11284)

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4915537 Mar 14, 2025 AR Injury 0 1
cr_4910319 Mar 10, 2025 OK Tow-Away 0 0
cr_4832117 Oct 21, 2024 MS Tow-Away 0 0
cr_4807543 Sep 13, 2024 TN Tow-Away 0 0
cr_4792397 Aug 1, 2024 AR Fatal 1 0
cr_4753745 May 28, 2024 AR Tow-Away 0 0
cr_4673940 Dec 26, 2023 TN Injury 0 1
cr_4652504 Nov 6, 2023 OK Tow-Away 0 0
cr_4070391 Dec 1, 2020 TN Tow-Away 0 0
cr_4078888 Nov 30, 2020 MS 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.