The crash BASIC score–specifically a high score–can have serious consequences for fleets, impacting insurance rates, compliance, and overall business reputation. However, not all recorded crashes are truly preventable. The FMCSA’s Crash Preventability Determination Program (CPDP) offers a way for fleets to challenge certain crash records and potentially lower their crash BASIC scores. Understanding how this program works and taking proactive steps can help fleets maintain a more accurate safety record and avoid unnecessary penalties.
The impact of high crash BASIC scores for fleets
A fleet’s crash BASIC score may seem disproportionately high compared to other CSA BASICs. While some fleets have high scores due to preventable crashes, others may have inflated scores because they have not submitted DataQs for crashes that could be deemed non-preventable.
A common example is when a vehicle strikes the back of a commercial truck while it is legally stopped in traffic. If injuries occur or a vehicle needs to be towed, the crash is recorded, even though it may not have been preventable. Many fleets have these types of incidents counting against them simply because a DataQ request through the CPDP was not submitted.
Understanding DOT recordable crashes
The first step to lowering a crash BASIC score is determining what types of collisions count against a company’s CSA score. Not all fleet accidents affect this score—only those classified as DOT recordable. A crash is considered DOT recordable if it meets any of the following criteria:
- A vehicle was towed from the scene
- A fatality occurred
- A person was injured and required immediate medical treatment away from the crash scene (e.g., transported to a hospital by ambulance or other means)
Incidents such as striking a pole in a warehouse or minor fender benders that do not meet these criteria are not considered DOT recordable. While non-recordable crashes may still impact liability, litigation, and insurance premiums, they do not count toward crash BASIC scores.
Identifying crashes eligible for review
Once an incident is confirmed as a DOT recordable crash, the next step is determining if it qualifies for a non-preventability challenge under the FMCSA’s CPDP program. Eligible crashes include:
- The truck was struck in the rear or on the side at the rear
- The other vehicle was driving in the wrong direction
- The other vehicle was making a U-turn or an illegal turn
- The truck was struck while parked or legally stopped
- The other driver was lawfully deemed under the influence of drugs or alcohol
- The other driver experienced a medical emergency, fell asleep, or was distracted
- The truck was damaged due to cargo, equipment, debris, or infrastructure failure
- The truck struck an animal (excluding crashes caused by attempting to avoid an animal)
- The other party was attempting suicide
- Other rare or unusual circumstances
Best practices for submitting a DataQ challenge
When submitting a DataQ request for the CPDP program, it is important to clearly articulate how the crash fits into one of the eligible categories. Providing thorough and precise documentation increases the chances of a successful challenge. Ensuring a fleet has a strong safety culture of documenting incidents properly, staying organized with documentation, and is properly trained on compliance and CPDP criteria can ensure the best outcomes for submitted requests.
Getting ahead of the crash BASICs score
Navigating the CPDP process can be complex, but with expert guidance and the right safety tools, fleets can significantly improve their chances of a favorable outcome. A knowledgeable fleet safety team can provide comprehensive support throughout the process. They assist in reviewing crashes, identifying eligibility, and crafting effective DataQ submissions to ensure that each case is handled with precision. By leveraging industry expertise, fleets can challenge inaccurate data, correct discrepancies, and strengthen their safety record. This proactive approach not only helps achieve a more favorable crash BASIC score but also enhances overall fleet safety, compliance, and reputation.
To learn more about how Nirvana’s fleet safety team provides support in reviewing crashes, identifying eligibility, and crafting effective DataQ submissions, visit nirvanatech.com.
The crash BASIC score–specifically a high score–can have serious consequences for fleets, impacting insurance rates, compliance, and overall business reputation. However, not all recorded crashes are truly preventable. The FMCSA’s Crash Preventability Determination Program (CPDP) offers a way for fleets to challenge certain crash records and potentially lower their crash BASIC scores. Understanding how this program works and taking proactive steps can help fleets maintain a more accurate safety record and avoid unnecessary penalties.
The impact of high crash BASIC scores for fleets
A fleet’s crash BASIC score may seem disproportionately high compared to other CSA BASICs. While some fleets have high scores due to preventable crashes, others may have inflated scores because they have not submitted DataQs for crashes that could be deemed non-preventable.
A common example is when a vehicle strikes the back of a commercial truck while it is legally stopped in traffic. If injuries occur or a vehicle needs to be towed, the crash is recorded, even though it may not have been preventable. Many fleets have these types of incidents counting against them simply because a DataQ request through the CPDP was not submitted.
Understanding DOT recordable crashes
The first step to lowering a crash BASIC score is determining what types of collisions count against a company’s CSA score. Not all fleet accidents affect this score—only those classified as DOT recordable. A crash is considered DOT recordable if it meets any of the following criteria:
- A vehicle was towed from the scene
- A fatality occurred
- A person was injured and required immediate medical treatment away from the crash scene (e.g., transported to a hospital by ambulance or other means)
Incidents such as striking a pole in a warehouse or minor fender benders that do not meet these criteria are not considered DOT recordable. While non-recordable crashes may still impact liability, litigation, and insurance premiums, they do not count toward crash BASIC scores.
Identifying crashes eligible for review
Once an incident is confirmed as a DOT recordable crash, the next step is determining if it qualifies for a non-preventability challenge under the FMCSA’s CPDP program. Eligible crashes include:
- The truck was struck in the rear or on the side at the rear
- The other vehicle was driving in the wrong direction
- The other vehicle was making a U-turn or an illegal turn
- The truck was struck while parked or legally stopped
- The other driver was lawfully deemed under the influence of drugs or alcohol
- The other driver experienced a medical emergency, fell asleep, or was distracted
- The truck was damaged due to cargo, equipment, debris, or infrastructure failure
- The truck struck an animal (excluding crashes caused by attempting to avoid an animal)
- The other party was attempting suicide
- Other rare or unusual circumstances
Best practices for submitting a DataQ challenge
When submitting a DataQ request for the CPDP program, it is important to clearly articulate how the crash fits into one of the eligible categories. Providing thorough and precise documentation increases the chances of a successful challenge. Ensuring a fleet has a strong safety culture of documenting incidents properly, staying organized with documentation, and is properly trained on compliance and CPDP criteria can ensure the best outcomes for submitted requests.
Getting ahead of the crash BASICs score
Navigating the CPDP process can be complex, but with expert guidance and the right safety tools, fleets can significantly improve their chances of a favorable outcome. A knowledgeable fleet safety team can provide comprehensive support throughout the process. They assist in reviewing crashes, identifying eligibility, and crafting effective DataQ submissions to ensure that each case is handled with precision. By leveraging industry expertise, fleets can challenge inaccurate data, correct discrepancies, and strengthen their safety record. This proactive approach not only helps achieve a more favorable crash BASIC score but also enhances overall fleet safety, compliance, and reputation.
To learn more about how Nirvana’s fleet safety team provides support in reviewing crashes, identifying eligibility, and crafting effective DataQ submissions, visit nirvanatech.com.
