Crash Record WA000EB83710

FMCSA crash record in WENATCHEE on Oct 25, 2021.

Tow-Away Federal Recordable

What happened

On October 25, 2021, FMCSA recorded a tow-away crash with no reported injuries in WENATCHEE, Washington. The vehicle was operated by BNSF RAILWAY COMPANY (USDOT 281683). Recorded conditions: 3 / 1 / 1 pavement. Reported by BNSF RAILWAY COMPANY, FMCSA reference WA000EB83710.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

BNSF RAILWAY COMPANY

USDOT 281683

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

5 injury · 19 tow-away

Crashes per 100 power units (24 mo)

0.6

18 crashes · 2,987 units

Days since prior carrier crash

Last on Oct 5, 2021

Vs fleet-size peers

above the median

Cohort median 0.0 · 3,867 carriers

Geographic context

How this crash sits in its setting.

Within WENATCHEE, Washington, 7 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: 3
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 #:: WA000EB83710
Date:: Oct 25, 2021
Time:: 0307
State:: Washington
City:: WENATCHEE
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: BNSF RAILWAY COMPANY (281683)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	5	98	1FVACXBS8CDBD4628	YASB049 (OR)	BNSF RAILWAY COMPANY	2	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
cmoxtyolt001xnu5lck2j2shw	May 4, 2026	OR	Tow-Away	0	0
cr_5127249	Mar 26, 2026	NE	Tow-Away	0	0
cr_5119901	Mar 10, 2026	NE	Injury	0	1
cr_5107660	Feb 3, 2026	TX	Tow-Away	0	0
cr_5076187	Dec 2, 2025	MO	Tow-Away	0	0
cr_5096699	Dec 1, 2025	IL	Tow-Away	0	0
cr_5095168	Nov 7, 2025	IL	Tow-Away	0	0
cr_5048915	Oct 27, 2025	OK	Tow-Away	0	0
cr_5022018	Aug 14, 2025	KS	Fatal	1	1
cr_4996611	Aug 13, 2025	IL	Injury	0	1

Carrier booking & risk tools

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

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

Related records

Carrier

BNSF RAILWAY COMPANY

USDOT 281683 · 357 crashes · 1,069 inspections

Safety

Carrier inspections

Roadside inspection history for this USDOT.

Vehicle

VIN: 1FVACXBS8CDBD4628

Decode this VIN for make, model, year, and recall data.

State

Crashes in Washington

Statewide crash records.

Agency

BNSF RAILWAY COMPANY

Crashes reported by this law-enforcement agency.

City

Crashes in WENATCHEE, 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.