2005 Lexus Rx330,clean Tx Title,rust Free,red Tag Sale on 2040-cars

Auto blog

2013 Lexus LS460 F-Sport AWD

Gary Approved
There's a guy that goes to my gym who can't get enough of the Lexus LS - let's call him Gary. Gary's the guy - you've probably got one at your gym, or coffee shop, or some other public but quasi-social location - who talks to everyone he meets. Sit next to him on the rowing machine or run by him on the track, and he's almost certainly going to bend your ear for a minute or 20. Gary is in his mid-60s, a business owner, and the super-proud owner of a 2013 Lexus LS.
Not being a shy man, Gary will be the first one to tell you that he didn't do much comparative shopping (he "drove by" the BMW dealership, and looked at a 7 Series "on the computer"). Being a satisfied former owner of multiple Lexus RXs, there was probably only a tiny statistical chance that Gary wouldn't end up in an LS when it came time for him to treat himself to the tricked out luxury car that he'd wanted for a long time. Still, when I found myself chatting with Gary about his new LS, right after I had spent a wintry week in the 2013 LS460 F-Sport AWD, I figured that he'd have some light to shed on the car.

Lexus gives Jay Leno a shot at driving its 2014 IS

After we drove a prototype of the 2014 Lexus IS, we were told that Lexus was shipping it back to Japan. As it turns out, late-night funnyman Jay Leno was already in the motherland with the coming sport sedan, and he lapped it around Fuji Motor Speedway with Chief Engineer Junichi Furuyama.
This was probably during his LFA drive two months ago, actually, when Furuyama-san was even more tight-lipped about the IS than he was a week ago, so Leno has to make the best guesses he can. Leno goes over the whole car, then takes it out for a casual spin, so at least you get to see it in action. As for Jay's take, you'll just have to watch the video below to find out.

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.