2024 Mercedes-Benz EQE 350+

The contact owns a 2024 Mercedes-Benz EQE 350+. The contact stated that while her husband was driving at 75 MPH, the panoramic sunroof suddenly shattered without warning, producing a loud booming sound. The contact's husband pulled over and inspected the vehicle before driving back to the residence. There were no other vehicles or objects nearby to cause external impact. The vehicle was taken to a dealer, where a repair estimate was provided. The vehicle was not repaired. The manufacturer was not notified of the failure. The failure mileage was approximately 37,000.

NHTSA ID

11748503

Incident

Jul 6, 2026

Mileage

37,000 mi

Component/system that malfunctioned: The braking and acceleration system, including the collision assistance (driver-assistance/automatic braking) feature. The vehicle is available for inspection upon request. How safety was put at risk: The car lags when braking and at times accelerates unexpectedly. On one occasion, the collision assistance system—which is designed to brake—instead caused the vehicle to accelerate. The most dangerous incident occurred when the car accelerated on its own into an intersection, nearly causing a collision. Reproduced/confirmed by a dealer or service center: The vehicle was taken to the Mercedes-Benz dealer twice regarding this issue. On both visits, the dealer reported that they found no problem. The fault has not been confirmed or reproduced by the dealer. Inspected by manufacturer, police, insurance or others: Inspected by the Mercedes-Benz dealer on two occasions (no fault found). UNKNOWN whether the manufacturer's engineering team, police, or insurance representatives have inspected the vehicle—to my knowledge, they have not. Warning lamps, messages, or symptoms prior to failure: UNKNOWN / none noticed. No warning lamps or dashboard messages were observed before or during these events. The symptoms (braking lag and unexpected acceleration) have been consistently noticed by all three drivers of the vehicle.

NHTSA ID

11741951

Incident

Jun 3, 2026

The vehicle stopped twice while being driven, with no apparent cause.

NHTSA ID

11720558

Incident

Feb 24, 2026

The vehicle experienced repeated electrical wiring harness damage in the lighting, tire and connector areas due to exposed and insufficiently protected wiring near socket terminations. On two separate service visits, authorized dealership technicians confirmed that rodents chewed through multiple exposed wires. The affected wiring involves critical electrical systems. The connectors lack adequate shielding, loom, or protective insulation at exposed termination points. The insulation ends before the connector, leaving conductors vulnerable to environmental exposure and rodent access. Warning indicators illuminated on the dashboard, and the vehicle required dealer repair on both occasions. The damaged wiring was inspected and confirmed by certified technicians and is available for inspection upon request. This condition presents a significant safety risk. If a rodent partially damages a wire connected to braking systems, steering systems, high-voltage components, sensors, or engine control systems, failure could occur while the vehicle is in motion. A sudden loss of power, interruption of propulsion, or malfunction of safety systems at highway speeds could increase the risk of a crash. Because this is an electric vehicle, sudden electrical interruption may result in complete loss of propulsion or charging capability. If such failure occurs in remote areas, at night, or in extreme weather conditions, occupants could be left stranded in potentially hazardous situations. This issue has occurred more than once, and no permanent preventive solution has been provided. The design appears to leave critical wiring insufficiently protected from foreseeable environmental and rodent exposure, creating an ongoing safety hazard. I request review of whether the wiring design provides adequate protection for safety-related electrical systems.

NHTSA ID

11718164

Incident

Oct 23, 2025

The car made a sudden and very hard brake in the middle of the street at around 40 - 50 miles per hour, on a empty road.

NHTSA ID

11689289

Incident

Sep 20, 2025

Twice, the car has autonomously braked when there was no threat to the car. The first time we were subsequently rear ended, though fortunately at low speed. There was cosmetic damage to the bumpers of both cars and the occupants were shaken up, but not injured. The second time the were driving at about 35mph when the car slammed on the brakes. Fortunately the following vehicle was not close and there was no collision. The occupants were again shaken up, but not injured. The "braking assistance" can be disabled, but only for the current trip. It is automatically reenabled the next time the car is started.

NHTSA ID

11684105

Incident

Jul 19, 2025

I was driving from Fresno to Lake Tahoe stopped in Manteca to charge my car at the Tesla SC as I was reversing into the charge spot the car suddenly stopped a message appeared “speed severely restricted “ I tapped the gas pedal and no response within a millisecond the car accelerated in reverse at a high speed hitting the pole in front of the Supercharger resulting in damage to the backend of the eqe

NHTSA ID

11677127

Incident

Jul 24, 2025

On [XXX] around [XXX] while driving my 2024 Mercedes-Benz EQE350 [XXX] near Santa Clarita, CA, I experienced a flat tire due to a 4 mm puncture in the center tread of the rear driver's side tire. I immediately contacted Mercedes Me customer support , and the representative advised me that my vehicle's run-flat tire system would allow me to continue driving up to 50 miles, as long as I stayed under 50 mph. I followed this guidance very cautiously, driving under 30 mph. Despite this, the tire completely blew out in less than10 miles. The road conditions were normal, the tire was in good condition prior to the incident, and weather was mild. This incident endangered my safety and that of my wife and our toddler, who were in the vehicle with me at the time and was extremely frightened by the sudden blowout. I believe the run-flat system failed to perform as expected and/or the advice I received from Mercedes Me was unsafe and caused more damage to my vehicle and put my family in more danger. I am submitting this report in case other Mercedes EQE owners experience similar failures. I request that NHTSA investigate whether this represents a design flaw or safety hazard in the vehicle's tire/run-flat system? Tire Spec: Good year 265 40 21 105 H MOES INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

NHTSA ID

11650193

Incident

Mar 23, 2025

Complaint During part of the steering movement, it feels heavier or more difficult to steer in the same spot every time. OR Rattling, humming, dry sliding/gravel noise from the electric steering system when steering (see attachment). Complaint does not impact the ability to safely steer or control the vehicle. Cause Ball screw drive (KGT) of electric steering damaged by: 1. External force due to: ‑ Hitting the curb/posts with the front wheels. ‑ Driving over obstacles (e.g. pothole/ threshold/ speed bump/ gully) at an inappropriate speed. 2. Corrosion/ water ingress through a damaged boot (see attachment). ‑ Cracks (1) ‑ High pressure cleaner (2) ‑ Animal bite (3) See various examples listed in the attachments for examples of outside influence. Remedy Remove boot clamps closest to steering gear housing on both left and right (as seen in "Steering Rack Boot Clamp Location"). Pull back boot and inspect for rust, broken end stops, water, or any other anomalies. Replace electric steering. Note: Steering gears replaced due to outside influence or damage must not be claimed under warranty!

Complaint Tailgate opens unintentionally. Cause Accidental or unnoticed activation of the button to open the tailgate on the vehicle key. EXAMPLE: when stored in trouser pocket, handbag etc. Remedy As of the 6th generation, the vehicle key can be recoded so that the tailgate no longer opens as a result of a long press on the button, but by double‑clicking on the button instead. This reduces the likelihood of the button being activated accidentally or unintentionally. The recoding can be carried out as follows: 1. Add SA Code O19 into VeDoc (O for Oscar, not "zero") • an XSS ticket may be necessary to add the SA code 2. Perform SCN coding of EIS N73 control unit 3. Deactivate the vehicle key (a successful deactivation is indicated by the LED lighting up 2x briefly and then 1x for a long period). 4. Place the vehicle key in the storage compartment on the key symbol and turn on the ignition. IMPORTANT: all other vehicle keys must be outside the recognition range of the vehicle when doing this! Perform steps 3 and 4 successively for all vehicle keys. Notes: 6th, 7th and 8th generation keys can be deactivated as follows: Up to modification year 22/1 by double clicking the "Lock button" As of modification year 22/1, by press and holding the “Lock button", then double‑click the “Unlock button" at the same time. On model series 167, the storage compartment with the key symbol is located in the armrest. The SCN coding from the EZS is only transferred correctly to the vehicle key under the following conditions: Only one vehicle key is located in the vehicle, this key has been deactivated and it is positioned on the marking in the storage compartment for the data transfer. The costs for this adaptation are to be borne by the customer. For the newer BR 174, 178, 244, 248, 520, and 540, a software update must be initiated, as there is no way to perform SCN coding.

Complaint Traffic sign symbol for "Traffic Sign Assist" is blinking in instrument cluster without obvious cause usually with one of the following scenarios: • Flashing without a speed limit ("‑ ‑"). • Flashing when current vehicle speed is under speed limit. • Flashing between US speed limit symbol and European speed limit symbol. NOTE: • Verify that the concern falls under one of the attachment videos. If not, then it is outside of the scope of this LI. • This also does not cover "Traffic Sign Inoperative" messages on the instrument cluster. Cause There are two identified reasons for this concern: 1. Country code information stored incorrectly at a particular geographic latitude range. 2. Incorrect reference data when the vehicle is started and a GPS signal is not immediately available. Remedy Update head unit software to latest version and the re‑check function in the same location. If vehicle is still exhibiting one of the symptoms as described exactly as in the complaint section or as shown in the video attachments, open a TIPS case to the Body/Chassis/Entertainment inbox with the following: • Video of the concern. • Exact location (latitude and longitude is best)

Complaint The following most common complaints may be observed: • Brief connectivity interruptions when using Apple CarPlay over Wi-Fi • Audio cuts out • Device not recognized • No operation possible Cause There are multiple possible causes for an iPhone disconnecting from a vehicle’s head unit while using Apple CarPlay. These include hardware, software, and environmental factors: Environmental Interference External Sources: • Passing under toll bridges, driving near airports, or areas with heavy electronic interference (e.g., as described in LI82.85-P-076157) can cause connection drops. Cellular Networks: • Interference from nearby cell towers operating on similar frequencies (usually 2.4GHz or 5GHz) can disrupt the signal. Storage Location: • Keeping your phone in a handbag or surrounded by other objects inside the vehicle can create physical or electronic interference. Device and Software Issues Head Unit Software/Hardware: • Outdated firmware, bugs, or hardware faults in the vehicle’s head unit can prevent a stable connection. iPhone Software/Hardware: • Similar issues in the iPhone, including buggy iOS updates or hardware problems, may affect performance. Reset or Reboot:• Automatic rebooting or resetting of either the head unit or the iPhone will temporarily disrupt CarPlay. Connection and Settings Wired Connections: • Faulty Cable: A damaged or poor-quality USB cable can cause intermittent or total loss of connection. • USB Port Issues: Dust, debris, or physical damage in the USB port of either the head unit or the iPhone can also lead to disconnects. Wireless Connections: • Intermittent Bluetooth/Wi-Fi: Unstable wireless communication (Bluetooth/Wi-Fi) can frequently break the Car- Play connection. Power Management: • Battery Saver Mode: Enabling low power mode may restrict background processes, affecting CarPlay. • Vehicle’s Electrical System: Unstable power delivery from the car’s battery or electrical interruptions can cause the head unit to malfunction. Phone & App Configuration Phone Settings: • Incorrect or conflicting settings (especially Bluetooth or Wi-Fi) on your iPhone can interfere with the CarPlay link. • Third-Party Apps/Profiles: • Installed apps or configuration profiles may conflict with CarPlay’s operation. • Native apps are apple maps, apple music, audio books, apple news, podcasts, messages and phone. All other apps are considered third party apps. App Conflicts: • Running conflicting apps that require similar system resources as CarPlay can cause instability. Mobile Data Plan: • Streaming from online sources without sufficient mobile data can result in lost connectivity. Other Factors Heat & Overheating: • If either the phone or the head unit overheats, they may disable certain functions to prevent damage, leading to disconnection. User Actions: • Accidentally disconnecting the device in settings, or physically moving or bumping the phone or cable, may disrupt the connection. Remedy FUP6 (E605.8) software has been released for the following chassis: 118, 177, 243,247,206,254,167,294,295,296,223, 297. Flash available software for the head unit and test for function. The LI will be updated once available for the remaining chassis. If the complaint remains after the SW update please continue with the steps below. Guided Diagnostic Path for Apple CarPlay Connection Issues: Please follow the steps below to systematically diagnose and resolve CarPlay concerns:Update Devices: • Ensure the iPhone is updated to the latest available iOS version. • Ensure the vehicle’s head unit is updated to the latest software version available. Isolate the Issue: • Check whether the symptom persists with another iPhone running the latest iOS version. • Test both wireless and wired CarPlay connections: • Does the issue only occur with wireless CarPlay? • Does the wired connection to the phone function correctly? Further Troubleshooting Steps: • Reboot the iPhone. See attachment for further instructions.

Complaint 1. General Diagnostic Tips 2. One or More PARK Sensor Activations 3. Red Ring Around Vehicle 4. "Active Parking and Parking Assist Inoperative" on Instrument Cluster 5. Cameras 6. Other Park Topics. Cause Various root causes Remedy See attached diagnostic guide.

Complaint Customer Complaint: - AC charging is not possible. - The departure time, charging pause, location-based charging or target SOC limit is automatically set to 50% or to a random value in the Mercedes me application or in the charging settings on the head unit display. (Picture 1 & 3) - Incorrect notifications appear in the Mercedes me application for charging-related functions. (Picture 2) Related DTCs in quick test: No related fault codes (DTCs) are stored in the relevant control units. CPC3 - N127 (Drivetrain control unit) OBL223_GEN4 - N83/11 (Alternating current charger for high-voltage battery) DCB223 - N116/5 - Direct current charge connection unit (DCCU) Picture1 The target SOC limit is automatically set to 50% or any random values during charging. Picture 2 Incorrect notification Example “Unable to unlock charging cable. Picture 3 Incorrect settings of charge interruption or pause. (If applicable) Cause - The Customer shares their Mercedes me credentials (password) with a third-party application, for example, a wall box application. This causes the Mercedes Benz backend server to receive random requests to reset the maximum SOC, departure time, charging pause, etc. - Charging settings are set incorrectly, for example, incorrect departure time, charging program, charging interruption/ pause, etc. Remedy The remedies below may vary depending on the customer complaint. Refer to the remedy that best matches the customer complaint. Remedy 1: The target SOC limit is automatically set to 50% or to random values during charging. - Change the Mercedes me login password on the Mercedes me homepage. (My Account > Login and Security > Reset). (Refer to Annex 1). Previously granted authorizations should then be revoked so that the charging settings can no longer be changed by external applications. Advise customers not to share the new password again. - Are there any sub-users? If yes, revoke their rights and reassess the function. -If differences between the vehicle and the Mercedes me app are visible, a new synchronization is recommended. Turn off Digital Extras through the Mercedes me app or the MMCR portal, and then turn the services on again. Remedy 2: Incorrect notifications in the Mercedes me app for charging-related functions. - Restart synchronization between the app and backend. Turn off Digital Extras through the Mercedes me app or the MMCR portal, and then turn the services on again. (Refer to Annex 2) Remedy 3: Incorrect charge interruption or pause setting. - Perform a factory reset of the head unit (A26/17). (Home > Functions > System > Reset), or turn off/correct all charging settings. (Refer to Annex 3) Additional Information: (Good to know) The LED on the charging inlet or socket indicates whether charging is completed or paused. 1) If the target SOC is reached, the charging inlet LED lights up Blue/Green without flashing. 2) If charging is paused, the charging inlet LED lights up orange without flashing. Additionally, the head unit charging settings display a charging pause. Note: Do not replace any hardware components for these complaints. If the complaint cannot be solved, please contact via TIPS or CAC.