Skip to main content
TruckCodex
Hubs

Crash Record WA000EC23502

FMCSA crash record in KENT on Feb 24, 2022.

Tow-Away Federal Recordable

What happened

On February 24, 2022, FMCSA recorded a tow-away crash with no reported injuries in KENT, Washington. The vehicle was operated by RUSTY BRADEEN TRUCKING INC (USDOT 494089). Recorded conditions: 3 / 4 / 4 pavement. Reported by RUSTY BRADEEN TRUCKING INC, FMCSA reference WA000EC23502.

Geographic note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
USDOT 494089
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
3
0 injury · 3 tow-away
Crashes per 100 power units (24 mo)
0.0
0 crashes · 13 units
Days since prior carrier crash
412
Last on Jan 8, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 315,794 carriers

Geographic context

How this crash sits in its setting.

Within KENT, Washington, 86 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
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 #:
WA000EC23502
Date:
Feb 24, 2022
Time:
0346
State:
Washington
City:
KENT
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 98 1XKWP49X7HR160577 61071RP (WA) RUSTY BRADEEN TRUCKING 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
cr_4653708 Nov 3, 2023 WA Injury 0 1
cr_4125272 Jan 8, 2021 WA Tow-Away 0 0
cr_3948744 Mar 16, 2020 WA Tow-Away 0 0
cr_3381754 Apr 7, 2017 WA Tow-Away 0 0
cr_3223098 Jun 3, 2016 WA Tow-Away 0 0
cr_2847453 Apr 7, 2014 WA Tow-Away 0 0
cr_2038585 Oct 17, 2008 OR Tow-Away 0 0
cr_2079140 Oct 13, 2008 WA Tow-Away 0 0
cr_1954886 Mar 27, 2008 WA Tow-Away 0 0
cr_1766170 Feb 13, 2007 WA Tow-Away 0 0

Carrier booking & risk tools

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

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.