Crash Record OH0245006107

FMCSA crash record in JEFFERSON (TOWNSHIP OF) on Jan 9, 2024.

Tow-Away Federal Recordable

What happened

On January 9, 2024, FMCSA recorded a tow-away crash with no reported injuries in JEFFERSON (TOWNSHIP OF), Ohio. The vehicle was operated by GAMMA PRIME INC (USDOT 3194118). Recorded conditions: 2 / 4 / 5 pavement. Reported by GAMMA PRIME INC, FMCSA reference OH0245006107.

Carrier pattern note

This is the carrier's 5 crashes in the past 24 months — above the typical pattern (median 0) for fleets of 1–5 power units.

Geographic note

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

Fatalities

Injuries

Vehicles

Carrier

GAMMA PRIME INC

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

2 injury · 5 tow-away

Crashes per 100 power units (24 mo)

0.0

0 crashes · 1 units

Days since prior carrier crash

Last on Jan 7, 2024

Vs fleet-size peers

above the median

Cohort median 0.0 · 3,564,119 carriers

Geographic context

How this crash sits in its setting.

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

Agencies most active in this area:

UNKNOWN · 7 reports
SKYLINE AB LLC · 2 reports
NEW PRIME INC · 2 reports

Contributing factors

What the responding officer recorded.

Light: 2
Weather: 4
Road surface: 5

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 #:: OH0245006107
Date:: Jan 9, 2024
Time:: 0346
State:: Ohio
City:: JEFFERSON (TOWNSHIP OF)
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 1
Carrier (USDOT):: GAMMA PRIME INC (3194118)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	9	3	3AKJHHDR4LSLM5486	P1178051 (IL)	GAMMA PRIME INC	3	No

Crash event

Event sequence description.

1:6:NONCOLLISION:EXPLOSION OR FIRE;2:18:COLLISION INVOLVING FIXED OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record	Date	State	Severity	Injuries
cr_4809784	Sep 3, 2024	MO	Tow-Away	0
cr_4795404	Aug 12, 2024	MO	Tow-Away	0
cr_4846357	Aug 7, 2024	CO	Injury	1
cr_4802523	Aug 6, 2024	GA	Tow-Away	0
cr_4794321	Jul 24, 2024	CA	Tow-Away	0
cr_4783094	Jul 24, 2024	NC	Tow-Away	0
cr_4788243	Jul 22, 2024	VA	Tow-Away	0
cr_4789615	Jul 19, 2024	VA	Tow-Away	0
cr_4784800	Jul 19, 2024	UT	Tow-Away	0
cr_4781312	Jul 13, 2024	OK	Tow-Away	0

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 3194118 · 31 crashes · 0 inspections

Vehicle

VIN: 3AKJHHDR4LSLM5486

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

State

Crashes in Ohio

Statewide crash records.

Agency

GAMMA PRIME INC

Crashes reported by this law-enforcement agency.

City

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