Crash Record OH0225217852

FMCSA crash record in UNION (TOWNSHIP OF) on Nov 8, 2022.

Tow-Away Federal Recordable

What happened

On November 8, 2022, FMCSA recorded a tow-away crash with no reported injuries in UNION (TOWNSHIP OF), Ohio. The vehicle was operated by SHARP TRANSIT LLC (USDOT 910824). Recorded conditions: 2 / 1 / 1 pavement. Reported by SHARP TRANSIT, FMCSA reference OH0225217852.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

SHARP TRANSIT LLC

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

3 fatal · 13 injury

Crashes per 100 power units (24 mo)

7.2

26 crashes · 360 units

Days since prior carrier crash

Last on Oct 30, 2022

Vs fleet-size peers

above the median

Cohort median 0.0 · 27,005 carriers

Geographic context

How this crash sits in its setting.

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

Agencies most active in this area:

CENTRAL TRANSPORT LLC · 2 reports
HOGAN DEDICATED SERVICES LLC · 2 reports
UNKNOWN · 2 reports

Contributing factors

What the responding officer recorded.

Light: 2
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 #:: OH0225217852
Date:: Nov 8, 2022
Time:: 2328
State:: Ohio
City:: UNION (TOWNSHIP OF)
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: SHARP TRANSIT LLC (910824)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	9	3	1M1AN4GY1MM022595	NM1440 (NC)	SHARP TRANSIT	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
cmsw88se500edpev3oea1oedm	Aug 7, 2026	NC	Tow-Away	0	0
cr_5123749	Mar 15, 2026	NC	Fatal	1	1
cr_5113136	Feb 28, 2026	NC	Tow-Away	0	0
cr_5108379	Jan 23, 2026	SC	Tow-Away	0	0
cr_5093107	Jan 15, 2026	OH	Tow-Away	0	0
cr_5074406	Dec 4, 2025	GA	Tow-Away	0	0
cr_5047854	Oct 17, 2025	MI	Tow-Away	0	0
cr_5029796	Sep 6, 2025	GA	Tow-Away	0	0
cr_5033909	Sep 1, 2025	FL	Tow-Away	0	0
cr_5009950	Aug 1, 2025	TN	Fatal	1	2

Related records

Carrier

SHARP TRANSIT LLC

USDOT 910824 · 369 crashes · 490 inspections

Safety

Carrier inspections

Roadside inspection history for this USDOT.

Vehicle

VIN: 1M1AN4GY1MM022595

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

State

Crashes in Ohio

Statewide crash records.

Agency

SHARP TRANSIT

Crashes reported by this law-enforcement agency.

City

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