Crash Record TX245457101L

FMCSA crash record in Texas on Feb 28, 2008.

Tow-Away

What happened

On February 28, 2008, FMCSA recorded a tow-away crash with no reported injuries in Texas. The vehicle was operated by FRIEND TIRE COMPANY (USDOT 70376). FMCSA reference TX245457101L.

Fatalities
0
Injuries
0
Vehicles
Carrier
FRIEND TIRE COMPANY
Vehicle Type
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
3
2 fatal · 0 injury
Crashes per 100 power units (24 mo)
0.0
0 crashes · 105 units
Days since prior carrier crash
393
Last on Jan 31, 2007
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,602 carriers

Geographic context

How this crash sits in its setting.

Within Texas, 31,183 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 #:
TX245457101L
Date:
Feb 28, 2008
Time:
1229
State:
Texas
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Carrier (USDOT):
FRIEND TIRE COMPANY (70376)

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4672080 Oct 24, 2023 OK Tow-Away 0 0
cr_4468549 Nov 18, 2022 FL Injury 0 2
cr_4420562 Sep 2, 2022 TX Tow-Away 0 0
cr_4320447 Mar 16, 2022 AL Tow-Away 0 0
cr_4289252 Jan 5, 2022 LA Tow-Away 0 0
cr_4278417 Dec 23, 2021 MO Tow-Away 0 0
cr_4096098 Dec 21, 2020 MS Tow-Away 0 0
cr_4086196 Nov 6, 2020 IA Tow-Away 0 0
cr_4025693 Aug 26, 2020 OK Tow-Away 0 0
cr_3979214 May 12, 2020 MO Injury 0 1

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.