2014 MERCEDES-BENZ SPRINTER 3500 — Problems, Recalls & Safety Data

THE FOLLOWING HAS BEEN SENT TO MERCEDES CORPORATE CUSTOMER SERVICE All of the following has started happening since an exhaust recall was done by Mercedes. In September 2022, we were driving cross country to Denver Colorado and enough codes piled up in the background that we went into limp mode in the middle of 70 MPH highway traffic. This happened without warning and was an extreme safety concern. But I was lucky to be near an exit and already in the right lane. I reset these codes and finished going to Denver the next day. The two Sprinter dealers in Denver were backlogged several weeks; so we spent over $600 trying to troubleshoot the issues with Colorado Fleetworks, a qualified Sprinter specialist. He checked codes too; ran other diagnostics; replaced the fuel filter and air filter even though they had been done only 10,000 miles earlier; and performed a forced DPF regeneration. He also replaced the DPF pressure sensor. This work did not help change the daily multiple code problems. We had to reset them every day coming back from our trip. When we returned home we took it to the dealer. They confirmed the codes, reset them, and test drove it 25 miles. Since codes didn't return, they said, "There is nothing we can do if we don't witness active codes." I said, "How active do they have to be? I will have codes in the next 20 to 30 miles like I do every day I drive it." These never happened in the 6 years prior to the recall wok. Either the programming is confused, some of the new sensors are faulty, or something. A totally separate problem is the faulty factory crimps on the connector of the rail pressure sensor. This is a known defect; and we've had the exact same symptoms and code as noted in Xentry TSB MC-10135520-9999. The engine has actually cut off when turning into traffic a few times. This is an extreme safety concern.

THE FOLLOWING HAS BEEN SENT TO MERCEDES CORPORATE CUSTOMER SERVICE All of the following has started happening since an exhaust recall was done by Mercedes. In September 2022, we were driving cross country to Denver Colorado and enough codes piled up in the background that we went into limp mode in the middle of 70 MPH highway traffic. This happened without warning and was an extreme safety concern. But I was lucky to be near an exit and already in the right lane. I reset these codes and finished going to Denver the next day. The two Sprinter dealers in Denver were backlogged several weeks; so we spent over $600 trying to troubleshoot the issues with Colorado Fleetworks, a qualified Sprinter specialist. He checked codes too; ran other diagnostics; replaced the fuel filter and air filter even though they had been done only 10,000 miles earlier; and performed a forced DPF regeneration. He also replaced the DPF pressure sensor. This work did not help change the daily multiple code problems. We had to reset them every day coming back from our trip. When we returned home we took it to the dealer. They confirmed the codes, reset them, and test drove it 25 miles. Since codes didn't return, they said, "There is nothing we can do if we don't witness active codes." I said, "How active do they have to be? I will have codes in the next 20 to 30 miles like I do every day I drive it." These never happened in the 6 years prior to the recall wok. Either the programming is confused, some of the new sensors are faulty, or something. A totally separate problem is the faulty factory crimps on the connector of the rail pressure sensor. This is a known defect; and we've had the exact same symptoms and code as noted in Xentry TSB MC-10135520-9999. The engine has actually cut off when turning into traffic a few times. This is an extreme safety concern.

THE FOLLOWING HAS BEEN SENT TO MERCEDES CORPORATE CUSTOMER SERVICE All of the following has started happening since an exhaust recall was done by Mercedes. In September 2022, we were driving cross country to Denver Colorado and enough codes piled up in the background that we went into limp mode in the middle of 70 MPH highway traffic. This happened without warning and was an extreme safety concern. But I was lucky to be near an exit and already in the right lane. I reset these codes and finished going to Denver the next day. The two Sprinter dealers in Denver were backlogged several weeks; so we spent over $600 trying to troubleshoot the issues with Colorado Fleetworks, a qualified Sprinter specialist. He checked codes too; ran other diagnostics; replaced the fuel filter and air filter even though they had been done only 10,000 miles earlier; and performed a forced DPF regeneration. He also replaced the DPF pressure sensor. This work did not help change the daily multiple code problems. We had to reset them every day coming back from our trip. When we returned home we took it to the dealer. They confirmed the codes, reset them, and test drove it 25 miles. Since codes didn't return, they said, "There is nothing we can do if we don't witness active codes." I said, "How active do they have to be? I will have codes in the next 20 to 30 miles like I do every day I drive it." These never happened in the 6 years prior to the recall wok. Either the programming is confused, some of the new sensors are faulty, or something. A totally separate problem is the faulty factory crimps on the connector of the rail pressure sensor. This is a known defect; and we've had the exact same symptoms and code as noted in Xentry TSB MC-10135520-9999. The engine has actually cut off when turning into traffic a few times. This is an extreme safety concern.

received a recall for the ESP electronic stability control system inApril 2021, dealership made an appointment for May 2021. Then told me the reaper parts were not available, but would contact me asp, . Today, August 26th I checked to see why no notification, was told thy had the parts, but could not get to my project until later October. I told them that date would not work asm I was driving the vehicle to New York beginning October first. They failed to call me, and now put me at the back of the line for repairs. My notice from your office, dated August and received on the 18th go August suggests the time for repair would be one hour. My problem, related to their failure to notify, is I can not wait till late October. Any help?

The contact owns a 2014 Mercedes-Benz Sprinter 3500. The contact stated while driving 60 mph, the rear wheel speed sensor failed causing the transmission to inadvertently downshift. The contact stated that the abs warning light was illuminated. The vehicle was taken to a local dealer to be diagnosed. The mechanic determined that the rear wheel speed sensor needed to be replaced. The vehicle was repaired however, the failure recurred two years later. The contact was relating the failure to NHTSA campaign number: 21V042000 (Electronic Stability Control). The manufacturer was not informed of the failure. The failure mileage was approximately 28,000.