What makes an accident 'preventable' under fleet safety standards?

A crash is generally considered preventable when the driver had a reasonable opportunity to avoid it — through observation, speed management, space management, or a defensive action — and failed to take that opportunity. The National Safety Council's definition centers on whether the driver did everything reasonable to prevent the collision, regardless of legal fault.

Does a 'non-preventable' determination erase the accident from CSA scores?

Not automatically. A crash can appear on a carrier's FMCSA Safety Measurement System (SMS) record regardless of the internal preventability call. Carriers may challenge a crash's inclusion through FMCSA's DataQs system if objective evidence supports removal or reclassification, but the internal fleet determination and the federal data record are separate processes.

Can a driver be at fault legally but the crash still be 'non-preventable'?

The two judgments are legally independent. Legal fault is determined by traffic law and courts; preventability is an internal fleet safety evaluation based on whether the driver could reasonably have avoided the crash. A driver can receive a citation and still have the crash coded non-preventable internally — or vice versa.

What should happen after a preventable crash is identified?

A preventable determination should trigger a documented corrective action — typically targeted driver training, a coaching session, or both. The type of training assigned should match the behavioral root cause (e.g., following distance, distraction, speed management). Documenting the training is equally important for insurance and regulatory purposes.

Do FMCSA regulations require fleets to conduct preventability reviews?

FMCSA's 49 CFR Part 391 focuses on driver qualification, annual MVR review, and related requirements for FMCSA-regulated carriers — it does not mandate a specific preventability review process. Preventability classification is an industry best practice (rooted in NSC criteria) rather than a federal regulatory requirement for most fleets.

Preventable vs. Non-Preventable Accidents: How Fleets Classify Crashes

Learn how fleets use NSC preventability criteria to classify crashes, drive training decisions, and manage CSA exposure for every driver.

Every fleet safety manager has been there: a driver gets into a crash, the police report assigns no citation, and the question immediately lands in your lap — was it preventable? The answer shapes your training response, your insurance conversations, and potentially your FMCSA Safety Measurement System (SMS) standing. Getting the classification right matters. Getting it wrong — either whitewashing a fixable behavior or blaming a driver for something genuinely unforeseeable — erodes the credibility of your whole safety program.

This guide explains how the preventable / non-preventable determination works, where it comes from, and how the call flows downstream into training and compliance.

Where the standard comes from: the NSC definition

The most widely adopted framework in commercial fleet safety comes from the National Safety Council (NSC), which defines a preventable accident as one in which the driver failed to do everything reasonable to avoid it. Notice what the definition does not say: it does not say the driver caused the crash, it does not require a citation, and it does not ask whether the other party was at fault.

The NSC standard asks a single behavioral question: Could this driver, exercising reasonable care and defensive technique, have avoided the collision? If yes, it's preventable. If no reasonable action was available, it's non-preventable.

This framing matters because it anchors your program to behavior, not to legal outcomes — which is exactly where a safety program can intervene.

The determination process: who decides and how

A sound preventability review typically follows this sequence:

Gather all available evidence. Police report, driver statement, vehicle telematics, dashcam footage, witness accounts, and photos. Never make the call on the police report alone.
Apply the NSC behavioral test. For each contributing factor, ask: Was there a reasonable, available defensive action the driver could have taken? Common factors include following distance, speed relative to conditions, scanning habits, distraction, and lane positioning.
Document the reasoning. The determination — and the evidence behind it — should be in writing. A verbal "we'll call it non-prev" with no paper trail does nothing for you at an insurance renewal or a DOT audit.
Communicate the result to the driver. A preventable finding is not a punishment; it is a diagnostic. The driver needs to understand which specific behavior the program identified and what improvement looks like.
Assign corrective action. More on this below.

Disclaimer: Preventability standards, FMCSA SMS rules, and DataQs challenge procedures are subject to change. This post reflects general industry practice and publicly available FMCSA guidance as of the published date. Confirm current requirements directly with FMCSA at https://www.fmcsa.dot.gov and review 49 CFR Parts 390–391 at the eCFR (https://www.ecfr.gov) before making compliance decisions.

How preventability drives training assignments

A preventable classification without a training response is a missed opportunity. The root cause behind the classification should directly determine the training:

Root cause identified	Likely training focus
Following too closely	Space management / 4-second rule
Distraction (phone, in-cab)	Distracted driving policy + hands-free habits
Speed relative to conditions	Weather / road-condition decision-making
Backing incident	Backing protocols, spotter use, GOAL (Get Out And Look)
Intersection conflict	Intersection approach scanning, right-of-way yielding

Generic re-training — sending every driver through the same module after every crash — is less effective than targeted coaching tied to the specific behavior that made the crash preventable. Document both the determination and the training assigned in the driver's file. For FMCSA-regulated carriers, 49 CFR Part 391 already requires maintaining driver-qualification files and conducting annual MVR reviews; your post-crash training record belongs alongside that documentation.

For a deeper look at training programs that fit post-accident assignments, see our guide to post-accident driver training and our overview of the best online fleet safety training programs.

Preventability and CSA: two separate systems

One of the most persistent misconceptions in fleet safety is that a "non-preventable" internal ruling automatically removes a crash from the carrier's FMCSA SMS record. It does not.

The FMCSA's Crash Indicator BASIC (Behavior Analysis and Safety Improvement Category) scores crashes based on what appears in reportable crash data — not on your internal classification. A carrier that wants to challenge a crash's presence in SMS must use FMCSA's DataQs system, submitting objective evidence (dashcam, police report corrections, witness statements) that the crash record is inaccurate or that the carrier was not at fault under FMCSA's own Not-At-Fault criteria.

The DataQs process and your internal preventability review are parallel but separate workflows:

Internal review → drives training, coaching, and HR documentation.
DataQs challenge → attempts to correct or remove the crash from federal SMS data based on objective evidence.

Running both processes in parallel — whenever the evidence supports a non-preventable finding — gives your fleet the best chance of protecting both the driver's file and the carrier's safety rating.

Building consistency into the process

The greatest risk in preventability reviews isn't bad judgment on a single crash — it's inconsistency across crashes and reviewers. If two similar rear-end incidents get opposite classifications because different managers handled them, you've created a credibility problem that can surface in litigation, insurance audits, and driver grievances.

Reduce inconsistency by:

Using a written standard (NSC criteria or a documented company policy) that all reviewers apply.
Routing borderline cases through a review committee rather than a single manager.
Auditing past determinations periodically to spot drift.

For a broader framework, our fleet accident reporting procedure template and fleet safety program best practices walk through how to build this consistency into your standard operating procedures.

The bottom line

Preventability classification is one of the most consequential tools a fleet safety program has — because it forces a behavioral answer to a behavioral problem. Legal fault tells you who pays; preventability tells you what to fix. Done consistently and documented thoroughly, it turns every crash into data your program can act on.