At OOIDA’s request, FMCSA adds category to list of crash types
The Federal Motor Carrier Safety Administration listened to comments from OOIDA and added “rare or unusual” to its list of crash types in its Crash Preventability Determination Program.
The agency announced in May that it was restarting and expanding the program.
As part of the expansion, FMCSA is including new eligible crash types to the program. FMCSA’s notice about the program published in the Federal Register on May 6.
The crash types
- Rear collisions.
- Wrong direction or illegal turns.
- Parked or legally stopped.
- Failure of the other vehicle to stop.
- Under the influence.
- Medical issues, falling asleep or distracted driving.
- Cargo/equipment/debris or infrastructure failure.
- Animal strike.
- Rare or unusual types of crashes.
Under the program, commercial motor vehicle drivers with an eligible crash that occurred on or after Aug. 1, 2019, can submit a Request for Data Review with the required police accident report and other supporting documents, photos or videos through the agency’s DataQs website.
In July 2017, FMCSA announced a program to evaluate the preventability of eight categories of crashes through submissions of Requests for Data Review to its national data correction system known as DataQs. By August, FMCSA announced a streamlined process.
In October, OOIDA told FMCSA in formal comments that crashes deemed “not preventable” should not be counted against truck drivers or motor carriers.
The Association supported FMCSA’s proposal, saying that nonpreventable crashes have unnecessarily discredited safety ratings of drivers and motor carriers “for far too long.”
OOIDA also asked the agency to add a category.
“We believe a category covering ‘rare or unusual’ cases would be a practical addition,” OOIDA wrote. “This category would cover unique scenarios, such as a September 2019 incident, where a skydiver caused a truck crash in Northern California.”
FMCSA said it listened to the public’s feedback based off the August 2019 proposal and would exclude crashes with nonpreventable determinations from the algorithm. LL