What 161 owners told NHTSA about the 2024 Tesla Cybertruck (all Variants)

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 ODI 11747861

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 ODI 11745182

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 ODI 11743084

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 ODI 11741313

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 ODI 11738019

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 ODI 11736349

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 ODI 11734677

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 ODI 11722131

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 ODI 11718199

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 ODI 11710822

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 ODI 11708875

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 ODI 11695892

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 ODI 11695239

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 ODI 11677874

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 ODI 11668244

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 ODI 11665678

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 ODI 11661656

The contact owns a 2024 Tesla Cybertruck. The contact stated that while driving at 70 MPH with the "Full Self-Driving" (FSD) active, the vehicle ahead of the contact's vehicle abruptly slowed down. The contact began to notice that the vehicle failed to detect the vehicle slowing down and the contact attempted to manually stop the vehicle. The contact crashed into the vehicle which resulted in a three-vehicle collision. The air bags failed to deploy upon impact; as a result, the contact hit her chest on the steering wheel. The contact was taken to the hospital via an ambulance and was treated for neck, back and chest pain. The two other vehicle occupants sustained both neck and back injuries but did not seek medical treatment. The whereabouts of the other drivers were unknown. A police report was filed(report unavailable). The vehicle was initially towed to an independent tow yard. The manufacturer was notified of the failure and later towed the vehicle to an authorized Tesla service center where it remained in their possession. The current condition of the vehicle remains unknown. The failure mileage was 5,149.

NHTSA ODI 11646503

I was driving in a rain storm and the wiper started to malfunction. Would only clean half the windshield. Then shut off completely. Made a weird noise and started smoking in the front.Started working for on wipe then did a 360 on front end of the car. Wiper blade flew off and wiper arm Would not stay in position. Was able To get home but had to get the car towed to Tesla.

NHTSA ODI 11631277

NHTSA has created a safety risk by forcing FSD to have extreme monitoring. While in FSD I have to go back to normal driving to change the station on the radio or look at my phone. This is something I do in my non fsd vehicles all the time. The reason for me purchasing FSD is to be safer. Your ridiculous overreach may actually kill me.The entire purpose is to reduce distracted driving, yet your ridiculous rules force an unsafe environment. I hope whoever pushed these restrictions realizes they are accountable for the crashes and deaths they create for forcing people out of FSD.

NHTSA ODI 11626095