Skip to main content
TruckCodex
Hubs

Crash Record UT2206003196

FMCSA crash record in HEBER on Aug 26, 2022.

Injury Federal Recordable

What happened

On August 26, 2022, FMCSA recorded an injury crash with one person hurt in HEBER, Utah. The vehicle was operated by PILOT TRAVEL CENTERS LLC (USDOT 91805). Recorded conditions: 2 / 1 / 9 pavement. Reported by SARATOGA, FMCSA reference UT2206003196.

Carrier pattern note

This is the carrier's 151 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
PILOT TRAVEL CENTERS LLC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
151
6 fatal · 59 injury
Crashes per 100 power units (24 mo)
7.3
94 crashes · 1,279 units
Days since prior carrier crash
1
Last on Aug 25, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,855 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
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 #:
UT2206003196
Date:
Aug 26, 2022
Time:
0333
State:
Utah
City:
HEBER
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
1

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 4 1NKZX4EX9JJ205536 H0818HY (TN) SARATOGA 3 No

Crash event

Event sequence description.

3:17:COLLISION INVOLVING ANIMAL;1:19:COLLISION WITH WORK ZONE MAINTENANCE EQUIPMENT;2:6:NONCOLLISION:EXPLOSION OR FIRE

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cmqt2c387002fp84g4x0i42xa Jun 17, 2026 VA Tow-Away 0 0
cmpoujjv3004lr2048vc15j1e May 20, 2026 NC Tow-Away 0 0
cmouyr2u40065nu1klf04gm53 Apr 29, 2026 KY Tow-Away 0 0
cmodru16y0055nvfd9i54z0at Apr 19, 2026 TN Injury 0 3
cr_5127134 Mar 27, 2026 IA Tow-Away 0 0
cr_5125414 Mar 17, 2026 TX Tow-Away 0 0
cr_5123578 Mar 14, 2026 PA Tow-Away 0 0
cr_5124947 Mar 14, 2026 TX Tow-Away 0 0
cr_5116621 Mar 11, 2026 TN Tow-Away 0 0
cr_5121469 Feb 22, 2026 GA 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.