Skip to main content
TruckCodex
Hubs

Crash Record AL0001608223

FMCSA crash record in RURAL LEE on Jan 25, 2021.

Injury Federal Recordable

What happened

On January 25, 2021, FMCSA recorded an injury crash with one person hurt in RURAL LEE, Alabama. The vehicle was operated by SWIFT TRANSPORTATION COMPANY OF ARIZONA LLC (USDOT 54283). Recorded conditions: 3 / 1 / 2 pavement. Reported by SWIFT TRANSPORTATION CO OF ARIZONA LLC, FMCSA reference AL0001608223.

Carrier pattern note

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

Geographic note

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

Fatalities
0
Injuries
1
Vehicles
3
Carrier
SWIFT TRANSPORTATION COMPANY OF ARIZONA LLC
USDOT 54283
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
1,342
42 fatal · 366 injury
Crashes per 100 power units (24 mo)
4.4
563 crashes · 12,940 units
Days since prior carrier crash
2
Last on Jan 23, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,888 carriers

Geographic context

How this crash sits in its setting.

Within RURAL LEE, Alabama, 55 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
3
Weather
1
Road surface
2

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 #:
AL0001608223
Date:
Jan 25, 2021
Time:
0615
State:
Alabama
City:
RURAL LEE
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
3
Carrier (USDOT):
SWIFT TRANSPORTATION COMPANY OF ARIZONA LLC (54283)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 8 12 3AKJHHDR5LSLP8660 2532955 (IN) SWIFT TRANSPORTATION CO OF ARIZONA 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
cmvxr8j26003fo30enyldsysb Oct 26, 2026 PA Tow-Away 0 0
cmvuo5tbl002fo3dx1fwwewtk Oct 24, 2026 WI Injury 0 1
cmvotteqc001fo3rblibvpemj Oct 22, 2026 TN Injury 0 1
cmvj4mhi8002lo3kftz9q2pzd Oct 15, 2026 OH Tow-Away 0 0
cmup2ni5f007xl4z8d8tdmbbu Sep 22, 2026 KY Tow-Away 0 0
cmsw88s9h009dpev31o6cbe3d Aug 9, 2026 AZ Injury 0 1
cmsw88smn00nxpev32sh2b3ha Aug 6, 2026 WY Tow-Away 0 0
cmsipo3qo0005pef3myn0a8jv Aug 2, 2026 OK Tow-Away 0 0
cms76vgs80037pehvpzfszle2 Jul 23, 2026 NC Injury 0 1
cmrx2ea52001tpequnrnzqgvp Jul 16, 2026 NC Injury 0 3

Carrier booking & risk tools

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

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

Related records

Carrier
SWIFT TRANSPORTATION COMPANY OF ARIZONA LLC
USDOT 54283 · 23,618 crashes · 38,300 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 3AKJHHDR5LSLP8660
Decode this VIN for make, model, year, and recall data.
State
Crashes in Alabama
Statewide crash records.
Agency
SWIFT TRANSPORTATION CO OF ARIZONA LLC
Crashes reported by this law-enforcement agency.
City
Crashes in RURAL LEE, AL
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.