Crash Record OH0253239819

FMCSA crash record in TOLEDO on Dec 9, 2025.

Tow-Away Federal Recordable

What happened

On December 9, 2025, FMCSA recorded a tow-away crash with no reported injuries in TOLEDO, Ohio. The vehicle was operated by ANNETT HOLDINGS INC (USDOT 87409). Recorded conditions: 1 / 4 / 4 pavement. Reported by ANNETT HOLDINGS INC, FMCSA reference OH0253239819.

Carrier pattern note

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

Geographic note

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

Fatalities

Injuries

Vehicles

Carrier

ANNETT HOLDINGS INC

USDOT 87409

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

331

10 fatal · 114 injury

Crashes per 100 power units (24 mo)

3.5

251 crashes · 7,115 units

Days since prior carrier crash

Last on Dec 8, 2025

Vs fleet-size peers

above the median

Cohort median 0.0 · 3,878 carriers

Geographic context

How this crash sits in its setting.

Within TOLEDO, Ohio, 193 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

UNKNOWN · 7 reports
TARTA · 3 reports
TOLEDO AREA REGIONAL TRANSIT AUTHORITY · 2 reports

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 #:: OH0253239819
Date:: Dec 9, 2025
Time:: 0924
State:: Ohio
City:: TOLEDO
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: ANNETT HOLDINGS INC (87409)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	9	12	1XPBDP9X9ND770105	FP9972 (IA)	ANNETT HOLDINGS 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	Injuries
cmpqehz8l005jqiysz92n8jfz	May 21, 2026	NC	Injury	2
cmoxtyomi003dnu5lcg77crbv	May 3, 2026	KY	Tow-Away	0
cmo6itkzx0013o1aus0dzfxg8	Apr 15, 2026	TN	Tow-Away	0
cmny3yfpz003mk38vueis3brb	Apr 6, 2026	TN	Tow-Away	0
cmny3ygoh00qzk38vbie7v3d4	Apr 3, 2026	IA	Tow-Away	0
cr_5124737	Mar 20, 2026	MO	Injury	1
cr_5127711	Mar 18, 2026	MO	Tow-Away	0
cr_5123637	Mar 18, 2026	TN	Tow-Away	0
cr_5124328	Mar 13, 2026	GA	Injury	1
cr_5123655	Mar 11, 2026	TX	Injury	1

Carrier booking & risk tools

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

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

Related records

Vehicle

2022 PETERBILT 579

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

POWER TRAIN:AUTOMATIC TRANSMISSION:LEVER AND LINKAGE:COLUMN SHIFT

Carrier

ANNETT HOLDINGS INC

USDOT 87409 · 3,291 crashes · 10,375 inspections

Safety

Carrier inspections

Roadside inspection history for this USDOT.

Vehicle

VIN: 1XPBDP9X9ND770105

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

State

Crashes in Ohio

Statewide crash records.

Agency

ANNETT HOLDINGS INC

Crashes reported by this law-enforcement agency.

City

Crashes in TOLEDO, OH

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.