DataQs Crash Preventability Program: The Complete Guide
FMCSA's Crash Preventability Determination Program lets carriers request DataQs review of eligible crashes — such as being rear-ended or hit while legally stopped. If found not preventable, the crash is excluded from the carrier's Crash Indicator measurement. Submit promptly with the police report, dash footage, and corroborating evidence.
Not every crash on a carrier's record was the driver's fault — and the FMCSA's Crash Preventability Determination Program exists to recognize that. The program allows motor carriers to request a formal review of certain crashes and, when FMCSA agrees the crash was not preventable by the driver, to have that crash excluded from the carrier's safety measurement. For carriers, a successful determination can meaningfully improve how their safety record reads to enforcement, brokers, and insurers.
The program runs through DataQs, FMCSA's system for challenging safety data. It is separate from — but closely related to — the general DataQs process for correcting inspection violations and data errors. If you are dealing with a citation or an incorrect inspection report rather than a crash, start with our DataQs challenge guide; this guide focuses specifically on crash preventability reviews.
Below is how the program works in practice: which crashes are eligible for review, how to submit a request, what evidence reviewers expect, what 'not preventable' actually means in FMCSA's framework, and what happens after the determination — granted or denied.
What the Program Is and Why It Exists
The Crash Preventability Determination Program is FMCSA's formal process for reviewing crashes and determining whether they were preventable by the commercial driver. When a crash is found not preventable, FMCSA notes that finding in the safety measurement system so the crash does not count against the carrier the way a preventable crash would. The crash itself remains in the record — the program changes how it is weighted, not whether it happened.
The program exists because the Crash Indicator BASIC would otherwise treat every crash alike regardless of fault. A driver rear-ended while stopped at a red light and a driver who ran that same light would look identical in raw crash counts. Preventability review restores the distinction, giving carriers a fairer measurement and giving the enforcement system better data about actual risk.
For carriers, the practical value is in every downstream use of the safety record. Broker vetting, shipper qualification, insurance underwriting, and FMCSA's own intervention prioritization all read the same data. Removing a non-preventable crash from the measurement improves how the carrier looks in all of those readings at once.
Which Crashes Are Eligible for Review
FMCSA defines specific eligible crash types for the program — scenarios where the structure of the crash itself suggests the commercial driver may not have been at fault. Classic examples include being struck in the rear, being struck by a vehicle that was going the wrong way, or being hit while legally stopped or parked. The eligible-types list is published by FMCSA and has expanded over the program's life, so carriers should check the current list before submitting.
Eligibility by crash type is the threshold question, not the final answer. A crash that fits an eligible scenario still receives a full review of the evidence, and reviewers can deny the request if the facts show the driver contributed — for instance, a rear-end collision where the truck stopped suddenly without cause in moving traffic. The scenario opens the door; the evidence decides the outcome.
Crashes outside the eligible types cannot be submitted to this program, though other DataQs challenges may still apply — for example, if the crash was attributed to the wrong carrier or contains factual errors. Knowing which DataQs path fits your situation saves months: preventability review for eligible non-preventable crashes, standard data correction for everything else.
How to Submit a Request Through DataQs
Requests are submitted through the DataQs system, FMCSA's online portal for safety-data challenges. The carrier — not the driver individually, in practice — files the request, identifies the crash by its report details, selects the crash-preventability review track, and uploads the supporting evidence. Accurate crash identification matters: the request must match the crash as recorded in FMCSA's systems.
The submission should tell a clear, evidence-backed story of non-preventability. Reviewers work from the documents provided, so the request needs to establish what happened, what the driver did, and why the crash could not reasonably have been avoided. A thin submission with no documentation invites denial; a complete one lets the evidence speak.
Timing matters. File as soon as the evidence is assembled rather than waiting — the crash is affecting the carrier's measurement from the moment it posts, and every month of delay is a month of distorted data influencing broker checks and enforcement prioritization. Build preventability review into the post-crash procedure so eligible crashes are identified within days, not discovered a year later.
Evidence That Persuades Reviewers
The police crash report is the foundation of nearly every submission. Reviewers expect the official report, and its narrative and diagram carry significant weight — a report that clearly describes the other vehicle striking the truck supports non-preventability far more than a vague or contradictory one. Obtain the final report, not just the preliminary version, when they differ.
Dash camera footage is the single most persuasive supplement when it exists. Video showing the truck stopped, in its lane, or otherwise operating properly at the moment of impact can resolve in minutes what reports leave ambiguous. Carriers without dash cameras should consider this program one more reason to install them — the footage pays for itself the first time it wins a preventability review or defeats a false claim.
Supporting evidence rounds out the file: photographs of the scene and vehicle damage, witness statements, the driver's written account made promptly after the crash, and any available telematics or ELD data showing speed and position. Each piece should corroborate the others. Contradictions between the driver's account and the police report need explanation, not concealment — reviewers notice them either way.
What 'Not Preventable' Means in Practice
FMCSA's standard is whether the crash was preventable by the commercial driver exercising normal safe-driving practices — not whether the crash was anyone's 'fault' in a legal sense, and not whether the driver was perfect. The question is whether a reasonably prudent professional driver in the same situation could have avoided it. Reviewers apply this standard to the documented facts, not to speculation about what might have been.
This means the driver's own conduct is always under review. Speed appropriate for conditions, following distance, lane discipline, and attention all factor in. A crash that fits an eligible scenario can still be denied if the evidence shows the driver was speeding, distracted, or otherwise contributing. The program rewards genuinely safe driving; it does not excuse sloppy driving that happened to fit a category.
Carriers should apply the same standard internally before submitting. An honest internal review that concludes the crash was actually preventable saves the time and credibility of a doomed submission — and identifies the coaching opportunity the crash represents. File the strong cases aggressively; learn from the weak ones.
After the Determination: Granted or Denied
When FMCSA grants a not-preventable determination, the crash is noted accordingly in the safety measurement system and excluded from the Crash Indicator calculation. The improvement flows through to every downstream use of the data. Carriers should still keep the determination documentation on file — brokers or insurers asking about the crash deserve the full story, and the determination letter is the authoritative answer.
A denial is not the end of the road. Review the decision, understand what evidence was missing or unpersuasive, and consider whether additional documentation supports resubmission where the program permits it. Some denials reflect genuinely preventable crashes — accept those and coach the driver. Others reflect thin submissions that a second, better-documented attempt could win.
The strategic lesson is procedural: make preventability review a standard step in post-crash handling, alongside the insurance claim and the internal safety review. Carriers that systematically identify eligible crashes, preserve dash footage, and file complete submissions capture value their competitors leave on the table — cleaner safety data, earned honestly, one determination at a time.
Key takeaways
- The program can exclude non-preventable crashes from your Crash Indicator measurement.
- Only FMCSA's published eligible crash types qualify — check the current list first.
- File through DataQs promptly; the crash distorts your data from day one.
- The police report plus dash camera footage is the strongest evidence combination.
- 'Not preventable' means a prudent professional driver could not have avoided it.
- Make preventability review a standard step in every post-crash procedure.
Questions carriers ask
What is the Crash Preventability Determination Program?
An FMCSA program that lets carriers request formal review of certain crashes through DataQs. If FMCSA determines the crash was not preventable by the driver, the crash is excluded from the carrier's Crash Indicator safety measurement — improving how the safety record reads to enforcement, brokers, and insurers.
Which crashes can be submitted for preventability review?
FMCSA publishes a list of eligible crash types — scenarios like being struck in the rear or hit while legally stopped that suggest the commercial driver was not at fault. Check the current FMCSA list before submitting; crashes outside the eligible types cannot use this program.
How do I file a crash preventability request?
Through the DataQs system: identify the crash as recorded in FMCSA's systems, select the crash-preventability track, and upload supporting evidence. File promptly once evidence is assembled — the crash affects your measurement from the day it posts.
What evidence should I include?
The final police crash report as the foundation, dash camera footage when available, scene and damage photos, witness statements, the driver's prompt written account, and telematics or ELD data. Each piece should corroborate the others; explain contradictions rather than hiding them.
What does 'not preventable' mean to FMCSA?
Whether a reasonably prudent professional driver exercising normal safe practices could have avoided the crash — not legal fault, and not perfection. The driver's own conduct (speed, following distance, attention) is always part of the review, and eligible-scenario crashes can still be denied if the driver contributed.
What happens if my request is denied?
Review the decision to understand what was missing, and consider resubmission with stronger documentation where permitted. Accept genuinely preventable outcomes as coaching opportunities. Either way, keep the determination paperwork — granted or denied — in the crash file.