NHTSA Recall Wave Hits Waymo Robotaxis and Ford Trucks
By @sharedot · · 7 pages
- Automotive
- Autonomous Driving
- Vehicle Recalls
- Waymo
- Nhtsa
Waymo recalled 672 robotaxis after a Phoenix pole strike while Ford, GM and Land Rover issued their own NHTSA recalls.
What happened: 672 driverless cars recalled
Waymo, Alphabet's self-driving arm, said it would recall 672 driverless vehicles after one of its robotaxis struck a wooden utility pole in an alleyway in Phoenix, Arizona, during a low-speed pullover manoeuvre in May. According to Reuters, no passengers, other road users or injuries were involved.
The recall came with a software update and mapping improvements installed across the fleet, and the US National Highway Traffic Safety Administration has separately been examining 22 reports of Waymo robotaxis behaving unexpectedly, including 17 collisions.
In the same NHTSA pipeline, Ford is recalling 41,748 Expedition and Super Duty vehicles over defective LED headlight chips, GM is recalling Cadillac OPTIQ and Silverado/Sierra models, and Jaguar Land Rover is recalling 1,073 Range Rover Sports over possible rear subframe cracks.
Why a software fix for a pole is surprising
The remedy is what makes this recall unusual: rather than replacing parts, Waymo pushed a software update that changes how the automated driving system responds to poles and pole-like permanent objects.
According to the Associated Press, the update improves that response, and Reuters says the same remedy was part of the recall, with NHTSA stating that before the fix the system could fail to avoid a pole or similar object.
Waymo says "robust mapping updates and improvements" are already installed in all vehicles; the map update adds a "hard road edge" between the pole and the drivable surface.
A recall triggered by a perception blind spot, fixed entirely in software and maps, is a distinctly autonomous-driving kind of problem.
The evidence: a pattern of visible-object collisions
NHTSA opened its investigation in May after 22 reports of Waymo robotaxis behaving in ways that potentially violated traffic safety laws or showed other unexpected behaviour, 17 of them collisions.
Reuters adds that the regulator said several incidents involved collisions with clearly visible objects that a competent driver would be expected to avoid — stationary and semi-stationary objects such as gates and chains, parked vehicles, and cases where the driving system appeared to disobey traffic safety controls.
NHTSA required Waymo to answer detailed questions by 6 August, including whether any vehicles had been grounded and whether tests or updates addressed specific incidents.
This is also Waymo's second recall: an earlier one in February covered 444 vehicles after two minor Arizona collisions tied to a software error predicting towed vehicles.
The stakes for autonomous and conventional cars alike
The recall lands amid a string of NHTSA probes into self-driving performance, following investigations into General Motors' Cruise and Amazon's Zoox, so the regulator's scrutiny of Alphabet's robotaxis signals rising pressure on the whole autonomy sector.
Conventional recalls in the same window show hardware risks remain too: Ford reports six warranty claims and six field reports, and no accidents or injuries, from contaminated LED chips that can cause headlights and other exterior lamps to dim or fail, increasing crash risk.
What owners should do next
Waymo's fleet fix is already deployed, but NHTSA's questions and the ongoing investigation mean the regulator's review of the 22 incident reports remains the item to watch.
Ford says dealers will inspect and replace headlight assemblies free of charge, with owner notification letters expected to be mailed Oct. 26, VINs searchable on nhtsa.gov from that date, and Ford customer service reachable at 1-866-436-7332 under recall number 26C43.
According to Top Class Actions, Ford dealers will be notified between Oct. 26 and 30, and owner letters are expected from Nov. 6 to 13. GM letters are due Nov. 9, and Land Rover interim safety-risk letters Nov. 20.
Owners of affected vehicles can check their VIN in NHTSA's recall database.