Skip to main content
TruckCodex
Hubs

Crash Record IA1700991306

FMCSA crash record in Iowa on Jul 5, 2017.

Fatal

What happened

On July 5, 2017, FMCSA recorded a fatal crash that resulted in one death in Iowa. The vehicle was operated by NORTHLAND PRODUCTS CO INC (USDOT 1652). FMCSA reference IA1700991306.

Fatalities
1
Injuries
0
Vehicles
—
Carrier
USDOT 1652
Vehicle Type
—
Severity
Fatal

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
1
1 fatal · 0 injury
Crashes per 100 power units (24 mo)
0.0
0 crashes · 21 units
Days since prior carrier crash
2,744
Last on Dec 30, 2009
Vs fleet-size peers
above the median
Cohort median 0.0 · 315,833 carriers

Geographic context

How this crash sits in its setting.

Within Iowa, 3,671 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

Crash details

Key facts from the FMCSA crash record.

Report #:
IA1700991306
Date:
Jul 5, 2017
Time:
0749
State:
Iowa
Fatalities:
1
Injuries:
0
Tow-Away:
Yes
HazMat:
No

Other crashes by this carrier

8 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4683401 Jan 15, 2024 IA Injury 0 2
cr_4316208 Mar 7, 2022 IA Injury 0 1
cr_2225950 Dec 30, 2009 MN Tow-Away 0 0
cr_2163980 Aug 28, 2009 NE Tow-Away 0 0
cr_2152425 Aug 3, 2009 KS Tow-Away 0 0
cr_1159504 Aug 18, 2003 IA Injury 0 1
cr_1163538 Jul 7, 2003 KS Injury 0 1
cr_890610 Jan 18, 1998 NY Injury 0 2

Carrier booking & risk tools

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

Related records

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.