Consumer Complaint Detail

MERCEDES BENZ / S CLASS / 2003

Recalls
2 Injured
Investigations
0 Death
Complaints
No Fire
Components - Details
NHTSA Complaint Number: 006068607 Incident Date: Jun, 16 2006
Consumer's City: CHARLESTON Consumer's State: SC
Vehicle Transmission Type: Manufacturers Name: Mercedes-Benz USA, LLC
Model Name: S CLASS Model Year: 2003
Vehicle Involved in a Crash: No Component's Description: Latches/locks/linkages:trunk lid:lock
Vehicle Involved in a Fire: No Persons Injured: 2
Vehicle's VIN#: WDBNG84J53A Date added to File: May, 23 2021
Date Complaint Received: Jun, 18 2006 Complaint Type: IVOQ
Incident Reported To Police: No Purchase Date: -
Was Original Owner: No Anti-lock Brakes: No
Number of Cylinders: 0 Date of Manufacturer: -
Was Vehicle Towed: - Description of the Complaints: My 2003 mercedes s500 has twice electronically self-closed it's trunk on two separate users, on two separate occasions. this vehicle has been taken to two separate mercedes dealers for the problem. one of those dealers replaced a number of parts. despite doing so, the second occurrence (last night), left my other half in tears, pain, with a recess in her head and a headache. the electronic trunk lid has had instances where it does not open all the way, does not close all the way, or a combination of the two. then there is the more serious and i believe potentially life treating, unprovoked, unexplained and as yet un fixed electronic closing that has twice occurred when putting in or removing goods from the trunk. i would find it hard to believe that i am the only owner who has had such a problem. the metal trunk lid comes down with force striking directly on the top of an adults head. it is unknown what it would do to a non-adult. i have spoken to a representative for mercedes who states to her knowledge there is no problem and that they would be happy to get the car in and attempt to fix it, but can not guarantee they can. the first time it occurred, it hit me and nearly knocked me out. after bringing the car in i assumed it was fixed, however, after last night, it clearly is not. though i can not make it perform upon command, i have no reason to believe it will not occur again. *jb