The December 2022 issue of IEEE Spectrum is here!

Close bar

The LA Times, which over the past several weekends has been digging into the sudden unintended acceleration (SUA) problems in Toyota and Lexus cars following the fatal crash of California Highway Patrol Officer  Mark Saylor and his family in August, published another story Sunday that claims that the National Highway Traffic Safety Administration (NHTSA) repeatedly closed investigations into SUA complaints prematurely.

The Times story says that there have been at least 8 investigations into SUA in Toyota and Lexus vehicles since 2001 triggered by more than 1,000 driver complaints. All but two of the investigations were closed without finding any defect.

However, as the Times notes,

"... those [closed] investigations systematically excluded or dismissed the majority of complaints by owners that their Toyota and Lexus vehicles had suddenly accelerated, which sharply narrowed the scope of the probes... Federal officials eliminated broad categories of sudden-acceleration complaints, including cases in which drivers said they were unable to stop runaway cars using their brakes; incidents of unintended acceleration lasting more than a few seconds; and reports in which owners did not identify the possible causes of the problem."

By excluding these types of what appear to be legitimate complaints, the NHTSA then closed their investigations because there wasn't enough data to support an investigation.

For instance, the Times notes that, "In a 2003 Lexus probe ... the agency threw out all but one of 37 customer complaints cited in a defect petition. It then halted further investigation, saying it 'found no data indicating the existence of a defect trend.' "

Then, the paper reported, "In 2005.., Jordan Ziprin of Phoenix, who had experienced a minor accident he blamed on sudden acceleration, filed a defect petition with the NHTSA that included nearly 1,200 owner complaints about Toyota vehicles. The automaker argued that the majority should be eliminated because they dealt 'with two completely different issues.' "

"When owners said the 'vehicle unintentionally or suddenly 'accelerated,' Toyota claimed that represented a different issue than when they said "the vehicle 'surged' or 'lurched.'  The NHTSA ultimately went a step further, eliminating every single complaint except Ziprin's, finding them to have 'ambiguous significance.' "

Interesting Catch-22s.

NHTSA officials admitted that the exclusions were made, but defended the practice in a statement to the LA Times:

"While some vehicles may be excluded from the scope of an investigation into a specific defect allegation, all are continuously reviewed, along with other relevant information, in order to identify other emerging issues of concern."

The NHTSA insists that, "Safety is the No. 1 priority" of the agency.

However, the NHTSA also has refused to reopen investigations it has closed even if new information surfaces, the LA Times says. For instance, a reason for tossing out complaints was an assumption made in 2004 by the NHTSA and Toyota that brakes can always overcome a vehicle's engine and stop a car.

Both the NHTSA and Toyota now admit that may not be true.

A report over the weekend in Bloomberg News says that more people are suing Toyota for SUA involving their vehicles. It may be that the courts - and maybe more importantly the court of public opinion - which will decide whether Toyota vehicles are safe or not, not the NHTSA.

The Conversation (0)

Why Functional Programming Should Be the Future of Software Development

It’s hard to learn, but your code will produce fewer nasty surprises

11 min read
Vertical
A plate of spaghetti made from code
Shira Inbar
DarkBlue1

You’d expectthe longest and most costly phase in the lifecycle of a software product to be the initial development of the system, when all those great features are first imagined and then created. In fact, the hardest part comes later, during the maintenance phase. That’s when programmers pay the price for the shortcuts they took during development.

So why did they take shortcuts? Maybe they didn’t realize that they were cutting any corners. Only when their code was deployed and exercised by a lot of users did its hidden flaws come to light. And maybe the developers were rushed. Time-to-market pressures would almost guarantee that their software will contain more bugs than it would otherwise.

Keep Reading ↓Show less
{"imageShortcodeIds":["31996907"]}