Skip to main content
TruckCodex
Hubs

Crash Record AR2021503300

FMCSA crash record in LONDON on Jan 20, 2021.

Injury Federal Recordable

What happened

On January 20, 2021, FMCSA recorded an injury crash with one person hurt in LONDON, Arkansas. The vehicle was operated by TYSON FOODS INC (USDOT 3327). Recorded conditions: 1 / 1 / 1 pavement. Reported by TYSON, FMCSA reference AR2021503300.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
1
Carrier
TYSON FOODS INC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
196
4 fatal · 68 injury
Crashes per 100 power units (24 mo)
3.2
186 crashes · 5,861 units
Days since prior carrier crash
5
Last on Jan 15, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,853 carriers

Geographic context

How this crash sits in its setting.

Within LONDON, Arkansas, 14 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
1
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 #:
AR2021503300
Date:
Jan 20, 2021
Time:
1056
State:
Arkansas
City:
LONDON
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
1
Carrier (USDOT):
TYSON FOODS INC (3327)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 6 1M1AW07Y1FM047439 3AJ856 (OK) TYSON 3 No

Crash event

Event sequence description.

2:18:COLLISION INVOLVING FIXED OBJECT;1:1:NONCOLLISION:RAN OFF ROAD

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cmsw88s9d0091pev3dtc514nt Aug 10, 2026 AR Tow-Away 0 0
cmsw88sms00obpev39jyos6mz Aug 6, 2026 IA Tow-Away 0 0
cmrd638we000xp8pq9sa3xn0d Jul 3, 2026 NC Tow-Away 0 0
cmqkg784500bnp8fywd1dd1by Jun 11, 2026 AR Tow-Away 0 0
cmqkg78cj00k9p8fyh9ndc80e Jun 10, 2026 AR Injury 0 1
cmpqehz5m0039qiys2u9kquuw May 21, 2026 TN Tow-Away 0 0
cmo6itlnf00j3o1audlwnec1x Apr 8, 2026 AR Tow-Away 0 0
cmny3ygo800qtk38vecog8s4o Apr 3, 2026 AR Tow-Away 0 0
cr_5120795 Mar 14, 2026 TN Tow-Away 0 0
cr_5121039 Mar 12, 2026 OK 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.