fb-pixel Customers Still Battling With Ford Over “Death Wobble” Issue – Why Isn’t There a Recall? - Speed Society
Shop All

Customers Still Battling With Ford Over “Death Wobble” Issue – Why Isn’t There a Recall?

When someone purchases a vehicle, they shouldn’t have to expect to sink money into it to fix things that weren’t right to begin with. This is why we so commonly see recalls so that these sorts of issues can be remedied. Don’t get us wrong, mistakes happen. It’s how those shortcomings are handled that truly define a big portion of an automaker’s character.

Sometimes, though, it seems like there is a disconnect between an automaker and its products. Sometimes, there could be an issue that automakers don’t seem to acknowledge for one reason or another. In these situations, there’s a good chance that the court of law is brought into the picture.

This brings us to Ford’s “Death Wobble.”


The “Death Wobble,” as it’s commonly called, is a situation where a vehicle’s steering wheel shakes violently to the point where the vehicle can’t be driven. Most commonly, it’s attributed to a suspension or steering component. Most of the time, though, it seems to be related to older vehicles. In any situation, it’s a rather unpleasant situation and definitely one that could be dangerous.

In this particular case, it isn’t older vehicles that have been affected. Instead, newer Ford pickup trucks seem to be the victims of the death wobble. Right out of the box, owners complain of the violent shaking on their 2005-2019 F-250s and F-350s.

So far, there have been no deaths associated with the issue. However, 12 accidents or injuries have been reported along with 1200+ filed complaints to the NHSTA. With that in mind, a class-action lawsuit has been opened up against Ford to try to get to the bottom of things.

The suit claims that the defect is linked to “Abnormal wear and/or loosening of the track bar bushing, damper bracket, ball joints, control arms, shocks and/or struts.”

As of the posting of this article on May 13, 2020, we couldn’t find any information related to a resolution of the issue.