- Stellantis was notified of a potential issue more than 12 months ago.
- A total of 211,581 vehicles are impacted by this defect.
- Dealers and owners of affected models will be alerted to the recall on July 26.
More than 211,000 Ram and Dodge models have been recalled in the United States due to a fault with the ABS system, which could disable the electronic stability control (ESC).
In the recall notice, Stellantis revealed that a software malfunction may prompt the ABS control module to disable the ESC. The company hasn’t gone into detail about this software fault, but notes that the ESC may not work under certain conditions. That increases the risk of a crash and is obviously something that needs to be rectified.
Read: Jeep And Ram Recall 12 Vehicles Over Rearview Camera And ESC Glitches
A total of 211,581 vehicles are involved in the recall. These include 157,890 Ram 2500 models built during the 2022 model year from April 14, 2021, to December 7, 2022, and 53,167 Dodge Durangos manufactured from August 23, 2021, to December 9, 2022, for the 2022 model year. The recall also impacts 524 examples of the 2022 Ram 3500 Cab Chassis built from April 21, 2021, to November 25, 2022.
The carmaker’s Technical Safety and Regulatory Compliance department was notified of a potential issue related to the ABS control module software on March 2, 2023. Over the following eight months, they investigated the issue and looked at warranty data, field records, and customer assistance records.
Between November 2023, and March 2024, the issue was reviewed and in late April, it was concluded that a vehicle build issue on certain vehicles could cause the ESC to be disabled, meaning vehicles do not comply with Federal Motor Vehicle Safety Standards that require the ESC to work during all phases of driving.
Both dealers and owners of impacted vehicles will be notified of the recall from July 26, 2024. The ABS control module software will be updated free of charge, and the car manufacturer will reimburse any owners who have paid to have the issue fixed.
