Crash Record OH0215027217

FMCSA crash record in BERLIN (TOWNSHIP OF) on Feb 17, 2021.

Injury Federal Recordable

What happened

On February 17, 2021, FMCSA recorded an injury crash with 2 people hurt in BERLIN (TOWNSHIP OF), Ohio. The vehicle was operated by IG TRANSPORTATION INC (USDOT 1928967). Recorded conditions: 2 / 1 / 1 pavement. FMCSA reference OH0215027217.

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: 33 crashes occurred in the same city in the past 24 months.

Fatalities

Injuries

Vehicles

Carrier

IG TRANSPORTATION INC

USDOT 1928967

Vehicle Type

Truck

Severity

Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

3 injury · 11 tow-away

Crashes per 100 power units (24 mo)

2.7

13 crashes · 483 units

Days since prior carrier crash

Last on Jan 12, 2021

Vs fleet-size peers

above the median

Cohort median 0.0 · 27,136 carriers

Geographic context

How this crash sits in its setting.

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

Agencies most active in this area:

COOKE TRANSPORT LLC · 1 reports
ESTES EXPRESS LINES · 1 reports
BIG M LLC, · 1 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 #:: OH0215027217
Date:: Feb 17, 2021
Time:: 2154
State:: Ohio
City:: BERLIN (TOWNSHIP OF)
Fatalities:: 0
Injuries:: 2
Tow-Away:: Yes
HazMat:: No
Vehicles:: 3
Carrier (USDOT):: IG TRANSPORTATION INC (1928967)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
3	9	12	3ALXFB003KDKG8009	P1023574 (IL)	IG TRANSPORTATION 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
cmoax1cnl008lnvsy5z7uu30q	Apr 15, 2026	NC	Tow-Away	0
cr_5116858	Jan 26, 2026	PA	Tow-Away	0
cr_5114645	Sep 26, 2025	NC	Tow-Away	0
cr_5029997	Sep 13, 2025	TN	Tow-Away	0
cr_5025450	Aug 21, 2025	IN	Tow-Away	0
cr_5008982	Jul 30, 2025	SC	Tow-Away	0
cr_5014911	Jul 29, 2025	TX	Tow-Away	0
cr_4923646	Mar 9, 2025	MD	Tow-Away	0
cr_4886424	Jan 28, 2025	SC	Injury	1
cr_4894579	Jan 9, 2025	MI	Tow-Away	0

Carrier booking & risk tools

Check booking and risk signals for USDOT 1928967 — tools open pre-filled.

Book / don't book Insurance check Cancel desk Chameleon check Safety benchmark

Related records

Carrier

IG TRANSPORTATION INC

USDOT 1928967 · 72 crashes · 1,287 inspections

Safety

Carrier inspections

Roadside inspection history for this USDOT.

Vehicle

VIN: 3ALXFB003KDKG8009

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

State

Crashes in Ohio

Statewide crash records.

City

Crashes in BERLIN (TOWNSHIP OF), OH

All crashes on file for this city.

Station

IR 80

Weigh / inspection station matching this crash location.

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.