Five problems related to engine cooling system have been reported for the 2010 Dodge Ram 3500. The most recently reported issues are listed below.
The contact owns a 2010 Dodge Ram 3500. The contact received notification of NHTSA campaign number: 14v635000 (engine and engine cooling, fuel system, diesel); however, the part needed to repair the vehicle was unavailable. The contact stated that the manufacturer exceeded a reasonable amount of time for the recall repair. The manufacturer was notified of the issue. The contact had not experienced a failure.
The contact owns a 2010 Dodge Ram 3500. The contact received a notification for NHTSA campaign number: 14v635000 (engine and engine cooling, fuel system, diesel) and stated that the part needed was unavailable to repair the vehicle. The dealer was unable to inform when the part would become available. The manufacturer was notified of the issue. The contact had not experienced a failure.
The contact owns a 2010 Dodge Ram 3500. The contact received a notification for NHTSA campaign number: 14v635000 (engine and engine cooling, fuel system, diesel) and stated that the part needed was unavailable to repair the vehicle. The dealer was unable to inform when the part would become available. The manufacturer was not notified of the issue. The contact had not experienced a failure.
The contact owns a 2010 Dodge Ram 3500. The contact received notification of NHTSA campaign number: 14v635000 (engine and engine cooling, fuel system, diesel). However, the part needed to do the repair was unavailable. The contact stated that the manufacturer exceeded a reasonable amount of time for the recall repair. The manufacturer was made aware of the issue. The contact had not experienced a failure.
The contact owns a 2010 Dodge Ram 3500. The contact received a recall notification for NHTSA campaign number: 14v635000 (engine and engine cooling, fuel system, diesel) and stated that the part needed was unavailable to perform the recall repair. The manufacturer was notified of the issue. The contact had not experienced a failure.