2024 Tesla Cybertruck Driver assistance Problems

Approximately 10 minutes after my vehicle was serviced at a Tesla Service Center for a Full Self-Driving (FSD) concern, I entered the highway and engaged FSD. The service center had stated the system was operating correctly. While traveling approximately 75 mph through a highway curve, FSD suddenly changed to an "Unavailable" state. According to Tesla's own accident data, I did not disengage FSD. There was no audible warning, no effective visual warning, no takeover request, no controlled deceleration, and no safe handoff to the driver before the vehicle stopped controlling itself. Within about one second of FSD becoming unavailable, the vehicle left its intended path and struck a concrete highway divider. If the divider had not been present, the vehicle likely would have crossed into oncoming highway traffic, creating the risk of a catastrophic head-on collision with other vehicles, including a semi-truck. Tesla's accident report confirms I did not disengage FSD and shows no warning or takeover request before impact. I possess documentation supporting that FSD became unavailable without a safe transition to the driver. This failure occurred immediately after Tesla serviced the vehicle and represented that the FSD system was functioning properly. Despite the accident data, Tesla Customer Support and the Service Center have refused to acknowledge or investigate what appears to be a failure of the FSD system's fail-safe behavior. The failed component appears to be the FSD/Autopilot system and its driver handoff logic. The vehicle and electronic records are available for inspection. An automated driving system should not terminate operation at highway speed without providing adequate warning, a safe transfer of control, or controlled deceleration. I believe this presents a serious safety defect that could result in fatal crashes. The collision caused approximately $15,500 in vehicle damage.

NHTSA ID

11747861

Incident

Apr 28, 2026

This is reporting an issue with v14.3.3 and v14.3.4 of Tesla Full Self Driving (FSD) Supervised. This month I have driven over 4,000 miles with FSD enabled, approximately 2/3rd on 14.3.3 and 1/3 on 14.3.4. FSD has regularly failed to respect speed limit changes, even though it seems to recognize / observe the speed limit signs. I am certain it’s observing the signs because it renders them on the in-car display, but it doesn’t actually adjust its speed in response to those signs. The most egregious of cases have been when driving through Texas, New Mexico, and Arizona where the speed limit is often 75 mph on Interstate highways (e.g., [XXX]). On multiple occasions the vehicle has ignored construction speed limit changes to 55 mph, and instead has tried to maintain 75-80 mph through the construction zone. Not only could that get me a nasty speeding ticket, but it could also put construction workers lives at risk. It has also happened in non-construction zones, like when on a non-interstate highway that passes through towns and reduces speed when doing so. It doesn’t fail 100% of the time, but it has been an issue more than 50% of the time I enter a construction zone. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

NHTSA ID

11745182

Incident

Jun 18, 2026

Tesla does a warning if it can not detect your eyes on the road when using FSD (Full Self Driving). After few warnings on a trip it becomes a strike. After 5 strikes, they remove FSD and AutoPilot for a week. It becomes dangerous now since I have been driving on FSD for several years to drive the big CyberTruck without FSD. The removing FSD for a week behavior needs to be stopped. Without FSD chances of accident are 10000% increased.

NHTSA ID

11743084

Incident

Jun 8, 2026

On 05/30/2026 at approximately 15H24, my Tesla Cybertruck was parked and stopped at approx. [XXX] of Target). No one was seated in the driver seat. A passenger entered the vehicle and sat in the front passenger seat to play music. Shortly after the passenger sat down, the vehicle suddenly and unexpectedly moved forward on its own and rear-ended the vehicle parked directly in front of it and causing damages. This occurred while the vehicle was supposed to be parked/stationary and while there was no driver in the driver seat. We do not understand what triggered the vehicle to move forward. This appears to be a serious safety issue because a parked, unattended vehicle should not move forward without driver input. The incident created a collision risk to nearby vehicles, pedestrians, and anyone standing in front of or around the vehicle. I am requesting that NHTSA review this as a potential unintended movement / unintended acceleration / park-to-drive activation / rollaway safety defect. Tesla should be required to investigate the vehicle logs and determine whether the movement was caused by a software issue, gear selection issue, Autopark/FSD/Summon/mobile app activation, brake hold/parking brake failure, sensor/occupancy issue, accelerator pedal issue, or any other defect. Video and photos in the link: [XXX] There was property damage to the vehicle parked in front. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

NHTSA ID

11741313

Incident

May 30, 2026

NHTSA Recall 24V276000 covers an accelerator pedal pad that can dislodge and become trapped under the pedal, causing unintended acceleration. This recall was identified as active and unperformed on my vehicle by Tesla Council Bluffs, IA. Tesla Pensacola told me the vehicle had "nothing wrong" and performed no recall work despite multiple service visits. Safety risk: Unintended acceleration is an extreme safety hazard capable of causing fatal accidents. Manufacturer response: Tesla Pensacola failed to identify or perform this safety recall. Tesla Council Bluffs immediately identified it as requiring urgent attention. Available for inspection: Yes — vehicle at Tesla Tallahassee Service Center.

NHTSA ID

11740907

Incident

Jun 26, 2024

All vehicle cameras failed simultaneously on May 12, 2026 at approximately 4:41 PM. Tesla app displayed "Cameras Unavailable — Please try again later." All camera-dependent systems were completely inoperable: Autopilot, FSD, Sentry Mode, dashcam/TeslaCam. Component failed: Entire forward and perimeter camera system. Vehicle available for inspection at Tesla Tallahassee Service Center. Safety risk: Vehicle cannot safely operate driver assistance systems with all cameras dead. Total loss of rear/side visibility systems while driving. No warning prior to failure. Manufacturer response: Tesla Pensacola general manager intentionally cancelled 8 consecutive service appointments — confirmed on recorded Tesla corporate call May 29, 2026. Owner drove 2.5 hours to one appointment and the GM rescheduled it without any notice. Tesla corporate agent confirmed on record: "You shouldn't have to travel to a service center that's over 100 miles away when you have one that's close to you." As of May 29, 2026 vehicle is at Tallahassee SC — Tesla refusing to provide a loaner or complete repairs. Owner has been without vehicle 24-48 hours despite being promised a loaner at time of tow. Prior warning: TeslaCam left-repeater camera failure events auto-saved December 15, 2025 — system was already failing 5 months prior to total failure. Was defect reproduced by dealer: No — Tesla refused to inspect despite 8 cancelled appointments.

NHTSA ID

11740903

Incident

May 12, 2026

The main FSD computer has given me a fault which probably necessitates replacement of the main computer at a cost of $3250. Car is 2024 and is just out of warranty with 52,000 miles within the last month. Tesla states they will not cover. Safety features are "not available", per the warning on my dash.

NHTSA ID

11738019

Incident

May 15, 2026

The failed components include the Tesla Vision system (cameras), sensors, Active Safety Control Module (AEB), and Gear Selection UI. Symptoms first appeared on April 30, 2026, including black screens and "Autopilot Unavailable" alerts. Internal vehicle logs from Apr 30 to May 02 confirm persistent "SNA" (Signal Not Available) and "UNAVAILABLE" states for these critical safety modules well before the collision. On the day of the accident (May 02), the logs recorded 25 instances of Gear UI signal loss, which completely disabled the rearview camera and proximity alerts while reversing. This total "blind" state put my safety at extreme risk as I had zero visibility of blind spots and received no audible warnings. The Automatic Emergency Braking (AEB) was also recorded as "UNAVAILABLE," failing to prevent the collision. The problem is scientifically confirmed by the vehicle's internal diagnostic logs, which I have retrieved and am ready to provide for inspection. The accident has been reported to the local police and Progressive Insurance. I am currently coordinating with Tesla Service for a formal inspection of these software and hardware defects.

NHTSA ID

11736349

Incident

May 1, 2026

The new tesla update forces me to interact with the touch screen in order to operate my vehicle after self driving is disabled. There is no way to dismiss or disable this screen in the new update and no way for me to roll my vehicle back to the old software. After disengaging self driving a forced selector box forces you to make one of 4 choices in order to see your screen/navigation and perform other features in the car such as adjusting the windshield wipers. There is no way to disable this screen, it pops up every single time Full Self Driving is disengaged and there is no way to disable it. I believe this actively violates california law by requiring me to interact with the touch screen while actively controlling the vehicle on manual mode. I tried clicking elsewhere on the screen but yuo are forced to select one of the four options presented

NHTSA ID

11734677

Incident

Apr 29, 2026

On December 23, 2025, at approximately 9:45 AM, I was operating my Tesla Cybertruck with Autopilot engaged under normal driving conditions. There was no inclement weather, the roadway was straight, and visibility was clear. While driving, the vehicle suddenly veered off the main roadway without warning and traveled off-road, ultimately colliding with a tree. The movement was abrupt and not consistent with normal lane departure. I immediately attempted to correct the direction of the vehicle; however, the vehicle did not respond appropriately to my steering input and felt unresponsive during the event. At no point did I intentionally steer off the roadway. The loss of control was unexpected given the road conditions and environment. This incident raises concerns about the reliability and safety of the Autopilot/driver assistance system and its ability to maintain lane control and allow driver override when needed.

NHTSA ID

11725051

Incident

Dec 23, 2025

Vehicle Safety Complaint - Tesla Cybertruck Steering System Failure During FSD While driving my Tesla Cybertruck with Full Self-Driving (FSD) engaged, the rear steering system failed without any prior warning. FSD immediately disengaged, and a red steering system ERROR appeared on the instrument cluster. The rear axle steering was completely disabled, turning radius became severely limited, and vehicle speed was restricted. This occurred while actively driving in traffic and was extremely dangerous. I accessed the vehicle’s Service Mode and documented three fault codes that triggered simultaneously at 17:48:14 on March 4, 2026: 1.RSAM_a260_monitorTripDetected ∙Monitor trip detected, system degraded ∙Potential Impact: Steering system performance degraded, vehicle speed limited ∙Only clears on next power-up 2.RSA_a212_activeFault ∙Rear Steer Actuator (RSA) stopped at current position ∙Internal condition detected, defaulted to safe state ∙Fault Reason: CONTROLLER_IRRATIONAL ∙Previous State: RSASTATE_ACTIVE_STEERING (was actively steering when failure occurred) ∙rsamControllerRational = false 3.PEPS_a182_rearSteerDegraded ∙Primary Electric Power Steering (PEPS) detected RSA not functioning as expected ∙Reason: RSA_UNHEALTHY ∙rsaUnhealthy = true ∙rearSteerCommand = -0.59 All three faults were set at 17:48:14 and cleared at 17:50:55. Additionally, an earlier alert — EGGRIGHT3_a203_airwaveLeftLateralUnavailable — was logged on March 2, 2026 at 21:11:08, which may indicate a related or recurring issue. The simultaneous failure of the rear steering actuator and disengagement of FSD while driving at speed represents a serious safety hazard. The RSA controller was flagged as “IRRATIONAL” while the system was in active steering mode, meaning the steering hardware failed during operation — not at startup or in a parked state. I have photographic documentation of both the dashboard steering ERROR warning and all Service Mode diagnostic screens showin

NHTSA ID

11722131

Incident

Mar 4, 2026

Since the release of V14, the Full Self-Driving (FSD) system automatically defaults to operating approximately 7 MPH above the posted speed limit. This occurs on all road types, including city streets and highways. When FSD is engaged, the vehicle sets the cruising speed above the detected speed limit without driver input. There is no setting that allows the driver to enforce strict compliance with the posted limit. Available speed settings only permit equal or greater deviation above the speed limit. The driver cannot manually lock or command the system to remain at or below the posted limit while FSD is active. The only way to prevent speeding is to fully disengage FSD. This is not a malfunction. The vehicle is operating as designed under V14. This creates a safety concern because: 1.The system is programmed to exceed legal speed limits by default. 2.The driver does not retain meaningful authority to ensure lawful operation while automation is engaged. 3.Automatic speeding increases crash risk in construction zones, school zones, and changing speed areas. 4.Drivers may receive citations despite not intentionally selecting an unlawful speed. Because this behavior was introduced via V14 software, it likely affects all Tesla vehicles running FSD V14, not just this vehicle.

NHTSA ID

11718199

Incident

Jan 1, 2026

All the road safety features stopped working all of a sudden. Auto lights. Defaulted to high beams. Lane departure stopped, cruise control stopped, forward emergency braking stopped, rear cross traffic stopped, blind stopped stopped, and other safety’s I am not sure of.

NHTSA ID

11710822

Incident

Jan 14, 2026

While operating on a public roadway with Tesla Full Self-Driving (Supervised) engaged, the vehicle unexpectedly departed its intended roadway trajectory. Upon recognizing unsafe vehicle behavior, I attempted to manually override and disengage the system using normal driver control inputs. Despite these attempts, the system did not disengage or yield control in a timely or effective manner. The vehicle continued on an unsafe path, left the roadway, and collided with a fence and a tree before meaningful driver control could be restored. This incident raises concerns regarding the reliability of driver override authority and the system’s ability to relinquish control during supervised operation.

NHTSA ID

11709210

Incident

Dec 23, 2025

On December 23, 2025, my 2024 Tesla Cybertruck (Foundation Series) was operating with Full Self-Driving (FSD – Supervised) engaged. While FSD was active, the vehicle executed an unsafe driving trajectory. I attempted to intervene and regain control; however, the system did not disengage as expected and did not yield control appropriately to driver input. Despite driver intervention attempts, the vehicle continued along the unsafe trajectory, resulting in a loss of control and collision with roadside objects. There were no mechanical warnings or alerts prior to the incident. The issue appears related to system behavior, disengagement logic, and driver override response while FSD was active. The vehicle is currently preserved under a formal litigation hold. No inspection, teardown, or data access has occurred. Tesla has confirmed in writing that it does not modify, delete, or alter vehicle data it has received. I am submitting this complaint due to concerns regarding the safety behavior of Full Self-Driving (Supervised), including the system’s failure to disengage upon driver input and the human-machine interface governing control authority.

NHTSA ID

11708875

Incident

Dec 23, 2025

While exiting the Chick-fil-A drive-thru lane, I lightly pressed the accelerator to move into the next lane. Suddenly, the vehicle jerked forward very quickly, as if I had floored the accelerator. At the same time, the display showed "Emergency Braking in Progress." It felt as though the truck briefly braked and then rapidly released, causing unexpected acceleration. No collision occurred, but it was startling and very scary.

NHTSA ID

11695892

Incident

Oct 27, 2025

The contact’s father owns a 2024 Tesla Cybertruck. The contact’s father stated that while driving at an undisclosed speed, the Autopilot function became inoperable. The contact stated that while engaging the Autopilot function and attempting to make a turn in a residential area, the vehicle unexpectedly accelerated and collided with a tree. The air bags did not deploy during the incident. As a result of the crash, both the contact’s father and nephew sustained injuries and received medical attention at a local emergency room. The contact’s father sustained a rib injury and bruising, while the contact’s nephew suffered an ongoing back injury due to the incident. A police report was filed. The vehicle was towed and taken to a body shop. The dealer was contacted; however, the vehicle was not diagnosed or repaired. The manufacturer was made aware of the failure, and a case was opened. The approximate failure mileage was 1,500.

NHTSA ID

11695239

Incident

Oct 23, 2025

Mileage

1,500 mi

The car crosses solid yellow lines all the time. all the time. it hits rumble strips. it generally is unsafe and annoying. it is getting worse. this is not to mention the constant brake checking when engaging. it does not change lanes when prompted even if it is safe.

NHTSA ID

11695123

Incident

Oct 22, 2025

On May 15, 2025, at around 11:30 AM, my Tesla was involved in a collision while Full Self-Driving (FSD) was engaged. The incident occurred at the Tesla West Covina Dealership. The vehicle struck a barrier wall without any collision warning, suggesting both a failure of the sensors and FSD system. After the incident, Tesla staff directed me to their West Covina Service Center. A service advisor reviewed the dashcam footage with me and acknowledged the crash appeared to result from FSD malfunction. I was told Tesla will cover the repair. However, when I returned on May 26, 2025, I was informed that the dashcam footage was no longer available. I did not delete it and suspect it may have been removed by Tesla personnel. They also then claimed they will not cover any repairs. I have written to their legal department to formally request the video footage and any other data they have regarding the crash. Despite follow-up, Tesla has not responded or released any data. I am reporting this as a possible safety defect and mishandling of evidence. I request NHTSA investigate: The failure of Tesla’s FSD and collision avoidance system. The disappearance of crash footage after review by Tesla staff. Tesla’s lack of response to requests for data and documentation. Thank you for your attention.

NHTSA ID

11677874

Incident

May 15, 2025

I am filing this complaint regarding Tesla's failure to include the advertised Autosteer feature in my new Cybertruck, which I believe raises serious safety concerns. At the time I ordered my vehicle, Tesla's website and the official Cybertruck Owner’s Manual (archived October 15, 2024) clearly listed Autosteer as a feature included with Autopilot. Tesla also markets Autopilot as a system that “enhances safety and convenience,” which formed a core part of my purchasing decision. I previously owned both a Model 3 and Model Y, both of which had Autosteer included in the base Autopilot, reinforcing that expectation. Upon delivery of my Cybertruck, I learned that Autosteer was not actually included, and Tesla now requires customers to pay for Full Self-Driving (Supervised) to access this core safety function. This change was not communicated prior to purchase or delivery and contradicts both historical Tesla offerings and the documentation available at the time of sale. Tesla’s decision to restrict a safety-related feature—one that assists with lane keeping and crash avoidance—may put my family and others at greater risk. Drivers may assume Autosteer is included based on Tesla’s marketing, which could lead to misuse or over-reliance on the limited Base Autopilot. I contacted Tesla directly and requested a resolution. Despite multiple follow-ups, I received no meaningful response. I believe this matter represents a pattern of deceptive practices and raises legitimate safety concerns regarding what features are expected and what is actually delivered. I respectfully request that NHTSA investigate Tesla’s removal of Autosteer from Base Autopilot and its potential implications for consumer safety and transparency in driver-assistance system advertising.

NHTSA ID

11672921

Incident

May 6, 2025

Truck mirror came in contact with a small eucalyptus tree at 65 MPH on the side of the highway during a trip on FSD autopilot. On the way back from the trip, the destination address was put into navigation and the FSD button was pressed. Unbeknownst to me the vehicle had switched from FSD Autopilot to cruise control. The vehicle was swerving all over the road and almost hit a curb and other parked vehicles at 25-30 MPH Also, aside from this case in some areas on the highway the vehicle will cut over the lines and not stay in the lane while in FSD Autopilot. I have NEVER had this issue where FSD Autopilot disengaged after a trip and returning. Once the settings are placed in FSD Autopilot they were never changed unless done manually. There were no alerts/notification telling me FSD/Autopilot was disengaged. I’ve sent a report to Tesla and received an automatic AI response mentioning that FSD or Cruise Control needs to be selected for each trip. This has NEVER been the case.

NHTSA ID

11668403

Incident

Jun 20, 2025

I was driving [XXX] going through Saint Paul and the truck sped up and became uncontrollable. I started braking as fast as I could and caused it to rear end into another vehicle. I’ve tried to contact Tesla about this, and they have not responded to me. I was told the engineering team would get back to me about the possible cause of the accident, but never heard back and they could not provide me any of the vehicle data or video which they told me in the service center. They would be able to find that when they diagnosed it, they did fix the vehicle and I ended up selling it due to not being too excited about driving ever again. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

NHTSA ID

11668244

Incident

Dec 17, 2024

I am writing to report an incident that occurred on [XXX] [XXX] while my Cybertruck was operating in Full Self-Driving (FSD) mode. While driving on [XXX] Brooklyn NY with no other moving traffic present, my Cybertruck did not detect a vehicle that was parked improperly—sticking out too far into the lane. The FSD system failed to adjust its path accordingly and struck the side view mirror of my vehicle, causing significant damage to the mirror glass and housing. I understand that FSD is a driver-assist feature that requires supervision, and I was attentive during the drive. However, the clearance of side view mirrors from the driver’s perspective is extremely difficult to judge at street level, and I believe stationary obstacles of this nature should be reliably detected and avoided by the FSD system. This type of incident raises concerns about the performance of FSD in handling stationary objects, especially when the vehicle was otherwise properly supervised and operating in a straightforward environment. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

NHTSA ID

11665678

Incident

Jun 8, 2025

On [XXX], at approximately around [XXX], an incident occurred involving the Auto Park feature of a Tesla vehicle in a quiet parking lot. The conditions were clear, with no adverse weather, obstacles, or surrounding vehicles. The Auto Park function was engaged, and the vehicle reversed and moved forward as expected. However, it failed to stop and collided with a yellow pole directly in front. The front camera feed was visible on the screen, but the vehicle did not detect or recognize the pole, and no collision alert was issued. The incident occurred too quickly to allow manual intervention via the brake pedal. The collision resulted in minor front bumper damage, with repair costs estimated at over $1,500. All incident details and vehicle data have been provided to Tesla for investigation. And they rejected to provide front plastic bumper replacement. [XXX] [XXX] INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

NHTSA ID

11661656

Incident

May 10, 2025

While driving with Tesla's Full Self-Driving (FSD) system engaged, my vehicle struck two standard traffic cones in a clearly marked construction zone. The system failed to detect the cones or make any evasive action. I have video evidence of the incident. The situation was extremely dangerous. The cones could easily have been construction workers, pedestrians, or something more severe. I hesitated to intervene because it happened in a split second, and I was trusting the system to respond — which it completely failed to do. In that moment, I was also faced with a difficult choice: swerve and potentially cause a more serious accident, or trust that FSD would navigate correctly. It didn’t. The impact caused damage to my vehicle. When I brought it to Tesla, the technician dismissed my concern, laughed, and sarcastically told me, “There’s no way we’re paying for it.” He said it was my responsibility to avoid the cones — even while FSD was fully engaged. That kind of response is unacceptable, especially when Tesla markets this system as being capable of handling real-world driving environments like construction zones. This incident shows a significant failure in Tesla’s FSD recognition and decision-making systems. There were no warnings or alerts prior to the impact. The event raises major safety concerns, not only for the driver but for anyone on or near the road. I’m reporting this because I believe Tesla's current version of FSD has critical deficiencies that could lead to injury or worse. The system should never ignore basic road hazards like cones, and the company's dismissive response after the fact is alarming.

NHTSA ID

11653398

Incident

Apr 6, 2025