Skip to main content
TruckCodex
Hubs

Crash Record WA000EB37261

FMCSA crash record in NACHES on May 25, 2021.

Tow-Away Federal Recordable

What happened

On May 25, 2021, FMCSA recorded a tow-away crash with no reported injuries in NACHES, Washington. The vehicle was operated by WALSH TRUCKING CO LTD (USDOT 59492). Recorded conditions: 1 / 1 / 1 pavement. Reported by WALSH TRUCKING CO LTD, FMCSA reference WA000EB37261.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
3
Carrier
WALSH TRUCKING CO LTD
USDOT 59492
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
23
1 fatal · 3 injury
Crashes per 100 power units (24 mo)
5.8
20 crashes · 346 units
Days since prior carrier crash
7
Last on May 18, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 27,365 carriers

Geographic context

How this crash sits in its setting.

Within NACHES, Washington, 8 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 #:
WA000EB37261
Date:
May 25, 2021
Time:
1145
State:
Washington
City:
NACHES
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
3
Carrier (USDOT):
WALSH TRUCKING CO LTD (59492)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 7 3 1M1AW02Y7HM081394 YAIK137 (OR) WALSH TRUCKING CO LTD 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
cmvettq5n00n5ogssrcum9qz3 Oct 8, 2026 OR Tow-Away 0 0
cmsw88so300r9pev30o12ioea Aug 5, 2026 OR Fatal 2 0
cr_5115146 Mar 4, 2026 OR Tow-Away 0 0
cr_5083844 Dec 17, 2025 WA Tow-Away 0 0
cr_5061241 Nov 5, 2025 OR Injury 0 1
cr_5047413 Oct 21, 2025 OR Fatal 1 0
cr_5031720 Sep 17, 2025 OR Tow-Away 0 0
cr_5006640 Aug 1, 2025 OR Tow-Away 0 0
cr_5006716 Jul 1, 2025 OR Tow-Away 0 0
cr_5006694 Jun 9, 2025 OR Tow-Away 0 0

Carrier booking & risk tools

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

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

Related records

Vehicle
2017 MACK CXU (Pinnacle)
NHTSA recalls and complaints for this make/model/year.
Carrier
WALSH TRUCKING CO LTD
USDOT 59492 · 395 crashes · 183 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 1M1AW02Y7HM081394
Decode this VIN for make, model, year, and recall data.
State
Crashes in Washington
Statewide crash records.
Agency
WALSH TRUCKING CO LTD
Crashes reported by this law-enforcement agency.
City
Crashes in NACHES, 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.