2023 Rivian R1S

On our drive back from Yosemite, we began descending from Groveland, CA after leaving the Rivian charging station. Due to heavy rain, the car ahead of me was moving cautiously, limiting my speed to about 20 mph while maintaining a safe distance during the descent to Moccasin, CA. Thanks to the regenerative braking, I didn’t need to apply the brakes, as the car automatically slowed when I wasn’t pressing the throttle. However, my windows started to fog up, so I turned on the defoggers. Shortly after, I noticed the car’s door locks repeatedly unlocking and locking by themselves. As we neared the bottom of the descent, I began to smell something burning from the vents. This prompted me to step on the brake pedal for the first time, but it felt unusually stiff, with little travel. The car didn’t slow down, and the burning smell intensified. I pressed the brake pedal repeatedly, but it felt stuck, and the car did not decelerate. Eventually, I was able to roll to a stop. I pulled over to a side street where the issue persisted. I turned off the defogger and contacted Rivian via SOS. We were able to replicate the brake issue on the side street: as I maneuvered the car, the brake pedal sank on its own when the defogger was on. Once I turned it off, the pedal returned to normal. There were no warning lights or alerts from the car system. When I got out of the car, the burning smell was strong near the front wheels. It was clear that my family’s safety was at risk, including 3 young children. The car was towed to a service center, where it’s being inspected. Rivian hasn’t been able to reproduce the issue yet. I believe the regenerative brakes weren’t working properly, causing the car to rely on the regular brakes for the entire descent. This likely led to brake failure at the bottom, with the burning smell originating from overheated brakes. I also suspect that the overheating caused other electrical issues, which could explain why the door locks kept cycling on and off.

What component or system failed or malfunctioned, and is it available for inspection upon request? — ACCELERATOR PEDAL. YES, AVAILABLE FOR INSPECTION. How was your safety or the safety of others put at risk? — DUE TO ACCELERATOR PEDAL DEFECT, IT RESULTED IN ONE CASUALTY AND ONE INJURY. Has the problem been reproduced or confirmed by a dealer or independent service center? — YES, SERVICE RECALLS HAVE BEEN FOR THE SAME ISSUE WITH PRIOR MODELS. Has the vehicle or component been inspected by the manufacturer, police, insurance representatives or others? — CURRENTLY IN POLICE CUSTODY Were there any warning lamps, messages or other symptoms of the problem prior to the failure, and when did they first appear? — NO WARNING SIGNS.

I was at 44% state of charge and the ambient temp was around 65 F. While taking a turn at an intersection, the vehicle reduced regenerative braking(regen bar on the vehicle was greyed out) had I had quickly break as the car started to coast. This only lasted for 8-10 secs and the vehicle had regular regen breaking. Rivian don’t have blended braking, so if that had happened in different situations that needed much faster reaction time I would be in trouble. Issue 1: vehicle randomly decided to go into reduced regen for a brief period even at ideal conditions for regen( low SoC and normal temp, vehicle drive only for 5 mins) Issue 2: There is no blended braking to compensate for this in such situation, putting the driver/passengers at risk

Stopped at McDonalds drive through waiting to order with my foot on the brake and the vehicle lunged forward rearending the car stopped 5 feet in front of me ordering. I was trying to brake but it kept pushing the car in front of me then careened to the right hitting a sign and a parked car. I kept pumping the brakes and I thought it was going to run into a building when the vehicle finally stopped about 30 feet from the 2nd parked car it struck. Apparently it was "sudden unintended acceleration" and I've been reading on-line this has happened to many people including Actor Alan Ruck (see article). Rivian has not been responsive to us. Crash involving ‘Ferris Bueller,’ ‘Succession’ actor Alan Ruck was not a crime: LAPD by: Marc SternfieldPosted: Nov 2, 2023 / 03:22 PM PDT No charges will be filed as a result of the multi-car crash in Hollywood involving “Ferris Bueller” and “Succession” actor Alan Ruck, Los Angeles Police told KTLA on Thursday. The collision happened around 9 p.m. on Halloween night at the busy intersection of La Brea Avenue and Hollywood Boulevard. In two surveillance videos obtained by KTLA, Ruck’s Rivian electric pickup truck is seen stopped behind another car at a red light as pedestrians cross in the crosswalk. For reasons still unclear, the truck suddenly lunges forward and rear-ends the other car, and then careens across lanes of traffic, hitting another vehicle before crashing through the wall of Raffallo’s Pizza. At least one person is hospitalized after a three-vehicle collision sent a truck crashing through a pizza shop in Hollywood on Oct. ... Actor Alan Ruck is seen at the crash scene. Tim Ratcliff, who owns several adjacent restaurants, rushed to help the actor who he says was more concerned about the safety of the people he hit than his own wellbeing. “I asked him, ‘Are you okay? And the first thing out of his mouth was, ‘Is everyone [else] okay? I think I hit someone. Is he okay?’,” Ratcliff told KTLA.A 32-year-old man from one of th

One fine morning, went to start the car and the car threw a bunch of error messages related to servicing 12 V battery system and dis-engaged the parking brake that lead the vehicle to start rolling down the driveway. The message on screen warned of applying brakes, and luckily circumstances were safe around the car, and I was able to apply brakes and was able to reboot the car and systems restored. Considering this vehicle does not have traditional ignition and is capable of waking up via remote application, and this incident happened merely as the vehicle was waking up, this can be a dangerous situation especially if it happens while unattended. The vehicle does not have mechanical parking brake controls, and is completely computer controlled. The fail safe condition around parking brake systems and circuit/software faults need to ensure parking brake stays engaged during any computer faults.

Immediately after purchasing the vehicle, I got error codes thrown to service the suspension while driving to my house, specifically at 15-20mph over traffic calming bumps. This fault cleared immediately the first few times. On July 25 I submitted a service request as my family headed out on a two week, 900 mile trip. The service suspension fault had returned and disabled my ability to change modes/ride heights, blind spot sensors and cruise control, all of which I was counting on using during trip. I shut off and restarted the vehicle several times trying to clear the fault and regain functionality, but the fault inevitably returned. On July 25, Rivian added a response in the service portal that they would address the problem by July 28th. I heard nothing more. On August 1, I was driving south on HWY 57 in North Idaho. I hoped that code would have cleared, but it came back on almost immediately. After driving for about 5 miles, I decided to pull over at a visitor center parking lot to try and reset again to change modes, regain safety sensors, and cruise control. While turning left into the parking lot, another driver tried to pass on my left on a double yellow line driving above the 55mph speed limit. He collided with the front left part of my vehicle, damaging the body and breaking the front tie rod ends, leaving me unable to steer or drive forward, disabled, in the oncoming traffic lane. I asked Rivian to share data about the turn signal use, brake light, and speed data at the time of the accident with me. They did not respond in writing, but called and refused, getting quite angry during the call. After researching and observing other Rivians, I don't believe that my brake lights were on during regenerative braking. The rear, side, and blind spot sensors were disabled. Turning 1/4 second sooner or 5º sharper would have killed me.