2025 Tesla Model Y Recalls, Ratings & Complaints

Incident: October 22, 2026 · Filed: October 22, 2026

Subject: Multiple Recurring Issues — 2025 Tesla Model Y Long Range AWD I am submitting this complaint regarding multiple quality and potential safety-related issues with my 2025 Tesla Model Y Long Range Dual Motor AWD, purchased new in January 2025. 1. Persistent HVAC moldy/musty odor The vehicle develops a pronounced moldy or musty odor from the HVAC system, particularly in hot, humid, or rainy conditions. This raises concerns about possible moisture accumulation, microbial growth, or an underlying HVAC system defect. I have attempted to resolve this issue through Tesla service, including communications with the Randolph and Princeton service centers. I have experienced repeated scheduling difficulties and have not received a clear diagnosis or satisfactory resolution. I also investigated Tesla technical service information concerning HVAC inlet ductwork, including bulletin SB-26-18-002, but have not obtained a satisfactory determination regarding the applicable components on my vehicle. 2. Windshield residue affecting the front camera area I have also experienced an issue involving residue or plastic off-gassing contamination on the windshield in the area of the forward-facing camera system. This raises concerns about visibility through the camera's viewing area and the potential impact on camera-based driver-assistance functions. I have sought clarification regarding cleaning and inspection of this area. I would like this issue evaluated to determine whether the contamination is associated with an underlying vehicle material or manufacturing problem and whether it could interfere with the proper operation of safety-related camera systems. 3. Rear hatch seal and wind noise The vehicle also has a rear hatch area wind-noise issue that may be related to the hatch seal or its fitment. I am concerned about whether the seal is properly installed and functioning as intended. I would like the issue evaluated to determine whether it reflects a component, alignment

Incident: October 22, 2026 · Filed: October 22, 2026

The contact stated that while seated in a 2025 Tesla Model Y taxi cab driving 25 MPH, the vehicle failed to yield or stop while pedestrians were nearby the vehicle. The contact stated that the failure had occurred near a school zone. The contact expressed concerns that the vehicle posed a safety risk while driving in school zones or other areas with pedestrian traffic due to the failure to yield or stop for pedestrians. The contact stated that the manufacturer should account for high-traffic areas when manufacturing self-driving vehicles.

Incident: October 16, 2026 · Filed: October 22, 2026

While operating my vehicle with Full Self-Driving (Supervised) engaged on Friday, October 16 at 5:12 pm, the vehicle suffered an sudden loss of vehicle control, resulting in a full spinout. ​Road & Environmental Conditions: Wet roads Approximate Speed: 76 mph Incident Details: Without warning or driver steering/accelerator input, the vehicle's automated driving system lost traction, causing the vehicle to spin out of the lane. I was forced to intervene to bring the car to a complete stop and prevent a collision.

Incident: October 14, 2026 · Filed: October 14, 2026

Since a 2026 over-the-air software update, every time I disengage Tesla Full Self-Driving (Supervised) while driving, on any road and at any speed, the center touchscreen shows a large pop-up titled "Why did you intervene?" with four buttons (Navigation, Parking, Critical, Other) and a voice-message option. It covers about a third of the display, including navigation, media controls and, during parking, the camera view. It does not clear on its own while driving; it stays until the driver taps an option or shifts into Park. Photos attached. Disengagements happen at the most demanding moments: correcting the system, avoiding a hazard, merging or parking. This prompt draws the driver's eyes and hand to the touchscreen at exactly those moments, on every disengagement and several times per drive. I believe this creates a foreseeable visual-manual distraction risk and conflicts with NHTSA's Visual-Manual Driver Distraction Guidelines. This is a particular safety concern because I regularly drive this vehicle with young children on board. Any distraction at the moment I take over from FSD puts them at risk. There is no setting to disable this prompt; the only way to avoid it is to stop using FSD, which we paid for. The car is collecting training feedback from drivers in real time at the expense of attention to the road. I request that NHTSA review this and that Tesla make the prompt dismissible, defer it until the vehicle is parked, or make it optional. Reproducible on every FSD disengagement; not inspected by a dealer. Vehicle software 2026.27.11, FSD (Supervised) v14.3.10.

Incident: February 17, 2026 · Filed: October 13, 2026

On XXX, I was driving my 2025 Tesla Model Y with Full Self-Driving (Supervised) engaged. While merging onto [XXX] in [XXX], the vehicle veered and crashed into the guardrail. I was not controlling the vehicle at the time — FSD (Supervised) was in control. Both of my child passengers were injured; one suffered a wrist fracture. A police report was filed at the scene. The vehicle was totaled in the crash and has not been driven since. Vehicle software at the time of the crash: 2025.45.9.1; Full Self-Driving (Supervised) v14.2.2.4. After the crash, I asked Tesla for the vehicle's driving data/logs to confirm that FSD was engaged at the time of the crash. Tesla did not provide the data. I am concerned that Full Self-Driving (Supervised) failed to safely execute a highway merge maneuver and drove the vehicle into the guardrail, resulting in injuries to my children. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

Incident: October 8, 2026 · Filed: October 8, 2026

On 10/08/2026, while Full Self-Driving (Supervised) software v14.3.10 was engaged in an underground parking garage, the vehicle failed to stop when it should have, causing the left-front bumper to scrape against a concrete pillar. The driver was supervising at the time. No injuries; cosmetic damage to the left-front bumper only.

Incident: October 1, 2026 · Filed: October 7, 2026

On October 1, 2026, at approximately 5:40 p.m. in the Marina Square Center parking lot in San Leandro, California, the powered rear trunk of my 2025 Tesla Model Y popped up slightly but failed to fully open. I repeatedly attempted to open it using both the touchscreen and the physical trunk button without success. When I reached underneath to manually lift it, the trunk unexpectedly began closing under power and trapped both of my hands, injuring six fingers. I remained trapped for several minutes and had to call for help; two bystanders assisted, and repeated electronic and manual attempts were required to free me. Nearly one week later, visible wounds and soft-tissue injuries remain, and I experience intermittent numbness in my fingertips. I have not yet received a medical evaluation. The trunk still does not open reliably and sometimes requires a second activation. I reported the incident and submitted injury photos to Tesla Service, but Tesla declined to proceed with an in-person inspection, said I did not need to attend my scheduled appointment, and has not confirmed whether the vehicle logs were reviewed. I am reporting an unexpected powered-closure action on a trunk that failed to open, which trapped both of the operator's hands and required rescue by bystanders.

Incident: October 2, 2026 · Filed: October 3, 2026

On [XXX], at about [XXX], I was driving my 2025 Tesla Model Y with Full Self-Driving (Supervised) engaged. I was on [XXX] in Matthews, NC, heading toward Mint Hill, at about [XXX]. There were no vehicles, pedestrians or obstacles ahead of me. With no apparent reason and no warning or alert, the vehicle suddenly braked as hard as possible. It slowed from about 49 mph to 32 mph within roughly one second, which averages about 0.8 g. I took over from FSD and submitted feedback to Tesla marking the event as critical. It was nighttime and the weather was clear. Fortunately no vehicle was behind me, but if one had been, a rear-end collision would have been likely. The car was running software 2026.27.11 with FSD (Supervised) v14.3.10. I have dashcam footage of the event. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

Incident: September 29, 2026 · Filed: September 29, 2026

When in Full Self Drive (FSD), the car turns (every time) west on [XXX] in [XXX] when existing the XXX High School front driveway ([XXX]). This is a one way street where all traffic is directed east, so having it drive west means it's driving the wrong way on a one way road. Additionally, when then traversing the perimeter of the school and then traveling east of the [XXX]/[XXX] intersection on [XXX], the car will drive through the parallel parking spaces instead of the main lane. Both of these are critical safety issues and if the car were fully automated or perhaps a CyberCab, this could be extremely dangerous. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

Incident: September 10, 2026 · Filed: September 29, 2026

When self parking in a drive way, Tesla Y hit another car. There was more than enough space on the driveway for 2+ cars. We did the same self-parking tens times before. Tesla generated no alarms after collision. It didn’t stop after colliding with another car. I brought the Tesla to Irvine Tesla dealer and requested that the dealer checke cameras and software. The agents refused. They only checked if the car still self parks. The claimed as no alarms were generated during collision, they are not going to check cameras or anything else. The gave me no paperwork at all. I believe it’s a serious precedent that may affect thousands of Tesla owners and compromises their safety.