Skip to main content
TruckCodex
Hubs

Crash Record SC0021290167

FMCSA crash record in SUMMERVILLE on Oct 26, 2021.

Tow-Away Federal Recordable

What happened

On October 26, 2021, FMCSA recorded a tow-away crash with no reported injuries in SUMMERVILLE, South Carolina. The vehicle was operated by CHRIS THOMPSON SERVICES LLC (USDOT 2207311). Recorded conditions: 2 / 1 / 1 pavement. Reported by CHRIS THOMPSON SERVICES LLC, FMCSA reference SC0021290167.

Geographic note

This crash is part of an active corridor: 178 crashes occurred in the same city in the past 24 months.

Fatalities
0
Injuries
0
Vehicles
2
Carrier
CHRIS THOMPSON SERVICES LLC
USDOT 2207311
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
2
0 injury · 2 tow-away
Crashes per 100 power units (24 mo)
0.0
0 crashes · 40 units
Days since prior carrier crash
107
Last on Jul 11, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 315,143 carriers

Geographic context

How this crash sits in its setting.

Within SUMMERVILLE, South Carolina, 178 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

Contributing factors

What the responding officer recorded.

Light
2
Weather
1
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 #:
SC0021290167
Date:
Oct 26, 2021
Time:
2237
State:
South Carolina
City:
SUMMERVILLE
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
CHRIS THOMPSON SERVICES LLC (2207311)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 7 10 1FUJGBDVXFLGA7166 P808382 (SC) CHRIS THOMPSON SERVICES LLC 3 No

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT;2:6:NONCOLLISION:EXPLOSION OR FIRE

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4326694 Mar 23, 2022 SC Tow-Away 0 0
cr_4204630 Jul 11, 2021 SC Tow-Away 0 0
cr_3747643 Feb 23, 2019 SC Injury 0 1
cr_3183913 Mar 7, 2016 SC Tow-Away 0 0
cr_3098073 Sep 14, 2015 SC Tow-Away 0 0
cr_3046514 May 26, 2015 SC Tow-Away 0 0
cr_3024300 Apr 7, 2015 SC Injury 0 1
cr_2867840 May 15, 2014 SC Tow-Away 0 0
cr_2624455 Nov 7, 2012 SC Injury 0 1
cr_2583525 Aug 9, 2012 SC Injury 0 3

Carrier booking & risk tools

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

Book / don't book Insurance check Cancel desk Chameleon check Safety benchmark

Related records

Vehicle
2015 FREIGHTLINER Cascadia
NHTSA recalls and complaints for this make/model/year.
Recall
20V214000
EXTERIOR LIGHTING
Recall
19V370000
SERVICE BRAKES, AIR:SUPPLY:RESERVOIR/TANK
Recall
19V093000
STEERING:LINKAGES:TIE ROD ASSEMBLY
Carrier
CHRIS THOMPSON SERVICES LLC
USDOT 2207311 · 11 crashes · 24 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 1FUJGBDVXFLGA7166
Decode this VIN for make, model, year, and recall data.
State
Crashes in South Carolina
Statewide crash records.
Agency
CHRIS THOMPSON SERVICES LLC
Crashes reported by this law-enforcement agency.
City
Crashes in SUMMERVILLE, SC
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.