We Finance!!! 2007 Lexus Gx 470 4x4 Auto Roof Nav Rcamera 3rd Row Tow 1 Owner on 2040-cars

Auto blog

NHTSA may investigate new Toyota unintended acceleration case

After paying a $1.2-billion settlement to the US government last year, Toyota largely put the unintended acceleration recall behind it. Although, there were still some civil lawsuits to handle. A new case where the owner of a 2009 Lexus ES350 is petitioning the National Highway Traffic Safety Administration to open another analysis could draw the issue back to the forefront. Investigators are still deciding whether to research these claims further, though. According to this petition, the owner's wife was driving the ES350 in February 2015. While pulling into a parking space, the sedan allegedly surged forward, and there was a low-speed accident. The claim asserts there are at least two other similar cases in NHTSA's database: one in a 2009 Camry in 2009 and another in a 2010 Corolla in 2014. Specifically, this person wants an "investigation into low-speed surging in different models of Toyota automobiles in which the car starts accelerating and the engine RPM increases even when the accelerator pedal is not depressed," according to the agency. NHTSA will do further research into this person's claim and will decide whether to conduct a full investigation into the alleged issue. This won't be the first reappraisal of unintended acceleration in Toyotas by the agency in recent months, though. Between September 2014 and May 2015, NHTSA evaluated a similar petition with allegations covering 2006-2010 Corollas, and the government body decided to deny that one because the problem couldn't be replicated. Related Video: INVESTIGATION Subject : Low-speed surging Date Investigation Opened: JUL 09, 2015 Date Investigation Closed: Open NHTSA Action Number: DP15005 Component(s): VEHICLE SPEED CONTROL All Products Associated with this Investigation close Vehicle Make Model Model Year(s) LEXUS ES350 2009 Details Manufacturer: Toyota Motor Corporation SUMMARY: In a letter dated June 19, 2015, a consumer petitioned the National Highway Traffic Safety Administration (NHTSA) for an "investigation into low-speed surging in different models of Toyota automobiles in which the car starts accelerating and the engine RPM increases even when the accelerator pedal is not depressed." The petition was prompted by a February 2015 crash involving a model year (MY) 2009 Lexus ES350, which allegedly surged as the petitioner's wife was pulling into a parking spot.

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.

Translogic 165: 2015 Lexus RC F Biometrics Test

A traditional vehicle review goes like this: Reviewer drives car, reviewer gathers thoughts, reviewer relays vehicle impressions to audience. But what if instead of explaining what it's like to drive a given car, the reviewer could simply show the audience their response to the vehicle? With advancements in wearable biometrics technology, it's now possible to replace car review adjectives with cold, hard data. Translogic host Jonathon Buckley heads to Palm Beach Raceway in Florida to gauge his physiological reaction to driving the all-new Lexus RC F, with a little help from biometrics experts at Emotiv and Hexoskin. From his brain, to his body, Jonathon's vitals are measured as he takes to the track in Lexus's latest sports coupe. Follow Translogic on Twitter and Facebook. Click here to subscribe to Translogic in iTunes. Click here to learn more about our host, Jonathon Buckley. Lexus Technology Gadgets Coupe Performance Translogic