Hyundai Palisade power-seat software recall after child's death (26V160)
Hyundai recalled about 61,000 2026 Palisade and Palisade Hybrid SUVs and halted sales after a two-year-old died in Ohio when a third-row power seat failed to stop; Hyundai logged one fatality and several injuries by the recall decision, and regulators in the US, Canada and South Korea acted.
The damage was public. The root cause was preventable.
Hyundai recalled about 61,000 2026 Palisade and Palisade Hybrid SUVs and halted sales after a two-year-old died in Ohio when a third-row power seat failed to stop; Hyundai logged one fatality and several injuries by the recall decision, and regulators in the US, Canada and South Korea acted.
What the software actually got wrong
NHTSA filings say the second- and third-row power seats may fail to detect contact with a person or object during automatic fold/stow and one-touch tilt-and-slide, and the remedy is a software update to the power seat control logic (delivered over the air, including a press-and-hold requirement for fold switches), pointing to inadequate obstruction-detection logic in the seat controller.
NHTSA filings say the second- and third-row power seats...
NHTSA filings say the second- and third-row power seats may fail to detect contact with a person or object during automatic fold/stow and one-touch tilt-and-slide
Requs AI Edge Case flags this exact pattern at the requirements and architecture stage — before a single line of code implementing it exists — so the assumption behind it gets challenged while it is still cheap to fix.
The remedy is a software update to the power...
the remedy is a software update to the power seat control logic (delivered over the air, including a press-and-hold requirement for fold switches), pointing to inadequate obstruction-detection logic in the seat controller
Requs AI Software FMEA traces this failure mode back to the system-level hazard it feeds, tagging it against the Common Defect Enumeration so it surfaces in review instead of in the field.
Beyond code coverage and "shall" testing
Root causes like this one rarely show up in code coverage or requirements-compliance testing, because nobody wrote a requirement anticipating the specific edge case that broke. Requs AI Edge Case and Requs AI Software FMEA are built to surface exactly this class of overlooked failure mode — before the software is written.
Surfaces this before code exists
Identifies edge cases like this one at requirements and architecture time, using the Common Defect Enumeration to catalog failure patterns seen across hundreds of real-world software failures — including this one.
Connects the failure mode to the hazard
Traces this class of root cause directly to the system-level hazard it can produce, so a defect pattern like this one gets flagged during design review instead of after it ships.
Find the overlooked root causes before they ship.
Schedule a demonstration, or explore how Requs AI Edge Case and Software FMEA use the Common Defect Enumeration.