Recent Comments

Operator tops hill, slams jackknifed flatbedder — Could he have prevented it?

| March 07, 2014

Pg108_PreventableOrNotDrawingTruck driver John Doe was making his way through a bad spring snow storm on an empty four-lane highway, hauling a big load of parkas. 

The posted speed limit was 65, but the conditions had Doe traveling at just 35 mph, but behind him a flatbed driver coming up fast. 

Related

Driver slams tree in the road in heavy snow — Could trucker have prevented it?

Truck driver John Doe was caught in a bad blizzard on a dark road in the middle of South Dakota when he suddenly came up ...

The flatbedder then zipped past Doe in the left lane disappeared into the storm ahead. Shortly after, the snow eased some and visibility improved, so Doe took his speed up to 55. 

Doe then topped a hill and proceeded down a long, moderately graded decline that curved to the right. 

Suddenly, halfway down, there was the flatbed that had passed him jackknifed and stretching across the entirety of the highway. The road was glazed with ice, and Doe could hardly slow his rig down, but he was able to steer toward the rear of the flatbed trailer.

He struck the trailer, pushing it aside, then slid to a stop. 

Shortly thereafter, he received a preventable-accident letter from his safety director. The National Safety Council Accident Review Committee made the final judgment in the case, ruling against Doe. The committee ruled Doe was blindly driving down the hill and was going faster than what the conditions warranted.

This was an adaptation of Overdrive sister site CCJ‘s “Preventable or not?” series, which appears regularly on CCJdigital.com.

Cummins Redefining Tour – Driver Reactions and Future Tour Dates

Notice: Overdrive is transitioning to a new comment platform due to technical problems with the former commenting system. The new commenting system is now live. We are currently in the process of moving all of the comments from the old system into the new system. We appreciate your patience in the meantime.
0 comments