5 minute read

A single crash in your Safety Measurement System (SMS) record can push your Crash Indicator BASIC percentile past the intervention threshold, triggering carrier investigations, shipper audits, and broker contract terminations — even when the crash was caused entirely by another party. FMCSA’s Crash Preventability Determination Program (CPDP) provides a formal mechanism to challenge that attribution. Understanding how to use it precisely, and when it actually changes your SMS standing, is a critical operational competency for any carrier serious about compliance management.

What the FMCSA Crash Preventability Determination Program Actually Does

The FMCSA crash preventability determination program does not expunge crash records. That distinction is operationally significant and frequently misunderstood. When FMCSA determines a crash was “Not Preventable,” the crash remains in the MCMIS database and is still visible in SMS. However, it receives a “Not Preventable” notation, and its weight in your Crash Indicator BASIC calculation is reduced — specifically, FMCSA applies a 0.0 weight to Not Preventable crashes in the SMS algorithm.

The practical effect: a Not Preventable determination functionally removes the crash’s numeric contribution to your percentile ranking without deleting the underlying record. For carriers operating near or above the 65th to 80th percentile intervention thresholds — which vary by BASIC category and vehicle type — this can mean the difference between triggering an offsite investigation or remaining below the radar.

How the Program Scope Has Expanded Over Time

The CPDP launched as a pilot in 2017 covering eight specific crash types. FMCSA subsequently expanded eligibility. As of the current program parameters, eligible crash scenarios include:

  • Struck in the rear by another vehicle
  • Struck while legally stopped or parked
  • Crash caused by wrong-way driver
  • Crash involving a driver under the influence of alcohol or drugs (other driver)
  • Struck by cargo or equipment from another vehicle
  • Pedestrian, cyclist, or other non-motorist entering the roadway illegally
  • Vehicle experiencing a medical emergency (other driver)
  • Crash occurring during an emergency response event

Each scenario carries specific evidentiary requirements. A rear-end strike, for example, requires documentation establishing the CMV driver’s position, speed, and that no prior traffic code violation contributed to the sequence.

Eligibility Requirements and Filing Mechanics

Qualifying Crash Criteria Under 49 CFR

To be eligible for a CPDP submission, the crash must meet the federal recordable threshold under 49 CFR 390.5 — meaning it resulted in a fatality, injury requiring medical treatment beyond first aid, or a vehicle tow-away. The crash must also appear in FMCSA’s MCMIS database, which generally occurs after state reporting pipelines complete, typically 60 to 90 days post-incident.

Requests must be submitted within 18 months of the crash date. This deadline is a hard cutoff — no appeals process exists for late submissions. Carriers managing new operations should note that SMS crash data and BASIC percentile mechanics interact with the broader monitoring framework described in the new entrant program’s 18-month monitoring period, making early crash events disproportionately damaging if left unchallenged.

Documentation That Drives Approval Rates

FMCSA reviews submitted documentation against the specific scenario definition. The submission portal accepts standard file formats. High-impact evidence packages typically include:

  • Official police accident report with narrative section
  • Toxicology results for the other driver (if DUI scenario)
  • Dashcam video from the CMV (timestamped, continuous)
  • Witness statements corroborating the CMV driver’s lawful operation
  • State DMV records confirming the other driver’s wrong-way or suspended status
  • GPS/ELD data demonstrating speed and lane position at time of impact

Incomplete or ambiguous documentation is the primary reason submissions are denied or returned. FMCSA does not conduct independent investigations — the determination is based solely on submitted materials.

How a Determination Affects Your SMS Standing

Crash Indicator BASIC Mechanics

Your Crash Indicator BASIC percentile is calculated using a time-weighted algorithm applied to crashes occurring within the previous 24 months. Recent crashes carry higher weight. If you understand how CSA points accumulate across violation categories, you already know that the Crash Indicator operates differently from the violation-based BASICs — it is driven by crash frequency and severity relative to miles traveled, not inspection violations.

A single fatal crash can move a carrier with moderate mileage into the 90th+ percentile. A Not Preventable determination zeros out that crash’s weight in the calculation, often producing a 15 to 30 percentile point drop depending on fleet size and total crash history. For small carriers operating fewer than 15 power units, one crash can be the entire basis of an elevated percentile, making the CPDP particularly high-value for smaller operations. The BASIC percentile threshold differences by vehicle type also affect how urgently intervention thresholds apply to your specific equipment mix.

Intersection With DataQs and Inspection Disputes

The CPDP is structurally separate from the DataQs system, which handles inspection record corrections. If you have a roadside inspection tied to a crash event — a common scenario where inspectors cite violations following an accident regardless of fault — you may need to pursue both processes in parallel. The DataQs dispute process for roadside inspection findings addresses violation code accuracy; the CPDP addresses crash preventability. Neither substitutes for the other.

Downstream Compliance and Commercial Implications

A carrier’s SMS profile is increasingly embedded in commercial relationships. Brokers running carrier vetting processes are checking Crash Indicator percentiles directly, and broker-carrier agreements now routinely contain compliance clauses that permit contract termination based on SMS thresholds. A Not Preventable determination that moves your percentile below 65 can have immediate commercial value beyond regulatory compliance.

FMCSA publishes both the program guidelines and aggregate acceptance rate data through its safety data and statistics portal. Carriers can also access the official CPDP submission interface and scenario definitions directly. Review the scenario definitions carefully before submitting — a crash that appears to qualify may fail on a technical element if the documentation does not clearly establish the scenario’s factual predicate.

Treat every eligible crash as a CPDP candidate from the moment of incident. Build evidence collection into your post-crash protocol. The 18-month window sounds generous until fleet operations consume the first six months and documentation becomes difficult to reconstruct.

Data sourced from FMCSA Crash Preventability Determination Program and FMCSA public records. Verify current enforcement thresholds at fmcsa.dot.gov.

Updated:

You May Also Enjoy