It pops up the symbol below on the QC when you overspeed: When you're driving along at top speed and that pops up on the QC for no apparent reason, it doesn't take a genius to figure out that it's not popping up because of overrevving or intertrip idle or you logging out. There's only one other reason it would pop up while you're driving. And it does make a "thud" sounding beep.
If a Swift driver is following to close its either a construction zone or traffic accident but on open road the vehicle ahead must be doing the minimum speed limit they need to change their name from Swift to No So Fast Trucking
Bottom line is, know what your truck is doing at all times. It's part of keeping control of it. There is only one way for a Swift truck to get an overspeed: by letting it "float" down a hill. In September, Swift made it very clear what the speed policy is and what would happen if a driver got too many. Additionally, overspeed severity was weighted by how far over the driver went. To be fired after two overspeeds meant those drivers were floating at least 6mph over their governors. For company guys, that means they were going 68mph. They were not in control of their trucks. With the clarity of the speed policy, the timing, while unfortunate, is not the fault of the company. And yes, I do know what it's like to lose a job just before Christmas.
It is when you're supposed to maintain 62 and you have no throttle left. Part of controling the vehicle is controlling its speed. Did you notice I was specifying Swift company trucks?
Oh I agree with you a 100%. Their is alot more to the story, I saw all the points and how he aquired them, lets just say it was the straw that broke the camels back. The speed thing was over 70 for 1 minute x2
