Crash Record AR2020527922

FMCSA crash record in Arkansas on Jun 16, 2020.

Injury

What happened

On June 16, 2020, FMCSA recorded an injury crash with one person hurt in Arkansas. The vehicle was operated by SUMMIT TRUCKING INC (USDOT 843546). FMCSA reference AR2020527922.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
Carrier
SUMMIT TRUCKING INC
Vehicle Type
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
19
6 injury · 18 tow-away
Crashes per 100 power units (24 mo)
4.3
6 crashes · 140 units
Days since prior carrier crash
33
Last on May 14, 2020
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,833 carriers

Geographic context

How this crash sits in its setting.

Within Arkansas, 4,630 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 #:
AR2020527922
Date:
Jun 16, 2020
Time:
0914
State:
Arkansas
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Carrier (USDOT):
SUMMIT TRUCKING INC (843546)

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cmp7tlui4002znu0xpc597t4u May 11, 2026 OK Tow-Away 0 0
cr_5036507 Sep 18, 2025 TX Injury 0 1
cr_4996690 Aug 14, 2025 IL Tow-Away 0 0
cr_4951318 May 26, 2025 TX Injury 0 1
cr_4901164 Feb 25, 2025 TX Injury 0 2
cr_4816881 Sep 26, 2024 IA Tow-Away 0 0
cr_4813298 Sep 14, 2024 TX Injury 0 1
cr_4790314 Jul 23, 2024 TX Fatal 1 0
cr_4700954 Feb 19, 2024 TN Injury 0 1
cr_4622670 Aug 30, 2023 TX Tow-Away 0 0

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.