TruckCodex
Hubs

Crash Record WA000EB12540

FMCSA crash record in SPOKANE on Feb 25, 2021.

Injury Federal Recordable

What happened

On February 25, 2021, FMCSA recorded an injury crash with one person hurt in SPOKANE, Washington. The vehicle was operated by USF REDDAWAY INC (USDOT 2436459). Recorded conditions: 1 / 4 / 4 pavement. Reported by USF REDDAWAY INC, FMCSA reference WA000EB12540.

Geographic note

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

Fatalities
0
Injuries
1
Vehicles
4
Carrier
USF REDDAWAY INC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
34
9 injury · 34 tow-away
Days since prior carrier crash
1
Last on Feb 24, 2021

Geographic context

How this crash sits in its setting.

Within SPOKANE, Washington, 102 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
4
Road surface
4

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 #:
WA000EB12540
Date:
Feb 25, 2021
Time:
0820
State:
Washington
City:
SPOKANE
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
4
Carrier (USDOT):
USF REDDAWAY INC (2436459)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 10 3 2HSCPAPN46C225627 2659847 (IN) USF REDDAWAY INC 3 Yes

Crash event

Event sequence description.

4:20:COLLISION INVOLVING OTHER MOVABLE OBJECT;3:20:COLLISION INVOLVING OTHER MOVABLE OBJECT;1:1:NONCOLLISION:RAN OFF ROAD;2:20:COLLISION INVOLVING OTHER MOVABLE OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4488536 Dec 27, 2022 ID Tow-Away 0 0
cr_4482286 Dec 22, 2022 WA Tow-Away 0 0
cr_4500399 Dec 14, 2022 CO Tow-Away 0 0
cr_4431335 Oct 4, 2022 MT Tow-Away 0 0
cr_4421018 Sep 10, 2022 WA Tow-Away 0 0
cr_4427825 Aug 12, 2022 OR Tow-Away 0 0
cr_4374358 Jun 9, 2022 WA Tow-Away 0 0
cr_4363176 Apr 26, 2022 OR Tow-Away 0 0
cr_4332168 Apr 6, 2022 AZ Injury 0 1
cr_4330076 Mar 30, 2022 WA Tow-Away 0 0

Related records

Vehicle
2006 INTERNATIONAL 9400i
NHTSA recalls and complaints for this make/model/year.
Recall
23V353000
EXTERIOR LIGHTING:BACK UP LIGHTS
Recall
09V386000
ENGINE AND ENGINE COOLING
Recall
06V077000
ENGINE AND ENGINE COOLING:COOLING SYSTEM:HOSES/LINES/PIPING/FITTINGS
Carrier
USF REDDAWAY INC
USDOT 2436459 · 66 crashes · 0 inspections
Vehicle
VIN: 2HSCPAPN46C225627
Decode this VIN for make, model, year, and recall data.
State
Crashes in Washington
Statewide crash records.
Agency
USF REDDAWAY INC
Crashes reported by this law-enforcement agency.
City
Crashes in SPOKANE, 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.