NHTSA Complaint #11507834 — 2020 NISSAN ROGUE

In October of 2022, While I was driving my 2020 Rogue on a country road to a school event for my granddaughter, the car made a soft bell sound then it immediately slammed on the brakes for no reason that I can understand. I immediately pulled the car off the road. It showed a triangle with an exclamation point within it in the dash display. I shut the car off and when I restarted it the triangle was gone and it drove ok. I later read online that this could be an AEB issue. It was a clear day with no rain and no cars close in front and, luckily, behind me. It scared the hell out of my wife and I. I no longer feel safe in the car if it can do this for no reason! I brought the car into a Nissan Dealer to have it checked on 9/20/22. They did not find any problems with it. They also did not see any fault codes that something happened within the vehicle's memory. I find it unbelievable that the car did not record the fault. To me this means that Nissan has deliberately disabled this function for this fault. I have done a lot of research and apparently this is a well known issue with Nissan vehicles, not just the rogues. I have also read that there are 2 class action suits against Nissan for this. I brought the vehicle in again in Jan 2023 to get the car checked again for the False Activation of AEB, FEB, or FCW. This time I asked to have it checked per NTB18-041D and reprogrammed to the latest software and/or any required hardware to fix this well known issue. They said this NTB was not for my rogue and did not fix it. I have read that this is normal for this defect shown in the NTB. I am still afraid to drive this car and have only driven it about 400 miles since it was looked at. And now I only drive it with the AEB disabled as I was instructed by a tech in the service dept. I would really like to be able to use the AEB safety feature without fear of it falsely locking up the brakes while I'm driving. This Rogue only has 6835 miles on it.