Crash Indicator
The FMCSA BASIC category measuring a carrier's crash history. Counts reportable crashes — those resulting in fatality, injury, or vehicle damage requiring tow — over a two-year window, weighted by recency and severity. Crashes are counted regardless of fault determination at the scene; FMCSA's position is that involvement is a measurable safety signal even when the carrier driver was not the at-fault party.
Why it matters
Crash Indicator is one of the most controversial BASICs because the fault question is set aside in the scoring. A carrier's drivers can be struck by other vehicles and still see their Crash Indicator percentile rise. Industry advocacy has pushed for fault-adjusted scoring for years; as of current rules, the BASIC counts the involvement. Despite the controversy, the BASIC remains a primary signal for federal enforcement, insurance underwriting, and procurement.
Where it appears in a ProHRHQ carrier page
The ProHRHQ carrier page shows the three-year reportable crash count in the Federal record summary and the most recent crash date in the Inspection and violation record. The Crash Indicator percentile rank itself is on the federal SMS site and is referenced in the page's safety analysis.
Which crashes count, and preventability
The Crash Indicator uses state-reported crashes from the past 24 months that meet the federal reporting threshold: a fatality, an injury needing treatment away from the scene, or a vehicle towed from the scene. By default every reportable crash counts, including ones the truck driver did not cause. Through the Crash Preventability Determination Program, a carrier can submit eligible crashes, such as being struck from behind or by a wrong-way driver, with police reports and other evidence; crashes found not preventable are removed from the measure. The Crash Indicator percentile is not shown publicly, so drivers and brokers see the crash count rather than the ranking.
Related terms
Crash Indicator scoring methodology is defined by FMCSA and evolves. Carriers contesting crash data accuracy file through the DataQs process; fault disputes are handled separately from the federal scoring.