Crash Record OH0222040293

FMCSA crash record in MARION (TOWNSHIP OF) on Feb 22, 2022.

Fatal Federal Recordable

What happened

On February 22, 2022, FMCSA recorded a fatal crash that resulted in one death in MARION (TOWNSHIP OF), Ohio. The vehicle was operated by STEP TRUCKING INC (USDOT 2543787). Recorded conditions: 5 / 2 / 2 pavement. FMCSA reference OH0222040293.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

STEP TRUCKING INC

Vehicle Type

Truck

Severity

Fatal

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

1 fatal · 3 injury

Crashes per 100 power units (24 mo)

10.0

11 crashes · 110 units

Days since prior carrier crash

Last on Feb 17, 2022

Vs fleet-size peers

above the median

Cohort median 0.0 · 26,684 carriers

Geographic context

How this crash sits in its setting.

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

Agencies most active in this area:

CHEESEMAN LLC · 1 reports
CK TRANSPORTATION LLC · 1 reports
APPLE FARM SERVICE INC · 1 reports

Contributing factors

What the responding officer recorded.

Light: 5
Weather: 2
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 #:: OH0222040293
Date:: Feb 22, 2022
Time:: 0647
State:: Ohio
City:: MARION (TOWNSHIP OF)
Fatalities:: 1
Injuries:: 1
Tow-Away:: No
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: STEP TRUCKING INC (2543787)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
2	9	3	4V4NC9EHXMN229976	P1077285 (IL)	STEP TRUCKING INC	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	Injuries
cr_5004873	Jul 29, 2025	OH	Injury	1
cr_4993928	Jul 14, 2025	GA	Tow-Away	0
cr_4996840	Jun 21, 2025	IN	Tow-Away	0
cr_4953641	May 29, 2025	OH	Tow-Away	0
cr_4945932	Apr 19, 2025	GA	Tow-Away	0
cr_4931419	Apr 9, 2025	TX	Tow-Away	0
cr_4879051	Jan 14, 2025	NY	Injury	1
cr_4873336	Jan 10, 2025	AL	Tow-Away	0
cr_4865108	Dec 15, 2024	UT	Tow-Away	0
cr_4850965	Nov 9, 2024	KS	Tow-Away	0

Related records

Carrier

STEP TRUCKING INC

USDOT 2543787 · 42 crashes · 0 inspections

Vehicle

VIN: 4V4NC9EHXMN229976

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

State

Crashes in Ohio

Statewide crash records.

City

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