Crash Record SD12300K0566

FMCSA crash record in South Dakota on Nov 8, 2000.

Tow-Away

What happened

On November 8, 2000, FMCSA recorded a tow-away crash with no reported injuries in South Dakota. The vehicle was operated by TIGER EXPRESS INC (USDOT 715987). FMCSA reference SD12300K0566.

Fatalities
0
Injuries
0
Vehicles
Carrier
TIGER EXPRESS INC
Vehicle Type
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
1
0 injury · 1 tow-away
Crashes per 100 power units (24 mo)
25.0
1 crashes · 4 units
Prior carrier crash
No earlier crash on file
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,562,959 carriers

Geographic context

How this crash sits in its setting.

Within South Dakota, 776 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 #:
SD12300K0566
Date:
Nov 8, 2000
Time:
0015
State:
South Dakota
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Carrier (USDOT):
TIGER EXPRESS INC (715987)

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4866898 Dec 27, 2024 NE Fatal 1 0
cr_4720099 Mar 22, 2024 IA Tow-Away 0 0
cr_4691022 Dec 22, 2023 SD Tow-Away 0 0
cr_4016065 Aug 17, 2020 NE Injury 0 1
cr_3816966 Jul 5, 2019 MO Injury 0 1
cr_3440250 Aug 1, 2017 MO Tow-Away 0 0
cr_3123539 Nov 19, 2015 IA Tow-Away 0 0
cr_2835280 Feb 20, 2014 NE Injury 0 1
cr_2708126 May 10, 2013 NE Tow-Away 0 0
cr_2679253 Nov 7, 2012 NE 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.