Ford image-processing-module reset recall (rearview camera and driver-assist loss)
Ford recalled about 254,640 SUVs (2022-2025 Lincoln Navigator, 2024-2025 Nautilus, 2025 Aviator and 2025 Ford Explorer) whose rearview camera image and driver-assist features could intermittently drop out; Ford first learned of module-reset reports in March 2025 and approved the recall in March 2026.
The damage was public. The root cause was preventable.
Ford recalled about 254,640 SUVs (2022-2025 Lincoln Navigator, 2024-2025 Nautilus, 2025 Aviator and 2025 Ford Explorer) whose rearview camera image and driver-assist features could intermittently drop out; Ford first learned of module-reset reports in March 2025 and approved the recall in March 2026.
What the software actually got wrong
An unexpected reset of the windshield-mounted image processing module's software could cause the rearview image to fail and disable pre-collision assist, lane-keeping assist and blind-spot monitoring, because that one module feeds both the camera and several ADAS functions.
An unexpected reset of the windshield-mounted image processing module's...
An unexpected reset of the windshield-mounted image processing module's software could cause the rearview image to fail and disable pre-collision assist, lane-keeping assist and blind-spot monitoring, because that one module feeds both the camera and several ADAS functions.
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.
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.