Crash Record OR2023030013

FMCSA crash record in HILLSBORO on Feb 19, 2023.

Tow-Away Federal Recordable

What happened

On February 19, 2023, FMCSA recorded a tow-away crash with no reported injuries in HILLSBORO, Oregon. The vehicle was operated by U-HAUL COMPANY OF OREGON (USDOT 428553). Recorded conditions: 1 / 1 / 1 pavement. Reported by U-HAUL AND U BOX OF OREGON, FMCSA reference OR2023030013.

Geographic note

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

Fatalities

Injuries

Vehicles

Carrier

U-HAUL COMPANY OF OREGON

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

0 injury · 2 tow-away

Crashes per 100 power units (24 mo)

0.0

0 crashes · 35 units

Days since prior carrier crash

205

Last on Jul 29, 2022

Vs fleet-size peers

above the median

Cohort median 0.0 · 314,932 carriers

Geographic context

How this crash sits in its setting.

Within HILLSBORO, Oregon, 38 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

HILLSBORO SCHOOL DISTRICT #1J · 6 reports
HILLSBORO GARBAGE DISPOSAL INC · 2 reports
BEAVERTON SCHOOL DISTRICT · 2 reports

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 #:: OR2023030013
Date:: Feb 19, 2023
Time:: 1039
State:: Oregon
City:: HILLSBORO
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: U-HAUL COMPANY OF OREGON (428553)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	7	5	3AKBCYCY6HDJH1617	YARW595 (OR)	U-HAUL AND U BOX OF OREGON	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	Injuries
cr_4417055	Jul 29, 2022	OR	Tow-Away	0
cr_3370788	Jan 24, 2017	OR	Tow-Away	0
cr_3260551	Aug 12, 2016	OR	Tow-Away	0
cr_3221491	May 4, 2016	OR	Tow-Away	0
cr_2574901	Apr 1, 2012	OR	Tow-Away	0
cr_218597	Dec 31, 1994	WI	Injury	2
cr_68888	Apr 19, 1993	TX	Tow-Away	0
cr_213244	Nov 8, 1992	WI	Injury	3
cr_161535	Aug 3, 1992	UT	Property Damage	0
cr_570484	Oct 15, 1990	ID	Injury	1

Carrier booking & risk tools

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

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

Related records

Vehicle

2017 FREIGHTLINER M2

NHTSA recalls and complaints for this make/model/year.

SERVICE BRAKES, AIR:SUPPLY:RESERVOIR/TANK

Carrier

U-HAUL COMPANY OF OREGON

USDOT 428553 · 11 crashes · 14 inspections

Safety

Carrier inspections

Roadside inspection history for this USDOT.

Vehicle

VIN: 3AKBCYCY6HDJH1617

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

State

Crashes in Oregon

Statewide crash records.

Agency

U-HAUL AND U BOX OF OREGON

Crashes reported by this law-enforcement agency.

City

Crashes in HILLSBORO, OR

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.