What 62 owners told NHTSA about the 2022 Rivian R1t Bev

We were driving on the highway going 70 MPH when we heard a loud bang, and then the car immediately catapulted to the right off the road and slammed into the concrete right median, spun around hit a sign and then ended up in the right bridge barrier (shoulder). During the crash 6 airbags deployed from the impact of the crash. The highway patrolman stated that you could see the driver-side rear wheel started skidding based on the marks on the road. We thought it was a blown tire. But the tires were all in tact. The driver-side rear wheel was turned out and it was clear that the toe-link joint had separated from the wheel axel and this is what caused our crash. The car has been totaled by insurance company and taken salvage yard in Knightdale, NC. We were both wearing seatbelts, and I (the passenger) was thrown around during the crash and ended up going to the hospital with neck and back pain. I have severe neck misalignment and soft tissue damage on my neck and back. I was unable to work for 4 days after the accident and still am not able to sleep well due to pain. We were in the right hand lane of the highway and did not hit any other cars, but if we had been in a different lane we could have hit another car and caused more injuries and damage. The problem that caused the accident was the problem that was listed on the product recall, we had an appointment to get it fixed the next day. We had the car towed to the Rivian service center where they verbally confirmed it was the toe link that separated. It was inspected by the police, the Rivian Service Center and our insurance adjuster. There was zero warning prior to the loud bang other than the recall notice We

NHTSA ODI 11730254

I was driving late night to a campsite in a very rural part of the Big Island of [XXX] , about 45 minutes from where I live. I was by myself except for my dog, in the passenger seat. I was on a country road with a 30 mph speed limit, going about 25 mph. I engaged the cruise control and it immediately went up to 40-45 mph, far faster than the limit and far faster than was safe given the wet conditions and windy road. As I tried to slow the car down, using the steering while cruise control adjustment buttons, I steered through a curve and rather than turn with the road, as I had intended, the truck slid off the road to the left, effectively hydroplaning, into two trees, at about 40 mph. The airbags deployed as the truck came to a complete halt against the two trees. The car automatically called 911 as I sat there trying to assess what had just happened, whether I was hurt, and whether my dog was hurt. I told the 911 operator that the truck had called them automatically adn that I was ok and I would call in the morning after assessing what had happened. I am waiting for the police report and also waiting for the incident report from Rivian, which has an on-board log of events. I don't know why the cruise control engaged at such a high speed, rather than at the posted speed limit, but this appears to be a known flaw with Rivian's cruise control that I was not aware of. The cruise control and software are available for inspection by NHTSA. There is also an active recall on this vehicle that I was aware of but had been unable to schedule for service yet b/c it required shipping the truck to [XXX] on a barge. I had only had the truck on island for a little more than a month. From previous operations I had no reason to believe that the cruise control was faulty. It is possible that the recall issue may have been a contributing factor to the crash but I don't know b/c the vehicle has not been inspected yet by Rivian. They have scheduled an adjuster to come on April 14. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

NHTSA ODI 11729578

The contact owns a 2022 Rivian R1T. The contact stated while making a left turn the vehicle would not allow the contact to straighten the steering wheel, causing the vehicle to run off the road and struck a small tree. The contact was able to control the vehicle and was able to drive home. The vehicle was diagnosed, and the bolts of the steering system were tightened. The manufacturer was contacted but offered no assistance. The failure mileage was 12,000.

NHTSA ODI 11509327

******* DELETE VOQ ******* THIS COMPLAINT IS BEING MARKED FOR DELETION BECAUSE IT IS AN INADVERTENT DUPLICATE OF ODI# 11504269*DJR ******* DELETE VOQ *******

NHTSA ODI 11504377

While preparing to pull out of a parallel street parking space in my R1T with a car 3 feet in front of me, I stepped on the brake to engage Drive from Park. On releasing the brake, before stepping on the accelerator, the R1T surged at a high rate of speed hitting the car straight on, deploying the air bags in the car and blowing the rear window out of the car. The car was pushed past an empty space, 20 ft or more, into another parked car. This all happened in 2-4 seconds. The R1T surged as if the accelerator had been push to the floor surprising me and pushing me back on the driver seat. The R1T stopped when I braked. The car was totaled. The driver of the car was taken to the hospital with minor injuries but might lead to later back and neck injuries. At no time did the R1T's alarms activate. The R1T is estimated to go from zero to 60 MPH in 3 seconds. Although contacted and advised of the accident Rivian has not accepted responsibility or offered proof otherwise. The only way to prove if this accident was either driver error or systems error is to get an analysis of my R1T computer system for the 2-5 minutes before, during and after the accident. I have requested this report from Rivian 4 times and have spoken with 3 people and have 2 emails. At no time while speaking with Rivian employees was I told they cannot do the analysis, until the final response which came from the Rivian legal Department, sixteen days after my first request. The report stated - "Rivian requires a valid subpoena to provide vehicle data.” From my Rivian R1T computer screen: "Rivian Data Analysis: Shares precise location data with Rivian for data analysis, which are used to improve our products and services.” I do have an insurance case number and a police report number on this accident. We have owned the truck since 8/2022.

NHTSA ODI 11504269

Truck without warning, suddenly stopped and I was on one of the busiest streets in Los Angeles at an intersection, blocking a large amount of traffic and too dangerous to get out due to cars rapidly passing. Called Rivian support and they said it would take. two hours to get a tow truck to me even though AAA was only 20 min away, they would not call AAA. I was at risk of being rear ended. Fire department came and was able to move car to side of road. Rivian gave no assistance. Engine light came on and said call tow truck and do not drive, red lights, manual said it was dangerous.

NHTSA ODI 11490062

I DO NOT OWN THIS VEHICLE. I WAS HOWEVER, INJURED BY THE DRIVER OF THE 2022 RIVIAN LAUNCH EDITION. I WAS REAR ENDED (WHILE I WAS STOPPED WAITING FOR A READ LIGHT) AT A RELATIVE HIGH SPEED FOR ROAD CONDITIONS. AFTER STUDYING THE OWNERS MANUAL, THERE ARE MULTIPLE COLLISION AVOIDANCE WARNINGS, AUDIBLE, VISUAL AND HAPTIC (VIBRATION OF THE STEERING WHEEL) WHEN A COLLISION IS IMMINENT. FURTHERMORE, THE AUTOMATIC EMERGENCY BRAKING FEATURE AND BRAKE ASSIST SHOULD COMPLETELY PREVENTED ME FROM BEING REAR ENDED AND INJURED AS A RESULT. i APPEARS THAT THE VEHICLE ACTUALLY ACCELERATED INTO THE REAR OF MY VEHICLE. DUE TO THE WEIGHT OF THE VEHICLE (7150LBS), THE "SKATEBOARD" LOW CENTER OF GRAVITY OF THE FRAME, THE 0-60MPH IN 3 SECONDS POWER (850HP - 908LB-FT TORQUE) AND THE PROTRUDING FRONT TOW HOOK, AND THE ABOVE SAFETY FEATURES NOT OPERATING AS DESIGNED, A HIGH CONCENTRATED AMOUNT OF FORCE STRUCK MY VEHICLE AND AS A RESULT IS WAS INJURED. (REPORTED TO CALFORNIA DMV) DATE OF ACCIDENT 06/29/2022

NHTSA ODI 11486117

The Driver+ (D+) feature on the Rivians have both adaptive cruise control and lane centering active at the same time. There is a function unknown to me that controls whether or not the D+ feature can turn on or remain on. In certain situations, the D+ features asks the driver the disable the system by pushing the right stalk upward with a red message on the gauge console screen. In other situations, the D+ feature forcibly disables with a similar red message on the gauge console screen. The messages themselves look very similar at first glance and require the driver to look down to discern between the two because the outcome for both scenarios is very different, particularly when D+ forcibly disables itself. When D+ disables itself (again the reasons are unknown to me at the time and not predictable other than maybe GPS location), there is a VERY brief warning to the driver then turns off and automatically brakes the vehicle. This D+ error is not as common as the other warning described above that asks the user to push the right stalk upward to turn it off. Once D+ forcibly turns itself off, the vehicle brakes aggressively. Due to muscle memory of the other similar-appearing error, it is normal to push the right stalk upward to disable it. Herein lies the issue: the vehicle is aggressively slowing down and pushing up on the right stalk (seemingly to disable D+) actually puts the vehicle into Reverse drive. This is because the vehicle does NOT require the brake pedal to be pressed to change into Reverse at low speeds (threshold unknown). This results in unpredictable and unexpected behavior of the vehicle within the matter of a few seconds. When the driver thinks they are disabling D+, they are unexpectedly putting the vehicle in reverse, so when accelerating from the stop caused by D+ the vehicle moves in reverse. This is most prevalent when using D+ in stop/go to light traffic and resulted in reversing on the freeway into another vehicle.

NHTSA ODI 11482330