Adaptive Cruise Control Problems of Tesla Model Y - part 1

The vehicle is experiencing an active, recurring safety hazard caused by a manufacturer software bug that triggers unprovoked alignment parameter and steering angle plausibility resets. This defect directly compromises the vehicle’s primary handling characteristics and stability control systems. This specific firmware vulnerability is officially documented and acknowledged by the manufacturer under Tesla internal toolbox article 8368100. The unprovoked resetting of steering and alignment parameters degrades the vehicle's driving stability, alters steering feedback, and can cause sudden, unexpected disengagements of advanced driver-assistance systems (autopilot/fsd). This sudden loss of driver assist functionality and changes to steering plausibility while operating at highway speeds pose a severe, immediate risk of a crash or loss of vehicle control. Tesla's standard remedy for this defect is a newer firmware deployment (branch . 32 or later). However, due to a severe firmware gap, the vehicle's automated over-the-air (ota) download architecture is corrupted, consistently freezing and failing mid-stream at precise milestones (50%, 67%, and 83%). While non-critical data packets (such as map and navigation updates) download successfully, the core safety-critical os update cannot be processed over the air. Tesla service has been formally notified of the active safety hazard and the corresponding internal technical article (toolbox article 8368100). Because the vehicle's automated ota path is blocked by a software-induced cache loop, a physical, local hardware tether via Tesla toolbox is required to bypass the download block. Tesla service has refused to perform this critical safety patch or tether the vehicle unless the consumer pays an out-of-pocket, mandatory "formal diagnostic fee. " forcing a consumer to pay a fee to resolve a documented, manufacturer-created code defect that compromises steering safety constitutes a failure to remediate a known safety hazard.

See all problems of the 2020 Tesla Model Y 🔎.

While driving on colorado state highways with traffic-aware cruise control (and/or autopilot) engaged, the vehicle repeatedly and unexpectedly decelerates rapidly from highway speeds of 75–80 mph down to approximately 45 mph. This occurs with no vehicles, obstacles, or other hazards visible ahead that would justify the slowdown. The deceleration is abrupt and feels aggressive. It has happened on multiple occasions during normal highway driving. I am forced to immediately override the system by pressing the accelerator to regain speed and avoid creating a hazard for traffic behind me. The issue occurs even in clear conditions with good visibility. This sudden braking creates a significant safety risk of being rear-ended by other drivers who are not expecting a vehicle to drop 30+ mph without warning. I have experienced this repeatedly and am concerned it is a safety defect with the vehicle’s cruise control / driver-assistance system. The problem occurs specifically when cruise control is active and does not appear to happen in the same way when I am fully controlling the throttle manually.

While using cruise control, the Tesla- several times in the last two weeks- engages "curvature assist" on completely straight roads, slams on the brakes and attempts to steer the car, creating very dangerous situations. This is a very well-known issue with Tesla and they do nothing about it.

See all problems of the 2023 Tesla Model Y 🔎.

This car was operating under "full self driving (supervised)", on [xxx] at [xxx], traveling on [xxx] near thornton gap. With no operator inputs, the car fully changed lanes to the left, crossing over the double-yellow line into the oncoming traffic lane. All four tires of the car crossed into the westbound lane before the car, still operating under full self driving (supervised) changed back into the eastbound lane. The operator of the car was prepared to take control, however without oncoming traffic at the time the car was allowed to complete the maneuvers. Information redacted pursuant to the freedom of information act (foia), 5 u. S. C. 552(b)(6).

The speed limit displayed to the driver is frequently incorrect. I believe this is a problem with all Teslas. Speaking as an aerospace engineer- as a rule it is better to provide no information to the pilot/driver than wrong information. Faa would never tolerate faulty instrumentation in an airplane, and we shouldn’t tolerate it in cars either. When the car is operating in fsd , it uses this wrong speed limit information. And operators driving manually will often rely on the displayed speed limit. Not good.

When you disengage full self driving supervised, a nag screen asking you why you turned off full self driving, blocks controls on your screen, and cannot be turned off without the driver being forced to respond. This is dangerous while parking and in other scenarios. Especially since the only way to get rid of it is by being a distracted driver, as you cannot use all controls without first answering the question as to why you decided to take over for the automated driving. This happens multiple times per drive, per day. I have included a picture of the bag screen from another driver as I did not feel comfortable taking a picture while driving.

See all problems of the 2024 Tesla Model Y 🔎.

The speed recognition of Tesla full self drive is unsafe in its present form. The speed recognition is very inaccurate. While driving on an interstate highway where the speed limit is 70mph, it is recognizing a route sign with a much lower number as a speed limit sign and suddenly applying braking, causing me to nearly be rear ended on multiple occasions. Every time I pass this sign I have to either disengage full self drive, or I have to override it to keep from being rear ended. The same thing happens on another highway, where the exit ramp has construction going on. When you are on the main road, it recognizes the exit ramp construction speed limit and tries to reduce you from 65 to 35. This problem has been reported to the manufacturer with no response other than "it is being forwarded on to the appropriate team for review".

I subscribe to Tesla fsd and there's a pop up window every time I disengaged from fsd. There's no way to systematically stop it from popping up. It is a serious distraction from driving, as it blocks part of the map and causes me thinking there's something wrong with the car. I want a way to stop it from popping up.

Critical fsd lane change - 2020 Tesla Model Y software 2026. 26. 6. 5 and fsd v14. 1 lite changed lanes suddenly and violently at freeway speed while entering an express lane with flexible lane delineators between the express lanes and the freeway. The automation made the lane change at the very last second, narrowly avoiding impact with the plastic posts, and swerving back into the left-most freeway lane. The action of the fsd could have caused a loss of control of the vehicle as it compensated for the weight shift caused by suddenly swerving. There was space between the Tesla and other vehicles at the time but this could have been catastrophic with only slight changes to the road condition etc. . . Reported to Tesla fsd beta team. No known failures, warning lights or other issues with the car.

Tesla supervised full self driving sped southbound into a school speed zone. Flashing speed zone yellow lights required speed of 20 mph. Tesla continued at 49-50 mph. Driver intervention was required to slow down to 20 mph. There has been one other incident reported for this Tesla in the same school zone operating northbound last week.

1. I was using Tesla self driving standard on my vehicle it accelerated up to 19 miles over the recorded speed limit. 2. The speed limit was 55 and it went to 74 way to high and no way to lower it manually 3. Confirmation by the MD state police radar 4. No inspection 5. There was no warnings. Consumers should be able to set the maximum speed desired or lower it if it goes to high manually, but you can't if you are using self driving options. You can go to chill which is the next level down but that is to slow. Consumers should be able to manual put the speed where they want to drive and feel safe. I was between two cars in the right lane driving down the highway. I believe my vehicle was keeping up with the flow of traffic but no way to slow it down unless I went out of standard self drive. Chill is the one below standard and that is to slow.

The suspected malfunction involved Tesla’s full self-driving (supervised) and related automated steering, lane guidance, lane-departure avoidance and disengagement/warning systems. Fsd was active before the event but changed to “unavailable” approximately 1. 35 seconds before impact as the vehicle began moving left toward a barrier. The exact cause has not been independently determined. The vehicle remains in my possession and is available for inspection, along with the edr report and Tesla data files. My safety and the safety of others were placed at risk because the vehicle departed its travel path at approximately 65–67 mph. The warning and disengagement sequence provided only about one to one-and-a-half seconds before impact. The vehicle struck the barrier at highway speed, deploying the left side and curtain airbags. This created a risk of serious injury, rollover or collision with nearby motorists. The problem has not been reproduced or confirmed by a dealer because the vehicle was rendered inoperable. However, Tesla’s data confirms that fsd was active, became unavailable approximately 1. 35 seconds before the crash, and that the steering angle moved sharply left immediately before impact. The data confirms the sequence but does not conclusively establish who or what initiated the steering movement. The vehicle has not received a technical inspection by Tesla or an independent defect specialist. Towing have handled it, but no one has technically evaluated the fsd or steering system. Crash data was retrieved from edr. Earlier in the drive, the vehicle recorded “autopilot features limited” and “camera blocked or blinded” warnings approximately 15 minutes before the crash. The vehicle later permitted fsd to engage. Approximately 1. 46 seconds before impact, a hands-on warning was detected; fsd then changed to “unavailable,” cruise control changed to standby and a lane-departure warning appeared less than one second before impact.

See all problems of the 2022 Tesla Model Y 🔎.

The Tesla will randomly when the adaptive cruise control is engaged brake from highway speeds down to 30mph. This happens when you go by off ramps and at some intersections on the highway. 1) at the intersection of [xxx] and [xxx] in [xxx] it happens sometimes especially if there is a vehicle next to you 2) at the intersection of [xxx] and [xxx] 3) off ramp on [xxx] and [xxx]. These are the places that it happens the most. It does very randomly do it at other locations. Information redacted pursuant to the freedom of information act (foia), 5 u. S. C. 552(b)(6).

See all problems of the 2021 Tesla Model Y 🔎.

Full self driving (fsd) has taken away my ability to set a maximum speed. Car is frequently wrong about the speed limit, especially in constructions zones where the speed limit changes more often. Car goes way too fast, then thinks the speed limit dropped and slows way down and then speeds up again. In addition, the 4 speed profiles they gave us instead of a simple max speed setting are useless. Standard mode usually works best but will sometimes do more than 15 mph over what it thinks the speed limit is.

I was using fsd today and was driving along highway 24 in orinda and the car almost hit the highway island at speed of 64 mph. I attached the bideo.

Tesla cruise control removed the speed limit functionality as part of its cruise control. I cannot set a maximum speed for the car. Nor can I set a minimum speed for the car. Tesla removed these features through a software update with their autopilot v14. I believe the vehicle is unsafe for myself and others as it does not allow me to set the speed using traffic-aware cruise control (tacc). Tesla is intentionally removing this feature.

This is an issue with Tesla's full self driving (supervised). The categories above don't match this capability. Sunday, xxx, about 6:05 pm. Fsd (supervised) version 14. 3. 9. Leaving in-n-out burger, [xxx], fsd chose to exit westbound onto [xxx]. A vehicle coming from the east had gone around the queue on my right and was westbound on [xxx]. Fsd pulled forward so the nose entered that westbound lane in front of that car. I intervened with throttle and steering. No contact. Since I didn't honk there was no saved dashcam clip. Information redacted pursuant to the freedom of information act (foia), 5 u. S. C. 552(b)(6).

2023 Tesla Model Y – hw3 autopilot computer/camera system failure my 2023 Tesla Model Y has approximately 54,000 miles and is equipped with the Tesla hardware 3 (hw3) autopilot computer. After receiving Tesla's fsd v14 lite software, the vehicle began intermittently losing camera-based driver-assistance functionality. I observed an app_w141 ecu thermal issue alert. The vehicle subsequently experienced aps_w134_appmia and aps_w135_appcritical alerts indicating that the autopilot processor secondary was losing communication with and detecting a malfunction of the autopilot processor primary. When the problem occurs, camera/vision functions and driving visualization become unavailable or degraded, and the vehicle has reported self-driving features limited, cruise control unavailable, adaptive headlight features unavailable, and other driver-assistance limitations. In Tesla service mode I have documented the primary autopilot processor repeatedly changing between init, critical and coreboot while the secondary processor remains nominal. A das reset can temporarily restore communication, but the failure returns. Tesla has proposed replacing the entire hw3 car computer at a cost of approximately $3,120. I am concerned that this may represent a safety-related hw3 computer failure, particularly because I observed an ecu thermal alert and because the failure removes multiple camera-based driver-assistance and safety functions. I have photographs documenting the alerts and processor states and have an open Tesla service case.

I own a 2023 Tesla Model Y (VIN: [xxx]) equipped with full self-driving and hardware 3 (hw3) computer. Over the last couple of years, while using autopilot/fsd, my vehicle has repeatedly exhibited phantom braking, including sometimes coming to a complete stop for no reason. My vehicle has also swerved into the lane of oncoming traffic on many occasions. On one occasion, this happened three separate times in one day, and the following day the vehicle swerved off the side of the road while fsd was engaged. I have reported these incidents to Tesla service repeatedly for years, including photos of related screen malfunctions and "what happened" incident data, documented in the Tesla app as well as in-person at service center visits. August 2026 was the first time Tesla told my husband and me that this was a known hardware/software (hardware 3) issue, despite years of prior reports. Tesla has given conflicting information about whether a hardware upgrade is possible: I was told the hw3 computer cannot be upgraded and was encouraged to purchase a new vehicle instead, while a service representative separately mentioned a $3,000 upgrade option that "probably wouldn't fix the issue anyway. " I am concerned this vehicle poses an ongoing risk of a head-on collision or road departure to myself and other drivers. Information redacted pursuant to the freedom of information act (foia), 5 u. S. C. 552(b)(6).

My chat constantly phantom brakes. This is a constant issue, I ve had the car since it was new and almost everytime im in adaptive cruise control it randomly brakes. Today with nothing in front of my on 3 separate occasions it applies the brakes and forces me to accelerate to maintain speed.

Whenever I disengage full self driving the car forces me to tell it why I did it via an on screen selection. It does not go away after a period of time. I used to be able to dismiss it by hitting the voice button twice but they've removed that loop hole. It's very distracting and forces me to interact with the screen while driving. The selection screen also blocks the blind spot cameras. It comes up even when disengaging to park. Someone is going to wreck messing around with this forced distraction.

I recently purchased this vehicle. I love it. It has a trial of full self driving, which I love almost all of the time. However, I noticed there is not any of the 5 settings for fsd that do not speed in school zones. I want to use fsd as much as possible, but I will not speed in a school zone. I am amazed that Tesla has been allowed to program the fsd in a way that will allow speeding in a school zone. I have to turn off fsd to maintain safety and avoid a ticket. Please require Tesla to have at least one of the 5 settings that will obey school zone speed limits.

Fsd routing issue: it’s a repeatable fsd lane selection safety issue, france avenue south to I-494. Description: when using fsd from france avenue south onto I-494, the system turns into the westbound only lane instead of staying in eastbound lane. At the end of westbound lane, fsd performs a sudden, last-second swerve into the eastbound only lane, cutting off vehicles behind already existing n the eastbound lane. This has happened multiple times, including both before and after the latest update v14. 3. 8. Expected behavior: fsd should identify the correct east only lane well in advance and stay in it when the rout is set for east 494. Concern: the late lane change cuts off traffic and creates a collision risk.

I am submitting this complaint regarding a safety defect in the human-machine interface (hmi) and driver monitoring system (dms) of Tesla's full self-driving (supervised) software. ?1. Automation complacency & vigilance degradation: when operating on highways, the system handles dynamic driving tasks in a manner that induces severe automation complacency and driver fatigue. Placing a human operator in an extended passive-monitoring role inevitably leads to degraded situational awareness, delayed reaction capability, and drowsiness. ?2. Defective in-cabin driver monitoring: the system's interior cabin camera fails to meet effective driver-monitoring standards. When a driver experiences involuntary micro-sleep, closed eyes, or drooping head posture, the cabin camera repeatedly fails to issue audible alerts, escalation chimes, or forced disengagements in a timely manner. The system permits continuous hands-free operation while the driver is compromised by automation-induced fatigue. ?3. Mismatch between marketing and safety architecture: while the manufacturer classifies the software as sae level 2 to disclaim operational liability, the operational behavior and weak attentiveness safeguards encourage disengagement without adequate fail-safes. ?because the system creates conditions that promote loss of driver alertness without a reliable monitoring system to detect and correct it, this design presents an unreasonable risk of high-speed collision. I have ceased using this software and request that NHTSA evaluate whether the cabin camera monitoring thresholds comply with defect standards under 49 u. S. C. Chapter 301.

On August 26, 2026, the vehicle’s full self-driving system was involved in three separate incidents. Between approximately 1:00 pm and 3:00 pm, while exiting a parking lot onto a main major street with full self-driving engaged, the vehicle struck the curb. At approximately 6:20 pm, while driving approximately 40 mph on a local road, one street before turning onto the highway, the vehicle began drifting out of its lane without warning for no apparent reason — it is unknown whether this was an attempted automated lane change or a system error. There was oncoming traffic in the adjacent lane at the time; I immediately took manual control of the steering wheel and applied the brakes to correct the vehicle’s path and avoid a collision. At approximately 6:45 pm, while exiting a different parking lot onto a main major street with full self-driving engaged, the vehicle struck the curb a second time. No warning lamp, alert, or message preceded any of these events, and no collision with another vehicle occurred in any of the three incidents. The vehicle has since been returned to the dealer where it was purchased. I am uncertain whether the dealer has separately reported these incidents.

Fsd (supervised) was engaged while the vehicle was traveling toward a freeway entrance. The vehicle was expected to turn right, but instead began veering left. The driver applied the brake in an attempt to slow the vehicle and disengage fsd. According to the driver’s recollection, the vehicle did not respond as expected and continued accelerating until it left the roadway and crashed into a ditch. The incident created a serious safety risk to the driver and an infant passenger. Emergency services responded, and the driver and infant passenger were transported to an emergency department for evaluation. The vehicle was subsequently towed from the scene. The suspected malfunction involves fsd/vehicle control behavior, including whether the system properly responded to brake input and whether commanded acceleration continued after the driver attempted to intervene. The vehicle and its electronic systems should currently be available for inspection, and a request has been made to preserve relevant vehicle telemetry, driver-input data, fsd engagement status, accelerator and brake inputs, commanded motor torque, speed, steering inputs, camera footage, event data recorder information, diagnostic logs, and software/fsd version information. A police report has been filed and both Tesla and Tesla insurance have been contacted.

While operating a 2022 Tesla Model Y with full self-driving (fsd supervised) engaged, the vehicle failed to execute a right merge onto the CA-280 north freeway ramp in redwood city, CA. Instead, fsd initiated an unexpected wrong-way maneuver down a downward off-ramp. As the vehicle headed toward a sharp left curve, it failed to decelerate sufficiently for the turn. The vehicle maintained speed on the downward incline and then accelerated slightly, traveling at around 30 mph immediately prior to impact. Facing an active hazard initiated by the software, I performed an emergency manual override. System steering resistance and abrupt load transfer mid-turn caused an immediate loss of control, driving the vehicle over a mound and into an off-road ditch. Airbags deployed upon impact, and occupants (including a 5-month-old infant) were transported to the emergency room for evaluation. A formal safety complaint is being filed regarding fsd wrong-way navigation failures, failure to decelerate, and severe handling/disengagement instability during emergency takeover scenarios.

My 2026 Tesla Model Y has repeatedly developed contamination/haze inside the enclosed forward-facing windshield camera area, resulting in camera visibility/cleaning warnings and potentially reduced availability or performance of driver-assistance features. Tesla has already cleaned the internal forward-camera/windshield area twice, but the condition continues to return. The contamination is located inside the camera enclosure/inboard windshield area and cannot be corrected through normal exterior vehicle cleaning. Tesla is now requesting approximately $60 to clean the area again rather than addressing why the contamination repeatedly develops. I am concerned that this is a recurring defect affecting forward-camera visibility rather than ordinary owner maintenance. The forward cameras are used by the vehicle’s driver-assistance systems. I am also aware of reports from other owners of newer Model Y vehicles experiencing recurring haze/contamination in this same enclosed camera area. I am requesting that NHTSA document and evaluate this issue for a possible defect trend in 2025+ Tesla Model Y vehicles.

On xxx at about 6:14 am, my 2026 Tesla Model Y drove into a flooded railroad underpass on [xxx] near [xxx], with full self-driving (supervised) engaged and a navigation route active. It was raining heavily (newark airport measured 1. 25 in from 5:51 to 6:51 am), the light was poor around sunrise, and the underpass was dark. The water depth was not apparent to me. At 6:12 am the national weather service had issued a flash flood warning naming [xxx] and listing underpasses. Tesla's data log (my privacy export) records fsd active from 6:12:02, my third fsd session that morning. With fsd active, speed rose from 7 to 27. 4 mph between 6:14:04 and 6:14:31, with no accelerator input recorded. Speed then fell sharply (up to about 0. 3 g), which I believe is when the car hit the water. Fsd stayed active about 8 seconds (200 ft) more; the state changed to aborting at 6:14:39, at about 6 mph. I saw no warning, and the export shows none during the approach. We could not drive out. Water rose to about window level and entered the cabin. From 6:17 the log shows restraint system, aeb, abs, stability and traction control alerts. I lowered a window at about 6:19. At 6:25 the log shows both front door releases activated repeatedly; neither door opened. We climbed out the window onto the roof. Our videos show us there at 6:31 with the front of the hood and headlights under water, and the elizabeth fire department rescued us by boat at about 6:51. The car is a total loss. Unknown: exact water-entry speed, what fsd perceived, and why it disengaged. I ask NHTSA to investigate whether fsd detects and responds to flooded roads in heavy rain and poor light, to obtain Tesla's data for this event, and to review escape from a flooded vehicle whose doors did not open. A report with the data timeline is attached. The full Tesla data export and videos are available on request. Information redacted pursuant to the freedom of information act (foia), 5 u. S. C. 552(b)(6).

Phantom braking while using the tacc on the Tesla.

On xxx at approximately 7:23 a. M. , a 2024 Tesla Model Y was traveling westbound on [xxx] in [xxx] in the middle lane at approximately 71 mph with full self-driving (fsd) engaged. While traveling in traffic, the vehicle suddenly initiated a lane change toward the right lane without providing a warning or sufficient opportunity for the driver to respond. While the Tesla was executing the lane change, a vehicle traveling behind it collided with the left side of the Tesla. Following the impact, the driver manually took control and brought the Tesla to a complete stop on the right side of the highway. The system suspected of malfunctioning is Tesla’s fsd driver-assistance system, particularly its automated lane-selection and lane-change functions. The exact cause has not been determined. The vehicle and its electronic data were preserved. Currently, non-inspection was done. The unexpected maneuver placed the Tesla and surrounding motorists at risk because it occurred without warning at highway speed in active traffic and resulted in a collision. The driver had to intervene manually after the impact to control and stop the vehicle safely. At the time of this report, the suspected malfunction has not been reproduced or independently confirmed by a Tesla service center or independent repair facility. No technical determination of the cause has been received. A police officer arrived immediatly after the accident. An inspection was performed by insurance company over a video. Before the unexpected lane change, there were no warning lamps, messages, audible alerts, or other symptoms indicating that he vehicle was about to initiate the maneuver or malfunction. The lane change occurred suddenly while fsd was engaged. Information redacted pursuant to the freedom of information act (foia), 5 u. S. C. 552(b)(6).

I am reporting multiple safety?critical incidents involving my Tesla Model Y equipped with fsd (supervised). The vehicle has repeatedly performed sudden braking in active traffic without any obstacles present, causing physical jolting and creating a risk of collision. These incidents occurred on [xxx] and xxx including a sudden hard brake at approximately 2:18 p. M. On xxx. Additionally, the vehicle has shown lane?centering instability on the highway. On xxx at approximately 1:51 p. M. , the vehicle drifted within the lane and failed to maintain proper centering while fsd was engaged, requiring immediate manual intervention to avoid unsafe movement. Tesla service has stated that no error codes were detected, but also acknowledged known fsd software behaviors affecting hardware 3 vehicles. This indicates the system may be performing unsafe maneuvers without logging faults. I am reporting these incidents because they pose a direct safety risk to me, other drivers, and pedestrians. I request that NHTSA review these behaviors as potential safety defects in Tesla’s fsd (supervised) system. Information redacted pursuant to the freedom of information act (foia), 5 u. S. C. 552(b)(6).

The fsd failed when it back into garage; the back of passenger side of the car hit the wall of garage. There is no warning before. Beacuse the distance for parking into the garage is small, there is no time to take over the fsd to avoid it happen. It happen around 23:35 on August 07, 2026. We reported as a safety incident to Tesla an hour ago. We updated the the software on August 02, 2026. The car had been succesful back into the garage more than ten times before.

I own a 2021 Tesla Model Y with an hw3 car computer. At approximately 54,000 miles, the vehicle developed intermittent failures of the cameras, gps/navigation, and cruise control. On two occasions during the same routine drive, about 40 minutes into the trip, the gps, cameras, and cruise control abruptly stopped functioning at approximately the same location. The first occurrence was about July 7, 2026 at 9:15 am and the second August 7, 2026 at about 3:15 pm. I made the same trip once between these events without a failure. I had also previously experienced a frightening incident while driving northbound on I-280 approaching the lane division for 19th avenue in san francisco using autopilot. Where my lane widened and a new lane began, the vehicle abruptly attempted to follow the new lane to the right. I had to intervene firmly with the steering wheel to maintain control. I do not know whether this event was related to the later diagnosed computer failure, but report it because of its possible safety significance. Tesla serviced the vehicle in sunnyvale on August 16, 2026 at 54,565 miles. Tesla's invoice states: “technician addressed the intermittent loss of gps, cameras, and cruise control. The car computer had board-side failures and was replaced. ” Tesla replaced the hw3 computer with a hardware 3. 2 computer, part 1775000-s0-l. Tesla also found corrosion at the 12v input and replaced the 12v battery. My concern is that the hw3 computer failure was intermittent and simultaneously affected cameras, gps/navigation, and cruise control. The vehicle operated normally between failures, so a driver could not know when the problem might recur. I ask NHTSA to determine whether similar hw3 computer failures are occurring in other 2021 Model Y vehicles.

My 2023 Tesla Model Y suffered a critical factory safety defect: under-torqued front suspension lateral link bolts, causing dangerous clunking noises under autopilot. The official Tesla invoice verified the defect and noted it was re-torqued to spec. Crucially, a close friend owning an identical 2023 Model Y in [xxx] experienced the exact same suspension noise. Upon inspecting his car, the littleton facility attempted to exploit his lack of information by issuing a deceptive out-of-pocket diagnosis estimate of $240. 00 instead of honoring the active bumper-to-bumper warranty. Tesla only backed down and waived the fee to $0. 00 after being confronted with my personal repair invoice as leverage. This proves Tesla is actively executing predatory billing and hiding a systemic batch safety hazard from uninformed consumers. Regulatory investigators can verify this pattern by auditing the littleton service center's internal torque check logs and warranty waiver histories for 2023 Model Y vehicles. Furthermore, after touchless app-pickup on xxx, Tesla staff omitted any key card communication. Two weeks later, after discovering my physical key cards were missing, I initiated a brand-new service request to inquire, and agent tony admitted they were left at the front desk, exposing that advisor luis rodriguez falsified records on xxx by logging that the vehicle was retrieved on xxx. This constitutes bad-faith warranty denial, record alteration, and predatory consumer deception. I formally reported this severe failure directly to Tesla global compliance on xxx, but have received absolutely zero response to date. Full pdf report of my personal logs provided. Information redacted pursuant to the freedom of information act (foia), 5 u. S. C. 552(b)(6).