Crash Record TN0103306212

FMCSA crash record in FAYETTEVILLE on May 19, 2022.

Injury Federal Recordable

What happened

On May 19, 2022, FMCSA recorded an injury crash with one person hurt in FAYETTEVILLE, Tennessee. The vehicle was operated by S & S FIRESTONE INC (USDOT 271514). Recorded conditions: 1 / 1 pavement. Reported by S & S TIRE - PREMIER TRANSPORTATION NETWORK - BEST ONE TIRE & SERVICE - SSTRANS - PREMIER BANDAG, FMCSA reference TN0103306212.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

S & S FIRESTONE INC

Vehicle Type

Truck

Severity

Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

2 injury · 6 tow-away

Crashes per 100 power units (24 mo)

3.8

9 crashes · 240 units

Days since prior carrier crash

Last on May 11, 2022

Vs fleet-size peers

above the median

Cohort median 0.0 · 27,004 carriers

Geographic context

How this crash sits in its setting.

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

Agencies most active in this area:

BATESVILLE · 1 reports
CORTHELL TRANSPORTATION LLC · 1 reports
GRAHAM FARMS · 1 reports

Contributing factors

What the responding officer recorded.

Light: 1
Weather: —
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 #:: TN0103306212
Date:: May 19, 2022
Time:: 1108
State:: Tennessee
City:: FAYETTEVILLE
Fatalities:: 0
Injuries:: 1
Tow-Away:: No
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: S & S FIRESTONE INC (271514)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	5	3	1FVACWFC0KHKT0775	H470078 (TN)	S & S TIRE - PREMIER TRANSPORTATION NETWORK - BEST ONE TIRE & SERVICE - SSTRANS - PREMIER BANDAG	2	No

Crash event

Event sequence description.

1:8:NONCOLLISION:CROSS MEDIAN/CENTERLINE

Other crashes by this carrier

10 additional crash record(s) on file.

Record	Date	State	Severity	Injuries
cr_5114945	Mar 4, 2026	KY	Tow-Away	0
cr_5120069	Feb 24, 2026	AR	Tow-Away	0
cr_5030020	Sep 16, 2025	TN	Injury	1
cr_5026509	Aug 25, 2025	SC	Tow-Away	0
cr_4956148	Jun 11, 2025	AR	Injury	1
cr_4946074	May 15, 2025	WV	Injury	4
cr_4931158	Apr 22, 2025	TN	Tow-Away	0
cr_4851319	Nov 26, 2024	AL	Tow-Away	0
cr_4848945	Nov 22, 2024	KY	Tow-Away	0
cr_4768252	Jun 21, 2024	KY	Tow-Away	0

Related records

Carrier

S & S FIRESTONE INC

USDOT 271514 · 51 crashes · 577 inspections

Vehicle

VIN: 1FVACWFC0KHKT0775

Decode this VIN for make, model, year, and recall data.

State

Crashes in Tennessee

Statewide crash records.

Agency

S & S TIRE - PREMIER TRANSPORTATION NETWORK - BEST ONE TIRE & SERVICE - SSTRANS - PREMIER BANDAG

Crashes reported by this law-enforcement agency.

City

Crashes in FAYETTEVILLE, 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.