Skip to main content
TruckCodex
Hubs

Crash Record UT2105406776

FMCSA crash record in WEST VALLEY CITY on Jul 26, 2021.

Fatal Federal Recordable

What happened

On July 26, 2021, FMCSA recorded a fatal crash that resulted in one death in WEST VALLEY CITY, Utah. The vehicle was operated by RANDY MARRIOTT CONSTRUCTION (USDOT 748758). Recorded conditions: 1 / 1 / 9 pavement. FMCSA reference UT2105406776.

Carrier pattern note

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

Geographic note

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

Fatalities
1
Injuries
2
Vehicles
4
Carrier
RANDY MARRIOTT CONSTRUCTION
USDOT 748758
Vehicle Type
Truck
Severity
Fatal

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
4
1 fatal · 3 injury
Crashes per 100 power units (24 mo)
0.0
0 crashes · 10 units
Days since prior carrier crash
172
Last on Feb 4, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 314,932 carriers

Geographic context

How this crash sits in its setting.

Within WEST VALLEY CITY, Utah, 31 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
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 #:
UT2105406776
Date:
Jul 26, 2021
Time:
1302
State:
Utah
City:
WEST VALLEY CITY
Fatalities:
1
Injuries:
2
Tow-Away:
Yes
HazMat:
No
Vehicles:
4
Carrier (USDOT):
RANDY MARRIOTT CONSTRUCTION (748758)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
3 6 6 1NKWX4TX0DR340383 Z036235 (UT) RANDY MARRIOTT CONSTRUCTION 3 No

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT;2:13:COLLISION INVOLVING MOTOR VEHICLE IN TRANSPORT

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4123459 Feb 4, 2021 UT Injury 0 1
cr_4114977 Jan 6, 2021 UT Tow-Away 0 0
cr_4069124 Oct 16, 2020 UT Injury 0 2
cr_3622751 Apr 18, 2018 UT Tow-Away 0 0
cr_1633870 Mar 28, 2006 UT Tow-Away 0 0
cr_1218934 Nov 14, 2003 UT Tow-Away 0 0
cr_301177 Jun 28, 2001 UT Injury 0 4
cr_164810 May 4, 2000 UT Injury 0 5
cr_171967 Aug 11, 1998 UT Injury 0 2
cr_171586 May 14, 1998 UT Tow-Away 0 0

Carrier booking & risk tools

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

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

Related records

Vehicle
2013 KENWORTH W9 Series
NHTSA recalls and complaints for this make/model/year.
Carrier
RANDY MARRIOTT CONSTRUCTION
USDOT 748758 · 11 crashes · 12 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 1NKWX4TX0DR340383
Decode this VIN for make, model, year, and recall data.
State
Crashes in Utah
Statewide crash records.
City
Crashes in WEST VALLEY CITY, 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.