← The Crash Report
The Gap

Polestar Patched Its Backup Camera Twice. On September 1, NHTSA Finally Believed the Third Fix.

Rear backup camera view of a Polestar 2 showing a frozen and flickering reverse display

Let's talk about what happens in the first 150 milliseconds after you shift into reverse. On a Polestar 2, for the better part of two years, that answer was: sometimes nothing. Blank screen. Frozen frame. A flicker, then gone. Owners reported it 275 times, in cars that had already been through not one but two federal recalls for the same defect. On September 1, 2026, NHTSA finally closed the file.[1][5] Here is the part that should bother anyone who designs safety systems: the camera was never broken. Through three recalls and 21 months, the lens and the sensor worked exactly as designed. What kept failing was the software deciding whether to trust the feed and display it in the two seconds you have before backing over something you cannot see.

275 → 3
owner complaints before and after the third fix, over 27,816 Polestar 2 vehicles

Count the attempts, because the engineering story changes each time. In June 2024, Polestar recalled model years 2021-2024 for a memory allocation error in the infotainment head unit and patched it over the air, freeing graphics memory by killing the map display during backing events.[1] In April 2025, it recalled 2021-2025 cars again, this time for a synchronization fault between the parking assist camera and that same head unit, and pushed a second patch.[2] Complaints kept arriving. NHTSA's Office of Defects Investigation opened Recall Query RQ25004 in July 2025, and two months later Polestar filed a third recall, admitting in its own paperwork that the second remedy had failed and more engineering analysis was needed before it could try again.[3] That third campaign, 25V-615, replaced both earlier recalls outright. Cars already "repaired" had to be repaired again.

Now the part nobody outside the agency talks about: a recall query is not a defect investigation. It is an audit of the remedy. NHTSA opened RQ25004 to investigate allegations that the fix for 25V-280 did not fix anything, sent a formal information request, held a technical briefing, and monitored complaint volumes for the better part of a year before declaring the third software update, released April 2026, good enough.[2][5] This is a tool that exists because the industry kept proving that a recall and a repair are not automatically the same thing. Polestar just made the case study unusually legible: three attempts, and the only way to know the third one worked was to wait and count.

This is where the safety engineering gets genuinely uncomfortable. A backup camera is not an infotainment feature. It is federally mandated equipment under FMVSS 111, required industry-wide since May 2018 under the Cameron Gulbransen Kids Transportation Safety Act, a law named for a toddler killed when his own father backed over him in a driveway.[5] A brake light is a wire and a bulb: you replace the part and you can see it work. A backup camera is a decision, made in code, about whether to show a moving image fast enough to matter. When Polestar's screen went dark, that was the same category of mandated protection as a brake light, delivered through software that took the manufacturer three tries and the regulator fourteen months to validate. And it is worth being precise about scale: the post-fix complaint rate of 0.01% backs into a fleet of about 30,000 cars. A defect that would be statistical noise at Ford can trigger a year-long federal review at a niche brand. Small footprint, same law, no discount on verification.

What to do: Own a 2021-2025 Polestar 2? Run your VIN at nhtsa.gov/recalls and check for campaign 25V-615, Polestar's RP1069.[4] If you had the earlier camera recalls done, you need this one anyway: the third campaign explicitly replaces them. More broadly, treat any software-remedy recall as provisional until you confirm no superseding campaign exists. A patch on your update history is a claim, not proof. And when the camera goes dark, do not back up on a frozen screen: FMVSS 111 exists because driveway backovers are fatal, and two seconds of blind reversing is exactly the scenario the law was written for.

What this does not prove: The ODI resume logged zero crashes, zero fires, and zero injuries across the complaint population at query opening, so this is a verification saga, not a body count.[1] The 0.01% post-fix rate and the implied fleet size are our arithmetic on NHTSA's numbers, not the agency's claim. And closure is not exoneration: NHTSA's closing language reserves the right to take additional action if new complaints appear. Count them anyway.

Sources & References

  1. NHTSA Office of Defects Investigation, ODI Resume: RQ25004 — Loss of rearview camera image, opened July 9, 2025 (population 27,816; 109 complaints at open; Recalls 24V-477 and 25V-280). static.nhtsa.gov
  2. NHTSA ODI, Information Request RQ25004-01, July 18, 2025 (193 reports of blank, flickering, frozen rearview images after Recall 25V-280 remedy). static.nhtsa.gov
  3. NHTSA, Recall Acknowledgement 25V615, September 19, 2025 (27,816 units, MY 2021-2025; replaces 24V477 and 25V280; previously repaired vehicles must be remedied again). static.nhtsa.gov
  4. Preetika Parashuraman, “EV maker Polestar recalls over 27,000 US vehicles due to rearview camera issue, NHTSA says,” Reuters, September 20, 2025. reuters.com
  5. Shawn Henry, “Polestar’s Backup Camera Recall Took 3 Tries. Here’s Why,” The Autowire, September 2, 2026 (RQ25004 closed September 1, 2026; 275 complaints fell to 3 after April 2026 update). theautowire.com
  6. NHTSA, Recalls Database — VIN lookup. nhtsa.gov

Source: NHTSA ODI documents for Recall Query RQ25004 (INOA-RQ25004-15762, INIM-RQ25004-15916), Recall 25V-615 acknowledgement (RCAK-25V615-7299), and secondary reporting September 2025 and September 2026; complaint-rate arithmetic is ours; see methodology for caveats.