Crash Record OH0235084816

FMCSA crash record in AMBOY (TOWNSHIP OF) on May 15, 2023.

Tow-Away Federal Recordable

What happened

On May 15, 2023, FMCSA recorded a tow-away crash with no reported injuries in AMBOY (TOWNSHIP OF), Ohio. The vehicle was operated by TRADITION TRANSPORTATION COMPANY LLC (USDOT 247552). Recorded conditions: 1 / 1 / 1 pavement. FMCSA reference OH0235084816.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

TRADITION TRANSPORTATION COMPANY LLC

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

2 fatal · 2 injury

Crashes per 100 power units (24 mo)

0.0

0 crashes · 166 units

Days since prior carrier crash

Last on May 9, 2023

Vs fleet-size peers

above the median

Cohort median 0.0 · 26,697 carriers

Geographic context

How this crash sits in its setting.

Within AMBOY (TOWNSHIP OF), Ohio, 7 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

EVERGREEN LOCAL SCHOOL DISTRICT · 1 reports
MCMUNN TRANSPORT LLC · 1 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 #:: OH0235084816
Date:: May 15, 2023
Time:: 0750
State:: Ohio
City:: AMBOY (TOWNSHIP OF)
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: TRADITION TRANSPORTATION COMPANY LLC (247552)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
2	9	3	3AKJGBDV4HSHR4559	3037588 (IN)	TRADITION TRANSPORTATION COMPANY	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_4740904	Apr 8, 2024	MI	Tow-Away	0	0
cr_4710349	Feb 20, 2024	NC	Tow-Away	0	0
cr_4694966	Jan 16, 2024	IN	Tow-Away	0	0
cr_4697852	Jan 16, 2024	PA	Fatal	5	1
cr_4658739	Nov 17, 2023	MO	Tow-Away	0	0
cr_4621156	Sep 11, 2023	OH	Injury	0	1
cr_4659495	Aug 17, 2023	IL	Injury	0	1
cr_4586458	Jul 6, 2023	OH	Tow-Away	0	0
cr_4557750	May 9, 2023	IN	Tow-Away	0	0
cr_4514376	Feb 22, 2023	KY	Tow-Away	0	0

Related records

Vehicle

2017 FREIGHTLINER Cascadia

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

Recall

23V073000

ELECTRONIC STABILITY CONTROL (ESC)

Recall

22V817000

FORWARD COLLISION AVOIDANCE: ADAPTIVE CRUISE CONTROL

Recall

20V567000

EXTERIOR LIGHTING:BRAKE LIGHTS

Carrier

TRADITION TRANSPORTATION COMPANY LLC

USDOT 247552 · 248 crashes · 0 inspections

Vehicle

VIN: 3AKJGBDV4HSHR4559

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

State

Crashes in Ohio

Statewide crash records.

City

Crashes in AMBOY (TOWNSHIP OF), 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.