Administrator
Administrator
- Joined
- Nov 26, 2018
- Threads
- 262
- Messages
- 1,057
- Reaction score
- 3,620
- Location
- Rivianforums.com
- Vehicles
- Rivian
Same exact R1T prototype from its better days. ?
Sponsored
Announcing our new "CLUBS" section where you can join or create a Rivian club or group! You can use this new feature to conveniently plan and discuss local events, gatherings or other club/group related topics.
So we encourage you to join (or start) special-interest and regional-based Rivian clubs at: https://www.rivianforums.com/forum/group-categories/clubs-groups.1/
Hmmm. Maybe one our forum friends, say in the insurance field, in California, could pry it out with a request for a copy? Or bending the rules too much?dude I was checking this 1 hour ago, Irvine county has specific reqs and not available to public but how hilarious you thought of that as did I LOL.
That wouldn't match the very straight tracks across the grass. If the loss of control was because of a broken tie rod, the left wheel wouldn't have tracked straight that far. If the tie rod is broken, it almost certainly happened on impact with one of the other cars.I think the tie rod went when trying to go around the corner, and then it was code brown for the driver from there.
Calm down, joking. SheeshFor what exactly? Not being crashproof??
Given that this wasn't a highway, I don't think it would be a Driver+ issue. Not impossible since it's a test vehicle, though.Yikes, hope it wasn't driver+.
Could be but they were running with the ATs at the time of the crash.Same exact R1T prototype from its better days. ?
“On tape”?! ?
Looks like there is at least one camera in the area on the corner of the building to the north east of the turn. If it was pointing at the entrance of the parking lot it's next to, this would all be on "tape" somewhere. I'm sure they'll be getting a call from the NHTSA tomorrow.
Like everyone has said, really hope this was just an unfortunate traffic situation and hope everyone was OK, but I'm sure the driver will have a tough time sleeping the next few days.
I would actually argue the opposite and help explain the S shape of the left track.That wouldn't match the very straight tracks across the grass. If the loss of control was because of a broken tie rod, the left wheel wouldn't have tracked straight that far. If the tie rod is broken, it almost certainly happened on impact with one of the other cars.
To me it looks like impact with the curb broke the tie rod.I would actually argue the opposite and help explain the S shape of the left track.
Hmm... could be. I was reading that as an optical illusion due to the slope of that hill. Now that I look at the Google Street View though, I think I was misreading several parts of that hill. The photo of the wreck distorts several things, so, yeah, maybe that's what happened. Or maybe the tie rod broke when the R1T hit the curb.I would actually argue the opposite and help explain the S shape of the left track.
That’s exactly what I’m worried about. Seems likely to me it could be a Driver+ mishap.Man that is crazy. Pretty light damage to the Rivian compared to the other vehicles.
Lets just hope it wasn't the autonomous driving system. If so we are going to have some delays.
No way a broken tie rod caused this much damage without other mitigating factors. From 40 or 45 mph, you easily could have stopped the truck or at least scrubbed enough speed to limit the damage before that impact.Hmm... could be. I was reading that as an optical illusion due to the slope of that hill. Now that I look at the Google Street View though, I think I was misreading several parts of that hill. The photo of the wreck distorts several things, so, yeah, maybe that's what happened. Or maybe the tie rod broke when the R1T hit the curb.
If the tie rod simply failed while driving down the street, that's a potentially disastrous issue that Rivian must resolve before it ships any cars to customers. If it failed because of a direct hit on that curb at 30+ mph, then I'm not as concerned.
Or… prototype being driven with beta/future version of Driver+Let's see.... younger male driver making an error (this is obviously a very rare occurrence /s) or major software defect with Diver+ safety features that are only enabled on "certain highways at launch"?
Idk y'all... tough to tell.