TruckCodex
Hubs

Crash Record WA000EC66612

FMCSA crash record in MOSES LAKE on Jul 20, 2022.

Injury Federal Recordable

What happened

On July 20, 2022, FMCSA recorded an injury crash with one person hurt in MOSES LAKE, Washington. The vehicle was operated by CRST EXPEDITED INC (USDOT 53773). Recorded conditions: 1 / 1 / 1 pavement. Reported by CRST THE TRANSPORTATION SOLUTION INC, FMCSA reference WA000EC66612.

Carrier pattern note

This is the carrier's 459 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: 32 crashes occurred in the same city in the past 24 months.

Fatalities
0
Injuries
1
Vehicles
2
Carrier
CRST EXPEDITED INC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
459
12 fatal · 147 injury
Crashes per 100 power units (24 mo)
3.7
163 crashes · 4,362 units
Days since prior carrier crash
3
Last on Jul 17, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,837 carriers

Geographic context

How this crash sits in its setting.

Within MOSES LAKE, Washington, 32 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 #:
WA000EC66612
Date:
Jul 20, 2022
Time:
1926
State:
Washington
City:
MOSES LAKE
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
CRST EXPEDITED INC (53773)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 98 3AKNGLDR4KDJW1742 2670159 (IN) CRST THE TRANSPORTATION SOLUTION INC 3 No

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cmoz9e2gp004tnufy3s6jw0lq May 5, 2026 AZ Injury 0 1
cr_5123667 Feb 21, 2026 TX Tow-Away 0 0
cr_5110739 Feb 20, 2026 IA Tow-Away 0 0
cr_5123284 Feb 17, 2026 CA Injury 0 1
cr_5110844 Feb 6, 2026 IN Injury 0 2
cr_5109152 Feb 5, 2026 TX Tow-Away 0 0
cr_5109105 Feb 5, 2026 TX Tow-Away 0 0
cr_5106473 Jan 28, 2026 TX Tow-Away 0 0
cr_5121624 Jan 26, 2026 CA Injury 0 2
cr_5113451 Jan 19, 2026 PA Tow-Away 0 0

Related records

Vehicle
2019 FREIGHTLINER Cascadia
NHTSA recalls and complaints for this make/model/year.
Recall
23V105000
STEERING:LINKAGES:DRAG:LINK:CONNECTION
Recall
23V073000
ELECTRONIC STABILITY CONTROL (ESC)
Recall
22V919000
TIRES
Carrier
CRST EXPEDITED INC
USDOT 53773 · 4,955 crashes · 9,715 inspections
Vehicle
VIN: 3AKNGLDR4KDJW1742
Decode this VIN for make, model, year, and recall data.
State
Crashes in Washington
Statewide crash records.
Agency
CRST THE TRANSPORTATION SOLUTION INC
Crashes reported by this law-enforcement agency.
City
Crashes in MOSES LAKE, WA
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.