TruckCodex
Hubs

Crash Record OH0235037954

FMCSA crash record in FRANKLIN (TOWNSHIP OF) on Mar 6, 2023.

Injury Federal Recordable

What happened

On March 6, 2023, FMCSA recorded an injury crash with 2 people hurt in FRANKLIN (TOWNSHIP OF), Ohio. The vehicle was operated by VIRK TRANSPORTATION CORPORATION (USDOT 3291296). Recorded conditions: 1 / 1 / 1 pavement. Reported by VIRK TRANSPORTATION CORP, FMCSA reference OH0235037954.

Geographic note

This crash is part of an active corridor: 122 crashes occurred in the same city in the past 24 months.

Fatalities
0
Injuries
2
Vehicles
2
Carrier
VIRK TRANSPORTATION CORPORATION
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
2
1 injury · 2 tow-away
Crashes per 100 power units (24 mo)
0.0
0 crashes · 5 units
Days since prior carrier crash
98
Last on Nov 28, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,554,620 carriers

Geographic context

How this crash sits in its setting.

Within FRANKLIN (TOWNSHIP OF), Ohio, 122 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
1
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 #:
OH0235037954
Date:
Mar 6, 2023
Time:
1510
State:
Ohio
City:
FRANKLIN (TOWNSHIP OF)
Fatalities:
0
Injuries:
2
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
VIRK TRANSPORTATION CORPORATION (3291296)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 1XKYD49X4NJ499888 YP16739 (CA) VIRK TRANSPORTATION CORP 3 No

Crash event

Event sequence description.

1:1:NONCOLLISION:RAN OFF ROAD;2:20:COLLISION INVOLVING OTHER MOVABLE OBJECT

Other crashes by this carrier

1 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4474611 Nov 28, 2022 UT Tow-Away 0 0

Related records

Vehicle
2022 KENWORTH T680
NHTSA recalls and complaints for this make/model/year.
Recall
25V181000
ELECTRICAL SYSTEM
Recall
24V915000
ELECTRICAL SYSTEM
Recall
24V190000
POWER TRAIN:AUTOMATIC TRANSMISSION:LEVER AND LINKAGE:COLUMN SHIFT
Carrier
VIRK TRANSPORTATION CORPORATION
USDOT 3291296 · 2 crashes · 0 inspections
Vehicle
VIN: 1XKYD49X4NJ499888
Decode this VIN for make, model, year, and recall data.
State
Crashes in Ohio
Statewide crash records.
Agency
VIRK TRANSPORTATION CORP
Crashes reported by this law-enforcement agency.
City
Crashes in FRANKLIN (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.