Skip to main content
TruckCodex
Hubs

Crash Record OH0235013517

FMCSA crash record in PERRY (TOWNSHIP OF) on Jan 27, 2023.

Tow-Away Federal Recordable

What happened

On January 27, 2023, FMCSA recorded a tow-away crash with no reported injuries in PERRY (TOWNSHIP OF), Ohio. The vehicle was operated by ESTES EXPRESS LINES (USDOT 121018). Recorded conditions: 2 / 4 / 2 pavement. FMCSA reference OH0235013517.

Carrier pattern note

This is the carrier's 578 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: 90 crashes occurred in the same city in the past 24 months.

Fatalities
0
Injuries
0
Vehicles
3
Carrier
ESTES EXPRESS LINES
USDOT 121018
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
578
21 fatal · 180 injury
Crashes per 100 power units (24 mo)
4.4
430 crashes · 9,805 units
Days since prior carrier crash
1
Last on Jan 26, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,888 carriers

Geographic context

How this crash sits in its setting.

Within PERRY (TOWNSHIP OF), Ohio, 90 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
2
Weather
4
Road surface
2

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 #:
OH0235013517
Date:
Jan 27, 2023
Time:
0310
State:
Ohio
City:
PERRY (TOWNSHIP OF)
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
3
Carrier (USDOT):
ESTES EXPRESS LINES (121018)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
3 9 3 3HSDZAPR8NN050605 NP2272 (NC) ESTES EXPRESS 3 No

Crash event

Event sequence description.

1:21:COLLISION INVOLVING UNKNOWN MOVABLE OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cmvz8aav90015o3oxa7s9onkr Oct 29, 2026 TN Injury 0 2
cmvnd7c5n0025o3b5p0yrrvzi Oct 20, 2026 NJ Tow-Away 0 0
cmu0qslec0033pmtnxxnmf54e Sep 8, 2026 PA Tow-Away 0 0
cmsw88s6a0057pev3r146967x Aug 10, 2026 NC Injury 0 1
cmshdfe76000bpefy6qhcvfp2 Jul 31, 2026 OH Injury 0 1
cms8hio0p000fpeo5t4hsliwe Jul 26, 2026 NC Tow-Away 0 0
cms1c436x004fpee88ssjbxgy Jul 20, 2026 NJ Tow-Away 0 0
cmrn1fc43000dpez58l7k4248 Jul 11, 2026 NC Injury 0 1
cmqg6ahmm000bp48dbin0k41p Jun 11, 2026 TN Tow-Away 0 0
cmqesjpmp003vp4us3qim7lgf Jun 9, 2026 PA Tow-Away 0 0

Carrier booking & risk tools

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

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

Related records

Vehicle
2022 INTERNATIONAL LT625
NHTSA recalls and complaints for this make/model/year.
Carrier
ESTES EXPRESS LINES
USDOT 121018 · 6,288 crashes · 8,487 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 3HSDZAPR8NN050605
Decode this VIN for make, model, year, and recall data.
State
Crashes in Ohio
Statewide crash records.
City
Crashes in PERRY (TOWNSHIP OF), OH
All crashes on file for this city.
Station
IR 71
Weigh / inspection station matching this crash location.
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.