Crash Record OH0086255240

FMCSA crash record in Ohio on Aug 29, 2008.

Tow-Away

What happened

On August 29, 2008, FMCSA recorded a tow-away crash with no reported injuries in Ohio. The vehicle was operated by GETGO TRANSPORTATION COMPANY LLC (USDOT 920805). FMCSA reference OH0086255240.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
Carrier
GETGO TRANSPORTATION COMPANY LLC
Vehicle Type
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
4
0 injury · 4 tow-away
Crashes per 100 power units (24 mo)
8.0
4 crashes · 50 units
Days since prior carrier crash
148
Last on Apr 3, 2008
Vs fleet-size peers
above the median
Cohort median 0.0 · 312,512 carriers

Geographic context

How this crash sits in its setting.

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

Agencies most active in this area:

Crash details

Key facts from the FMCSA crash record.

Report #:
OH0086255240
Date:
Aug 29, 2008
Time:
0915
State:
Ohio
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5091132 Dec 11, 2025 PA Tow-Away 0 0
cr_5017187 Aug 16, 2025 PA Tow-Away 0 0
cr_5015984 Aug 7, 2025 WI Injury 0 1
cr_4809246 Sep 3, 2024 OH Fatal 1 0
cr_4690924 Jan 16, 2024 OH Injury 0 1
cr_4651700 Nov 7, 2023 OH Injury 0 1
cr_4339051 Jan 24, 2022 OH Tow-Away 0 0
cr_4297301 Jan 24, 2022 MI Tow-Away 0 0
cr_4077783 Nov 10, 2020 IN Tow-Away 0 0
cr_4032728 Aug 13, 2020 NC Injury 0 1

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.