TruckCodex
Hubs

Crash Record OH0235116947

FMCSA crash record in WASHINGTON (TOWNSHIP OF) on Jul 6, 2023.

Tow-Away Federal Recordable

What happened

On July 6, 2023, FMCSA recorded a tow-away crash with no reported injuries in WASHINGTON (TOWNSHIP OF), Ohio. The vehicle was operated by TRADITION TRANSPORTATION COMPANY LLC (USDOT 247552). Recorded conditions: 1 / 1 / 1 pavement. Reported by TRADITION TRANSPORT CO LLC, FMCSA reference OH0235116947.

Carrier pattern note

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

Geographic note

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

Fatalities
0
Injuries
0
Vehicles
2
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)
19
2 fatal · 2 injury
Crashes per 100 power units (24 mo)
0.0
0 crashes · 166 units
Days since prior carrier crash
52
Last on May 15, 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 WASHINGTON (TOWNSHIP OF), Ohio, 189 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
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 #:
OH0235116947
Date:
Jul 6, 2023
Time:
1836
State:
Ohio
City:
WASHINGTON (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
1 9 3 3AKJHHDR8KSKN9340 2754876 (IN) TRADITION TRANSPORT CO LLC 3 No

Crash event

Event sequence description.

1:5:NONCOLLISION:CARGO LOSS OR SHIFT

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_4564499 May 15, 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
2019 FREIGHTLINER Cascadia
NHTSA recalls and complaints for this make/model/year.
Recall
23V105000
STEERING:LINKAGES:DRAG:LINK:CONNECTION
Recall
23V073000
ELECTRONIC STABILITY CONTROL (ESC)
Recall
22V919000
TIRES
Carrier
TRADITION TRANSPORTATION COMPANY LLC
USDOT 247552 · 248 crashes · 0 inspections
Vehicle
VIN: 3AKJHHDR8KSKN9340
Decode this VIN for make, model, year, and recall data.
State
Crashes in Ohio
Statewide crash records.
Agency
TRADITION TRANSPORT CO LLC
Crashes reported by this law-enforcement agency.
City
Crashes in WASHINGTON (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.