i was in FSD mode and my car began parallel parking.As the car was in reverse it automatically accelerated and crashed into the car behind me. I did not step on the accelerator pedal, nor the brake and my hands were not on the steering wheel. I in no way caused this accident. What is most surprising is that there was no warning response. Normally if I get too close to any object a color warning shows up on the screen, if I decide to make a change while driving the screen comes up with 4 options as to why I took control but in this case with the car hitting an object there was no response at all.Teslas standard answer is always that it's my fault. I know what happened and it was not my fault.I now have a repair estimate for $1,897.98 which I must be responsible for
NHTSA complaint #11758297 — an unverified report by a vehicle owner.
Austin, TXCrash
UNKNOWN OR OTHER
This is what happened: While Full Self-Driving (FSD) was engaged, the vehicle approached an intersection and appeared unable to correctly follow the roadway. Instead of following the intended road path, the vehicle continued forward, drove over the curb, and struck a road sign. The impact knocked the sign down, and the sign subsequently struck the vehicle, including the roof glass. The roof glass shattered and small pieces of glass entered the cabin, exposing both the driver and front passenger to a safety risk. Vehicle data obtained after the incident shows that the vehicle was in ACTIVE_FSD leading up to the collision. FSD changed from ACTIVE to UNAVAILABLE approximately 1.5 seconds before the crash algorithm wake-up. Significant braking occurred only very close to the collision, and no Automatic Emergency Braking intervention was recorded during the incident window. The data also shows multiple substantial steering movements shortly before the collision. Accelerator-pedal data does not establish driver acceleration as the cause of the collision. The available samples show an accelerator position of 2.0% shortly before the collision and 0.0% in the next recorded sample. The driver applied the brake shortly before impact. There were no prior warning lamps or messages indicating that FSD was about to become unavailable before the vehicle departed the roadway. The vehicle has been inspected/repaired following the collision, and vehicle data relating to the incident has been obtained and preserved. Police responded to the collision, and the incident was also reported to insurance. A police report was filed, and the case number is 2026-07160174. I have not yet received the formal CR-4 crash report. Following the collision, I experienced significant psychological distress and trauma-related stress symptoms as a result of the incident.
NHTSA complaint #11758061 — an unverified report by a vehicle owner.
Laveen, AZ
UNKNOWN OR OTHER
[XXX] [XXX] [XXX] [XXX] [XXX] [XXX] [XXX] Email [XXX] National Highway Traffic Safety Administration Office of Defects Investigation [XXX] [XXX] Re: Safety Concern – Tesla Structural Battery Pack Design Dear NHTSA, I am writing to raise a serious safety and durability concern regarding Tesla’s structural battery pack design, in which the high-voltage battery is glued into the vehicle’s body and used as a load-bearing structural member. My primary concerns are as follows: See atrached PDF fe INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
NHTSA complaint #11757570 — an unverified report by a vehicle owner.
Leander, TXCrash1 injured
UNKNOWN OR OTHER
On August 3, 2026, my Tesla Model Y was traveling at approximately 50 mph with Tesla Full Self-Driving (FSD) engaged. At approximately 4:12:47 PM CDT, FSD became unavailable and then became available again. At 4:12:51.628 PM CDT, FSD was recorded as ACTIVE_FSD again. Approximately 2.36 seconds after FSD was re-engaged, at 4:12:53.987 PM CDT, the vehicle's steering began a sudden and rapid rightward movement. I did not turn the steering wheel or intentionally provide a rightward steering input that initiated this maneuver. The recorded steering angle increased rapidly from approximately +11.4° to +20.7°, +33.3°, +83.3°, +137.9°, +154.7°, and ultimately approximately +282° within about 1.6 seconds. Importantly, FSD was still recorded as ACTIVE_FSD when the steering movement began. FSD changed to UNAVAILABLE at approximately 4:12:54.364 PM CDT, about 0.38 seconds after the steering movement had already started. The steering continued to escalate after FSD became unavailable.The vehicle subsequently experienced severe lateral acceleration of approximately 0.96 g, and crash detection activated at approximately 4:12:55.710 PM CDT. The accelerator was recorded at 0% during the developing steering event and increased only after crash detection. Hard braking and ABS activation occurred afterward.I do not have Tesla Dashcam footage, but I have retained Tesla's vehicle telemetry export containing FSD state, steering, steering-torque, accelerator, braking, vehicle-speed, stability-control, and crash-event data.I am concerned that Tesla FSD may have initiated or contributed to the unexpected steering maneuver that resulted in the collision. I am certain that I did not initiate the sudden rightward steering maneuver.I request that NHTSA investigate whether this represents a potential safety defect or unexpected FSD behavior, particularly the sequence of FSD re-engagement followed approximately 2.36 seconds later by the unexpected steering event while FSD was still ACTIVE_FSD
NHTSA complaint #11756945 — an unverified report by a vehicle owner.
Greeneville, TN
UNKNOWN OR OTHER
I was operating my Tesla using Full Self-Driving (Supervised) when the vehicle approached an active school zone with flashing warning lights and a posted school-zone speed limit of 35 mph. FSD did not appropriately respond to the active school zone or reduce the vehicle's speed to the posted 35 mph limit, requiring me to disengage FSD and manually slow the vehicle. The incident was captured on the Tesla dashcam. The recording shows FSD active while approaching the school zone. At approximately 14 seconds into the recording, the vehicle was traveling approximately 52 mph with "Self-Driving" displayed while the flashing school-zone warning and SCHOOL pavement markings were visible ahead. The posted school-zone speed limit is 35 mph when the warning lights are flashing. Because FSD was not slowing the vehicle appropriately, I intervened and disengaged FSD. Immediately following my intervention, vehicle speed decreased from approximately 49 mph to 39 mph, 31 mph, and approximately 29 mph as I manually slowed the vehicle. This was the second time I experienced FSD failing to appropriately respond to this same active school zone. After this occurrence, I saved the dashcam recording and submitted a Bug Report through the vehicle. There were no warning messages indicating that FSD could not recognize or respond to the school zone. My safety concern is that FSD may proceed into an active school zone substantially above the posted school-zone speed limit unless the driver recognizes the failure and intervenes. The original dashcam recording is available and documents the vehicle speed, FSD status, active flashing school-zone warning, posted speed limit, and timing of my intervention.
NHTSA complaint #11756753 — an unverified report by a vehicle owner.
Post Falls, ID
UNKNOWN OR OTHER
My car locked itself with the phone key and the key card sitting in the car. My baby was trapped in the back seat. Eventually, I was able to get a hold of my husband and he was able to unlock the car from the app. I was talking to 911 when he saw my messages and unlocked the car. I think poor cell reception may have been the cause.
NHTSA complaint #11755383 — an unverified report by a vehicle owner.
Anaheim, CA
UNKNOWN OR OTHER
I was operating my Tesla using Full Self-Driving (Supervised) from my home to a coffee shop. The vehicle completed the entire drive under FSD without any manual intervention. After arriving at the destination, FSD automatically entered the parking lot, selected an available parking space, and initiated the parking maneuver on its own. I did not manually select the parking space or start the parking maneuver. During the automatic parking maneuver, the vehicle failed to detect a fixed square concrete bollard located within the parking space and continued moving until the front bumper made contact with the bollard, causing damage to the vehicle. No collision warning, parking collision warning, or automatic emergency braking occurred before impact. The vehicle remained under FSD control until the collision. The incident occurred in daylight with good visibility. The obstacle was a permanent concrete bollard, not a temporary object or a low parking curb. Dashcam footage of the incident has been preserved and has been provided to Tesla Insurance. I believe Tesla should review the vehicle telemetry and FSD logs to determine why the system failed to recognize the fixed obstacle during the automated parking maneuver.
NHTSA complaint #11754995 — an unverified report by a vehicle owner.
Pittsburgh, PA
UNKNOWN OR OTHER
On July 31, 2026, at approximately 12:55 PM, my 2026 Tesla Model Y experienced a severe safety defect while operating in Full Self-Driving (Supervised) mode. The vehicle completely failed to detect, slow down for, or stop at a clearly visible and unobstructed stop sign at an intersection. The vehicle attempted to proceed through the intersection without yielding. I was fully attentive with my hands on the wheel and had to instantly apply heavy manual braking and steering intervention to prevent a collision with an oncoming vehicle that had the right of way. This failure of the automated driving system to recognize fundamental traffic control devices constitutes an immediate and severe collision hazard.
NHTSA complaint #11754203 — an unverified report by a vehicle owner.
Dublin, CA
UNKNOWN OR OTHER
The Full Self-Driving (Supervised) software on my 2026 Tesla Model Y repeatedly performs unsafe driving maneuvers requiring manual takeover to avoid collisions. Documented incidents with timestamps since June 3, 2026 include: selecting the incorrect lane and then attempting a route correction against a red light; activating the left turn signal while executing a right turn; attempting to enter a freeway from an incorrect lane; repeatedly missing exits, on-ramps, and turns; and making unnecessary lane changes. In one drive on June 9, the system missed two exits, a freeway on-ramp, a left turn, a right turn, and a U-turn twice within 18 minutes. On July 8, 2026, hours after the vehicle was returned from service with the manufacturer's advised mitigation active, the system repeated the same errors and drove the wheel into a curb, causing wheel damage. My safety and that of other road users was put at risk by incorrect lane positioning, incorrect signaling, and a red light conflict. The manufacturer's service center has inspected the vehicle twice (completed July 8 and July 21, 2026). Both visits were closed with no repair performed. The only action was advising me to disable the Online Routing setting as a temporary workaround, which did not prevent recurrence. The manufacturer stated in writing on July 8 that this is a known software-related matter its engineering teams are actively working to resolve, and a service advisor described it verbally as a firmware issue. However, the manufacturer's written response on July 31 states diagnostics identified no faults. A service center supervisor verbally acknowledged experiencing similar behavior on his own vehicle, indicating the defect is not unique to my vehicle. Service records, complete timestamped incident logs, and dashcam footage of the incidents are preserved and available for inspection upon request. No warning lamps or fault messages appeared before or during any incident.
NHTSA complaint #11754061 — an unverified report by a vehicle owner.
Austin, TX
UNKNOWN OR OTHER
Vehicle: 2024 Tesla Model Y (VIN: [XXX]) Incident Date: [Insert Date] Current Mileage: 4,094 Description: "While operating the vehicle at low speed, the vehicle experienced a sudden, uncommanded acceleration event. Despite immediate and sustained application of the brake pedal, the vehicle failed to decelerate as intended, indicating a critical failure of the braking-override system and/or the drive-by-wire acceleration logic. This represents a catastrophic safety defect that resulted in an uncontrolled trajectory. Furthermore, Tesla Inc. has formally refused to release the Event Data Recorder (EDR) data associated with this VIN and timestamp (Ref: DOT Request #xxx). This refusal obstructs a transparent safety analysis of a known 'Sudden Unintended Acceleration' (SUA) event. I am requesting a formal Office of Defects Investigation (ODI) into this specific hardware/software failure and Tesla’s data-withholding practices regarding safety-critical events." I am a XXX and the threat is to take the loaner car away my only transportation from [XXX] to [XXX] for my XXX. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
NHTSA complaint #11753764 — an unverified report by a vehicle owner.
Milpitas, CACrash
UNKNOWN OR OTHER
The FSD (full self driving) failed when it backed into my garage. All passengers are safe, including my wife (pregnant), mother, and [XXX] child. I was following the supervised FSD requirement by supervising the FSD with hands on steering wheel and foot on brake the whole time. The FSD left very little amount of time for me to react. Tesla insurance judges it is my fault. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
NHTSA complaint #11751919 — an unverified report by a vehicle owner.
Plano, TXCrash
UNKNOWN OR OTHER
Home link failure 1 Homelink was set to close the garage at 90 feet. Garage was open and I was parking manually going in reverse. Home link closed the garage as rear of my car was entering. Since tesla has a taller base and the wing like device projects beyond the car was damaged. 2 Homelink does not work consistently and this has put my home at risk because sometimes the garage door does not close as it is supposed to. 3 I had a service call. The technician saw the problem and claimed to have fixed it. He also said that he will tell the service manager about the damage and will see if they could fix the damage. 4 problem with this inconsistent behavior has continued. I have escalated the complaint with Tesla. I have called four times. All visited a service center in East plano. No one has contacted me to discuss the problem.
NHTSA complaint #11750494 — an unverified report by a vehicle owner.
Redmond, WA
UNKNOWN OR OTHER
Tesla Full Self Driving has no way to limit the speed or lane changes, and even in its standard profile it keeps going 15+ over the limit. Chill mode occasionally goes 10+, and Sloth switches between -10 and +5 erratically. It's unsafe to use and there's no way to do anything about it without a manual speed limit, like it used to have
NHTSA complaint #11750233 — an unverified report by a vehicle owner.
Pflugerville, TXCrash1 injured
UNKNOWN OR OTHER
I am writing to bring to your immediate attention a serious safety incident involving our brand‑new 2026 Tesla Model Y (Juniper), equipped with FSD version 14.2.2.5 and Software Version 2025.45.10. We purchased this vehicle as our dream car, and for nearly six months it delivered exactly what we hoped for—innovation, safety, and an exceptional driving experience. That trust was the foundation of our decision to choose Tesla. On [XXX], at approximately [XXX] in Frisco, TX, that trust was shaken by a sudden and alarming event. After coming to a stop and while making a routine right turn at under 10 mph, the vehicle unexpectedly accelerated on its own, causing an immediate loss of control. The entire incident unfolded in seconds, leaving no opportunity to react or correct the vehicle’s behavior. The incident happened at the intersection of [XXX]. The "Autopilot" feature in Tesla was on at the time of the incident. The impact was severe. The airbags deployed, the vehicle was declared a total loss by insurance, and first responders—including the Frisco Police Department—were required to clear the wreckage. My wife sustained injuries in the crash and continues to recover. Witnesses at the scene confirmed that the acceleration was abrupt and not driver‑initiated. The emotional and physical toll has been significant. More importantly, the nature of this incident raises serious concerns about a potential safety issue that could affect other Tesla owners. We feel compelled to ensure this incident is thoroughly examined. If there is a systemic issue—software‑related or otherwise—it is critical that it be identified and addressed to protect other drivers and uphold the integrity of the Tesla name. We truly miss our vehicle and the confidence we once had in it. We hope Tesla will treat this matter with the seriousness it deserves and provide a transparent path forward. Thank you for your time, attention, and commitment to safety. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
NHTSA complaint #11745911 — an unverified report by a vehicle owner.
Irvine, CACrash
UNKNOWN OR OTHER
I was driving on FSD mode, my car suddenly changed very fast to left lane by itself and hit the car on that lane right behind me.
NHTSA complaint #11744840 — an unverified report by a vehicle owner.
Jamesville, NY
UNKNOWN OR OTHER
While operating a 2026 Tesla Model Y on Full Self-Driving (FSD) Supervised, the vehicle's vision-based lane-keeping system failed on an unmarked residential road. At approximately 26 MPH, the vehicle approached a blind crest of a hill. Due to the lack of painted center lines, the FSD software miscalculated the road geometry and drifted significantly into the center/oncoming lane exactly as it reached the top of the hill. This lane departure created an immediate, severe safety hazard, as it placed the vehicle directly in the path of potential oncoming traffic with zero forward visibility over the crest. Due to the critical lane positioning error, immediate driver intervention was required. The driver took manual control of the steering wheel to force the vehicle back into the correct lane, causing the FSD system to instantly disengage. Simultaneously, the driver applied manual braking to reduce speed drastically down to 10 MPH to safely clear a resident working on the right shoulder and stabilize the vehicle. Prior to the failure, there were no warning lamps, error messages, or symptoms indicating the system would fail to maintain proper lane positioning. The system appeared to be functioning normally up until the crest of the hill. The vehicle and its Autopilot/FSD components have not yet been inspected by Tesla, police, or an independent service center following this specific event. The vehicle remains available for inspection upon request
NHTSA complaint #11742469 — an unverified report by a vehicle owner.
Inglewood, CACrash
UNKNOWN OR OTHER
Tesla 2026 Model Y was involved in a severe motor vehicle accident directly caused by a critical software and/or hardware malfunction of Tesla’s Full Self-Driving (FSD) system. At the time of the incident, the vehicle’s Full Self-Driving (Supervised) software suite was actively engaged and driving the vehicle. While navigating, the system suffered an abrupt and uncommented control malfunction. Despite prompt attention, the autonomous system executed an erratic, uncorrectable maneuver that overrode human intervention thresholds, completely failed to respond safely to the immediate driving environment, and directly caused a collision.
NHTSA complaint #11740400 — an unverified report by a vehicle owner.
Murrieta, CA
UNKNOWN OR OTHER
My bulldog died yesterday in the new Tesla y we bought because the side storage in the back doesn’t have a cover. I regret ever buying that car. The side storage should come with a cover especially for the size of the space. My explorer came with covers. She went in head first and suffocated to death. I pulled over as soon as I realized something was wrong and had do compressions on her in front of my kids. But it was too late. This is a safety issue. Fix it before it happens to other families. My family is devastated by this. People put their animals back there. It should be safe. We should be able to trust the product especially at the cost we paid. The car has dog mode which means it is supposed to be safe for you to leave your dogs in the car. It is not. I have records of her cremation
NHTSA complaint #11739989 — an unverified report by a vehicle owner.
Southwest Ranches, FL
UNKNOWN OR OTHER
Car is missing front trunk emergency release. Apparently standard on newer Tesla’s but it violates FMVSS 401 as a child can easily fit in the front trunk.
NHTSA complaint #11738758 — an unverified report by a vehicle owner.
Galena, OH
UNKNOWN OR OTHER
The latest Tesla autopilot software forces users to engage in an autopilot product survey after disengaging autopilot while driving in order to gain access to audio/radio controls. The survey is not dismissible without reading a complicated prompt and choosing a response, and it completely obstructs audio controls until you participate in the survey. The driver therefore cannot turn off music to listen for emergency sirens, pedestrians, or other potential safety cues while driving at any speed, unless the driver also takes eyes off the road to participate in the forced product survey. This is by design and affects all Tesla drivers who use the autopilot feature.
NHTSA complaint #11738266 — an unverified report by a vehicle owner.
Keller, TX
UNKNOWN OR OTHER
2025/2026 Tesla Model Y Juniper experiences noticeable vibration starting at approximately 75 mph on smooth highways. The vibration is felt throughout the entire vehicle: steering wheel, doors, seats, and pedals/floor. It is not limited to the steering wheel. Tire balancing, alignment, and foam checks have all been performed with no resolution. Tesla service states the issue is ‘normal/within spec.’ Video of the vibration with speedometer visible is attached. This matches a widespread pattern reported by other Juniper owners. Video: [XXX] INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
NHTSA complaint #11738360 — an unverified report by a vehicle owner.
Santa Clarita, CA
UNKNOWN OR OTHER
Subject: Safety Concern with Video Evidence (4/28/2026) I am reporting a serious safety concern involving Full Self-Driving (Supervised) on my 2026 Tesla Model Y. Date/Time: April 28, 2026 at approximately 12:48–12:50 PM Location: Soledad Canyon Rd at Golden Oak Rd / Golden Triangle Rd, Santa Clarita, CA While operating in FSD (Supervised), my vehicle approached an active railroad crossing with warning signals engaged and the gate lowered. The vehicle initially stopped appropriately; however, it then proceeded forward onto the tracks while the crossing remained active and a train was approaching. I immediately intervened and reversed the vehicle off the tracks to avoid a potentially dangerous situation. During this maneuver, the railroad gate made contact with the vehicle. I have preserved video footage documenting: * Initial stop at the crossing * Forward movement onto the tracks under FSD * Manual intervention and reverse maneuver * Contact with the railroad gate Following the incident, I observed linear markings across the windshield consistent with contact from the railroad gate arm. While some of the markings appear to be transferable residue, there are remaining visible streaks that have not been fully removed and may indicate surface damage. Photos and videos will not upload
NHTSA complaint #11735337 — an unverified report by a vehicle owner.
Austin, TX
UNKNOWN OR OTHER
I took delivery of a brand new Tesla Model Y today in Austin, Texas. Within less than two hours of delivery, the vehicle experienced two separate and serious failures while driving. During the first incident, the vehicle suddenly stopped in the middle of the road without any warning while I was driving. The vehicle became completely unresponsive and came to a stop in active traffic. I immediately contacted Tesla service for assistance. The representative advised me not to worry and stated that the vehicle likely came to a safe stop location and that there appeared to be no issue since the system had recovered. I was told the vehicle was safe to continue driving. However, this information did not reflect what actually occurred. The vehicle had stopped in the middle of an active roadway, not in a safe location.After the system temporarily became operable again, I continued driving as instructed. However, during a second drive shortly after, the exact same issue occurred again within approximately 10–15 minutes, this time on a much larger and heavily trafficked road. When the vehicle stopped both times, it became completely electronically controlled and unresponsive. There was no manual way to move or safely reposition the vehicle. I was stranded in the middle of moving traffic on a major road, unable to control or move the car in any way. I felt that my life was in danger due to the inability to regain control or remove the vehicle from traffic. Both incidents occurred on the same day of delivery within a very short time frame, making the vehicle completely unreliable and unsafe to operate. At least one of the incidents occurred while using self-driving features. Due to the repeated failures, the severe safety risk, and the incorrect reassurance provided during the first incident, I no longer feel safe operating this vehicle. I am requesting a buyback or refund rather than repair, as this issue occurred immediately after delivery and represents a critical safety conce
NHTSA complaint #11734432 — an unverified report by a vehicle owner.
Las Vegas, NV
UNKNOWN OR OTHER
My 2026 Tesla Model Y front trunk ("frunk"), an Austin, Mar 2026 build, lacks internal lighting & emergency release (unlike 2025 models; the change started Oct 2025). Frunk size/capacity remained unchanged, allowing child up to 4yo to fit & get trapped w/ no escape or signal, esp. in low light. Violates FMVSS 401 (https://www.ecfr.gov/current/title-49/subtitle-B/chapter-V/part-571/subpart-B/section-571.401) which states: "Each passenger car with a trunk compartment must have an automatic or manual release mechanism inside the trunk compartment that unlatches the trunk lid, if the trunk is large enough so that the three-year-old child dummy described in Subpart C of Part 572 can be placed inside the trunk compartment, and the trunk lid can be closed and latched". Request recall/retrofit & investigate Model Y frunk complaints. (See attached picture of 2025 frunk vs 2026 frunk with changed features.)
NHTSA complaint #11733278 — an unverified report by a vehicle owner.
Belle Fourche, SD
UNKNOWN OR OTHER
I bought this car new and it does not have a FRUNK emergency release or a FRUNK light.
NHTSA complaint #11730214 — an unverified report by a vehicle owner.
San Jose, CA
UNKNOWN OR OTHER
The emergency door release handle is cracked and has the potential to fail during an emergency. Tesla refuses to replace or repair under warranty.
NHTSA complaint #11729559 — an unverified report by a vehicle owner.
Katy, TX
UNKNOWN OR OTHER
Missing front trunk light/emergency release in violation of FMVSS 401.
NHTSA complaint #11728890 — an unverified report by a vehicle owner.
Fort Worth, TXCrash
UNKNOWN OR OTHER
Safety Defect: Uncommanded trunk actuation while the user was asleep inside the vehicle. The vehicle’s proximity-sensing system (Bluetooth Phone Key) triggered a full power-open cycle without any active user input. The system failed to recognize that the vehicle was occupied and failed to detect an external obstruction, resulting in a collision. This poses a severe risk of unauthorized vehicle access or personal injury while a user is sleeping or camping in the vehicle.
NHTSA complaint #11728094 — an unverified report by a vehicle owner.
Jersey City, NJCrash
UNKNOWN OR OTHER
With Full Self-Driving activated, while the vehicle was performing a maneuver to exit a parking space, it reversed directly into a stationary concrete pillar. The impact occurred on the rear driver’s side. There was no driver steering or pedal input during the reversal. The pillar was a large, high-contrast concrete structure, and there was insufficient time to intervene once the vehicle began reversing toward the pillar. Such defect in the Full Self-Driving system is dangerous for drivers and pedestrians alike.
NHTSA complaint #11726425 — an unverified report by a vehicle owner.
Las Vegas, NV
UNKNOWN OR OTHER
In under a year I have had to replace my windshield three times due to cracks from debris. The total cost would be greater than $4,000. I, nor my wife and family have ever had to replace a windshield on any previous car we had owned this many times in under one year or even at all. I suspect there is a defect in the build of the windshield or the design of the car that may be causing this.
NHTSA complaint #11724418 — an unverified report by a vehicle owner.