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

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

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

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

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

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