Skip to main content
TruckCodex
Hubs

Crash Record TN0300140229

FMCSA crash record in Tennessee on Sep 26, 2013.

Injury

What happened

On September 26, 2013, FMCSA recorded an injury crash with one person hurt in Tennessee. The vehicle was operated by HOLLADAY FARMS LLC (USDOT 786093). FMCSA reference TN0300140229.

Fatalities
0
Injuries
1
Vehicles
—
Carrier
USDOT 786093
Vehicle Type
—
Severity
Injury

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 · 3 units
Days since prior carrier crash
528
Last on Apr 16, 2012
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,585,072 carriers

Geographic context

How this crash sits in its setting.

Within Tennessee, 6,717 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 #:
TN0300140229
Date:
Sep 26, 2013
Time:
0800
State:
Tennessee
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Carrier (USDOT):
HOLLADAY FARMS LLC (786093)

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4345181 Apr 14, 2022 AL Tow-Away 0 0
cr_4322861 Mar 17, 2022 TN Tow-Away 0 0
cr_4304585 Feb 3, 2022 TX Injury 0 1
cr_4271520 Oct 29, 2021 MS Injury 0 1
cr_3684565 Oct 19, 2018 MS Injury 0 1
cr_2996876 Jan 15, 2015 KS Tow-Away 0 0
cr_2552783 Apr 16, 2012 OK Tow-Away 0 0
cr_2475915 Jun 4, 2011 KS Tow-Away 0 0
cr_2180681 Oct 22, 2009 OK Tow-Away 0 0
cr_1989810 May 4, 2008 TX Tow-Away 0 0

Carrier booking & risk tools

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

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.