Crash Record OH0255244275

FMCSA crash record in PROVIDENCE (TOWNSHIP OF) 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 PROVIDENCE (TOWNSHIP OF), Ohio. The vehicle was operated by VASCOR TRANSPORT LTD (USDOT 2514939). Recorded conditions: 1 / 4 / 6 pavement. Reported by VASCOR TRANSPORT LTD, FMCSA reference OH0255244275.

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.

Fatalities

Injuries

Vehicles

Carrier

VASCOR TRANSPORT LTD

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

4 injury · 18 tow-away

Crashes per 100 power units (24 mo)

8.0

15 crashes · 188 units

Days since prior carrier crash

Last on Nov 14, 2025

Vs fleet-size peers

above the median

Cohort median 0.0 · 26,833 carriers

Geographic context

How this crash sits in its setting.

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

Agencies most active in this area:

AYDEN HEALTHCARE OF WATERVILLE, · 1 reports
CASSENS TRANSPORT COMPANY · 1 reports
10804053 CANADA LTD · 1 reports

Contributing factors

What the responding officer recorded.

Light: 1
Weather: 4
Road surface: 6

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 #:: OH0255244275
Date:: Dec 9, 2025
Time:: 0934
State:: Ohio
City:: PROVIDENCE (TOWNSHIP OF)
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 1
Carrier (USDOT):: VASCOR TRANSPORT LTD (2514939)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	9	3	3AKJHLDR1LSLG5855	2869394 (IN)	VASCOR TRANSPORT LTD	3	No

Crash event

Event sequence description.

1:15:COLLISION INVOLVING TRAIN;2:6:NONCOLLISION:EXPLOSION OR FIRE

Other crashes by this carrier

10 additional crash record(s) on file.

Record	Date	State	Severity	Injuries
cr_5122974	Mar 9, 2026	MI	Tow-Away	0
cr_5091603	Jan 15, 2026	KY	Injury	2
cr_5095904	Jan 9, 2026	GA	Tow-Away	0
cr_5068896	Nov 14, 2025	MI	Tow-Away	0
cr_5046525	Oct 17, 2025	OH	Tow-Away	0
cr_5054682	Oct 1, 2025	IN	Tow-Away	0
cr_5017849	Aug 26, 2025	KY	Injury	1
cr_4950236	May 20, 2025	OH	Tow-Away	0
cr_4919366	Mar 10, 2025	KY	Tow-Away	0
cr_4895889	Feb 19, 2025	AR	Injury	4

Related records

Vehicle

2020 FREIGHTLINER Cascadia

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

Recall

26V583000

SERVICE BRAKES, AIR:ANTILOCK

Recall

23V299000

ELECTRONIC STABILITY CONTROL (ESC)

USDOT 2514939 · 78 crashes · 510 inspections

Vehicle

VIN: 3AKJHLDR1LSLG5855

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

State

Crashes in Ohio

Statewide crash records.

Agency

VASCOR TRANSPORT LTD

Crashes reported by this law-enforcement agency.

City

Crashes in PROVIDENCE (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.