2013 Ls460 Like New! 8,223 Miles Call Maserati Of Marin For This Today on 2040-cars

Auto blog

Toyota recalling 20k 2014 and 2015 cars and CUVs with 3.5L engines

Toyota has announced a recall of roughly 20,000 vehicles covering the 2014 Avalon, Camry, Highlander (pictured) and Sienna, as well as the 2015 Lexus RX luxury crossover. The affected vehicles are all powered the 2GR-FE engine, which in layman's terms, is Toyota's well-regarded 3.5-liter V6.
According to Toyota's statement, a parts supplier might not have welded "the end cap on the right-hand fuel delivery pipe in the engine compartment" correctly, meaning fuel could leak. Leaking fuel, of course, increases the chance of an engine fire. That said, no fires, crashes or injuries have been reported due to the issue.
Owners will be notified to report to dealers, where techs will check the fuel delivery pipe and fit a replacement part as necessary.

Lexus teases Detroit-bound F Performance Coupe... again

A few weeks ago, Lexus released a teaser image of its upcoming Detroit Auto Show reveal, simply calling it the "next Lexus F." Now, a new shot of the Detroit-bound car has been sent out, and while we still don't know what the new model will be called, we can tell you this: it's a coupe.
Originally, we assumed the new Lexus F model would be the successor to the IS F sedan. But now that we know it'll be a two-door, it stands to reason that this could be the performance oriented version of the 2015 RC coupe that made its debut at the Tokyo Motor Show earlier this year. Of course, Lexus is still keeping quiet on any specifics, simply stating that the company "will unleash its upcoming F model as a coupe, conceived with grit, an entirely new expression of design and uncompromising performance."
The official name of the new F model is set to be revealed in early January, likely just before its official debut in Detroit. Stay tuned for more, and scroll down to read Lexus' very brief press blast.

Google shares more details on self-driving car accidents

Google has pledged to release monthly reports on the status of its self-driving car program, and says these updates will include information on accidents involving the vehicles. But the company won't release the actual accident reports, a sore point for activists who recently have clamored for the company to be more transparent in the way it tests this promising technology on public roads. "Google is dribbling out bits of information in the hope to silence legitimate calls for full transparency," said John Simpson, privacy director for Consumer Watchdog, a nonprofit that has asked Google to release reports from the 12 accidents the company says it has been involved in over the past six years. "They are testing on public roads, and the public has a right to know exactly what happened when something goes wrong." Under California law, the accident reports are not considered public records. Google has attributed all accidents to human error, and says drivers of the other cars involved caused 11 of the 12 accidents. In eight of those, the Google cars were rear-ended, and the autonomous vehicles were sideswiped in two other crashes. One of the accidents occurred at an intersection when a human driver failed to yield at a stop sign, and in one incident, a Google driver accidentally rear-ended another car while manually driving. Google had previously provided those details. The first monthly report installment sheds new light on which types of self-driving vehicles were involved, directions of travel, locations, and whether the cars were operating in autonomous or manual mode. Update: Google says this information comes directly from the OL 316 forms used to report accidents involving autonomous cars in California, though it has "edited the summaries lightly to protect other drivers' information." But Google still will not release the original OL 316 forms, nor the "traffic collision report" forms used in California to report accidents. Another company that has been involved in a single self-driving car accident, Delphi Automotive, has released this information, which verified its car was not at fault. Regarding Google, Simpson said, "We now know a few more details of what happened. The problem is that it's Google's version and they want us to take their word for it." The Google self-report adds information that goes beyond accidents, with further details on the company's overall program.