2014 Toyota Sienna L on 2040-cars

Auto blog

eBay Find of the Day: Back To The Future Marty McFly 1985 Toyota SR5 pickup tribute

With DeLorean time machine replicas thick on the ground, it was only a matter of time before someone started recreating the other vehicles in the McFly garage. At the end of the first Back to the Future movie, Marty returns to 1985 to find his sweet-looking Toyota SR5 truck all waxed and ready for his date. That truck always did look great in the movie, and now's your chance to own this close facsimile.
This Back to the Future replica Toyota is on eBay with a price of $14,500, which the seller claims is half of what's been invested. Perhaps that's true, but it's still a nearly 30-year-old truck that's covered 280,000 miles. The seller does say the 22RE engine has been recently rebuilt, along with the rest of the drivetrain, and there's new paint, too. The attention to detail is admirable, and if you've always admired Marty's '80s-chic 4x4, now's your chance to own it.

Toyota Supra, Rolls-Royces, dozens of BMWs recalled for backup camera issue

Weeks after Nissan and Infiniti recalled more than 1.2 million vehicles for a potentially dangerous programming oversight in the backup camera settings, BMW has issued a recall for similar problems. The recall, which covers 257,481 vehicles, includes numerous BMWs, as well as two Rolls-Royce models, and the 2020 Toyota Supra.  In total, the recall potentially affects 51 different products. This includes the 2018 BMW 540D, 2018–2019 BMW 640I, Rolls-Royce Phantom, 2018–2020 BMW 530e, 530i, 540i, M5, M550i, X3, 2019 Rolls-Royce Cullinan, 2019–2020 BMW 330I, 740Le, 740Li, 745Le, 750Li, 840i, M340i, M850i, X4, X5, X6, X7, Z4, and 2020 Toyota Supra. On certain BMW models, xDrive variants are also included. According to NHTSA campaign No. 19V684000, "The back-up camera and display settings can be adjusted such that the rearview image is no longer visible and the system will retain that setting the next time the vehicle is placed in reverse." If there is no display image when backing up, drivers can't properly see, and the car no longer meets modern safety regulations. Specifically, Federal Motor Vehicle Safety Standard (FMVSS) number 111, "Rearview Mirrors."  The recall was filed on September 27, 2019, and BMW plans to begin notifying affected owners in November. BMW, Toyota, and Rolls-Royce dealers will update the vehicles' software, which should fix the problem. 

Toyota settles first wrongful death suit related to unintended acceleration

Toyota's sales seem to have rebounded from the unintended acceleration issues from 2009 and 2010, but the automaker is far from done dealing with this situation. Following a settlement worth up to $1.4 billion for economic loss to affected vehicle owners, Toyota has settled rather than going to trial in a wrongful death lawsuit stemming from an accident in Utah in 2010 that left two passengers dead. This isn't the first case in which Toyota has settled, but it was the first among a consolidated group of cases being held in Santa Ana, CA.
According to The Detroit News, this case was scheduled to take place next month, and it was for a November 2010 incident in which Paul Van Alfen and Charlene James Lloyd were killed in a Camry when, based on findings by the Utah Highway Patrol, the accelerator got stuck causing the car to speed out of control and hit a wall; the terms of the settlement were not announced.
The article says that while Toyota will settle on some cases, it doesn't plan on settling on all of them as it still wants to be able to "defend [its] product at trial." This will probably be the case in suits claiming that software for the drive-by-wire accelerator was the cause of an accident in a Toyota or Lexus vehicle. The question of whether or not the electronic accelerator played any role in this problem has been a hot-button topic since the beginning. Toyota has issued recalls in the past to attempt to prevent unintended acceleration caused by trapped floor mats and faulty accelerator pedals, but it also says driver error was to blame in some instances.