Skip to main content
TruckCodex
Hubs

Crash Record UT2208423376

FMCSA crash record in HEBER on Dec 21, 2022.

Tow-Away Federal Recordable

What happened

On December 21, 2022, FMCSA recorded a tow-away crash with no reported injuries in HEBER, Utah. The vehicle was operated by SWIFT TRANSPORTATION COMPANY OF ARIZONA LLC (USDOT 54283). Recorded conditions: 2 / 6 / 9 pavement. Reported by SWIFT TRANSPORTATION CO OF ARIZONA LLC, FMCSA reference UT2208423376.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
1
Carrier
SWIFT TRANSPORTATION COMPANY OF ARIZONA LLC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
1,117
38 fatal · 320 injury
Crashes per 100 power units (24 mo)
4.6
595 crashes · 12,940 units
Days since prior carrier crash
1
Last on Dec 20, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,858 carriers

Geographic context

How this crash sits in its setting.

Within HEBER, Utah, 12 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
6
Road surface
9

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 #:
UT2208423376
Date:
Dec 21, 2022
Time:
2202
State:
Utah
City:
HEBER
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
1
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 9 3 3AKJHHDRXNSNA2646 3161817 (IN) SWIFT TRANSPORTATION CO OF ARIZONA LLC 3 No

Crash event

Event sequence description.

3:18:COLLISION INVOLVING FIXED OBJECT;1:6:NONCOLLISION:EXPLOSION OR FIRE;2:18:COLLISION INVOLVING FIXED OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
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
cmrrbu55a005hpebf4csfm2sz Jul 13, 2026 NJ Injury 0 1
cmrn1fcc0007vpez5e22v1hyc Jul 8, 2026 IA Tow-Away 0 0
cmrd638yj0011p8pq7huct9ay Jul 4, 2026 GA Injury 0 1
cmqxb77ce0069p8f0vlotdce9 Jun 22, 2026 AR Tow-Away 0 0
cmq1vv02s003hpbjqlgbhqsvb May 31, 2026 KY Tow-Away 0 0

Related records

Carrier
SWIFT TRANSPORTATION COMPANY OF ARIZONA LLC
USDOT 54283 · 23,613 crashes · 37,454 inspections
Vehicle
VIN: 3AKJHHDRXNSNA2646
Decode this VIN for make, model, year, and recall data.
State
Crashes in Utah
Statewide crash records.
Agency
SWIFT TRANSPORTATION CO OF ARIZONA LLC
Crashes reported by this law-enforcement agency.
City
Crashes in HEBER, UT
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.