2014 Toyota Venza Xle on 2040-cars

Auto blog

BMW i5 could get Toyota-sourced hydrogen power

It's starting to feel like the automotive landscape is right on the cusp of a boom in hydrogen-fueled vehicles. After all, the Toyota FCV is nearly ready, Volkswagen is readying a fuel cell concept for this week's Los Angeles Auto Show and Hyundai already sells its Tucson Fuel Cell. The next big name to add to that list might be BMW, as the company's co-development deal with Toyota starts to bear fruit.
According to Autocar, BMW may use a version of the fuel cell system from the Toyota FCV in the future i5. As part of its eco-oriented i sub-brand, the i5 is expected to be a stretched version of the i3 (pictured above) with extra rear legroom and cargo space. It's unclear at the moment whether a battery-powered pure electric powertrain will also be available. If accurate, then the rumor could give the Bavarian brand a counterattack against Mercedes-Benz' planned fuel cell vehicle in 2017.
BMW and Toyota first signed the memorandum of understanding to co-develop fuel cells, lightweight technology and a sports car back in 2012, and they made the arrangement official in late 2013. So far, few details on the progress of the work have been disclosed, but the performance model has been rumored to use a front-engine, all-wheel drive layout with supercapacitors.

Union to launch Toyota organization drive in Canada

Toyota may be heading toward some labor issues in the Great White North, as employees at a pair of Canadian Toyota factories may be set for a certification vote. The Unifor union, which was the result of a merger last year between the Canadian Auto Workers and the Communications, Energy and Paperworkers union, will be holding the vote.
Over 40 percent of the employees at the Woodstock and Cambridge, Ontario factories have signed union cards, cresting the minimum percentage required to instigate a legal certification vote, according to Reuters. The Woodstock factory is responsible for RAV4 production, while Cambridge builds the Lexus RX350 and RX450h, as well as the Toyota Corolla. The two factories employ nearly 7,000 people.
It's unclear when the union will hold a certification vote at the two factories, but what is rather clear are the worker complaints. Employees are concerned about workers being hired on temporary contracts which lack the benefits of full employment, John Aman, head of organizing for Unifor, told Reuters.

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.