Legally, yes. Federal law defines a recall by the existence of a safety defect, not by whether anyone touches a wrench.
Practically, it is something new and it creates a problem nobody designed the rules for. An over-the-air update admits a defect and erases it in the same motion.
If that defect hurt you, the thing that hurt you no longer exists.
What the law says
Under federal motor vehicle safety law, a manufacturer that learns a vehicle contains a defect related to motor vehicle safety must notify the agency and remedy it. The remedy can be repair, replacement, or refund.
Nothing in that framework requires the fix to be mechanical. A software update delivered wirelessly is a remedy, and the National Highway Traffic Safety Administration has processed a substantial and growing number of recalls remedied entirely that way.
So a company saying “this was just a software update, not a recall” is making a public relations statement, not a legal one. If it was filed as a defect remedy, it was a recall.
Why over-the-air changes everything
Traditional recalls are visible and slow, and that visibility is useful to an injured person.
| Traditional mechanical recall | Over-the-air software recall | |
|---|---|---|
| Owner action required | Yes, bring the vehicle in | None, often none noticed |
| Speed of deployment | Weeks to months | Hours to days |
| Physical evidence afterward | Old part exists, can be inspected | Prior code version is gone from the vehicle |
| Owner awareness | Notification letter, service appointment | Frequently a changelog entry, or nothing |
| Fleet consistency | Vehicles remediated at different times | Entire fleet can change overnight |
Look at row three. In a conventional defect case the removed part is evidence. You can inspect it, test it, and put it in front of a jury.
When the defect was in code, the version that caused your crash was overwritten. What remains on the vehicle is the fixed version, which will perform correctly in every test the defense runs.
The evidence problem, stated plainly
To prove a software defect caused your injury, you need the software that was running at the moment of impact. Not the current version. The one from that day.
That means:
- The exact build and version identifier active on that specific vehicle at that moment
- The code itself, which is proprietary and will be fought over
- Internal defect tracking, engineering tickets, and validation records showing what the company knew and when
- The agency defect filing and the chronology in it
- Deployment records showing when the update reached that vehicle
None of that is in your possession. All of it is in theirs, and retention follows their internal policy.
This is why a preservation demand in a case like this has to be written by someone who knows the specific artifacts to name. A generic letter asking a company to preserve “all relevant evidence” will not produce a version-pinned build.
Does the update help your case or hurt it?
Both, and the tension is real.
It helps. A defect filing is the manufacturer’s own written statement that a safety defect existed, usually with a description of the defective behavior and a chronology of when the company learned of it. That is a document you would otherwise spend a year of discovery trying to obtain. If the described behavior matches what happened to you, the connection is powerful.
It complicates things. Manufacturers argue that prompt remediation shows a responsible safety culture rather than fault. Courts also apply rules limiting the use of subsequent remedial measures to prove negligence, though those rules generally have exceptions for proving the feasibility of a safer alternative design, which is often exactly the point in a design defect case.
And there is a timing argument the defense will always make. If the update arrived before your crash and your vehicle had not yet installed it, they will say the remedy was available and the failure was in the deployment chain or the owner’s connectivity. If it arrived after, they will say the defect was not reasonably discoverable earlier.
The questions with no settled answer
Does an over-the-air update trigger a duty to warn the owner directly? Notification obligations were written around mailed letters and service visits. A silent background update reaching a vehicle whose owner never learns a safety defect existed sits uneasily with the purpose of the notice requirement.
Is a company obligated to preserve the prior version? No regulation clearly requires retaining superseded builds for the benefit of future injury claims. Spoliation doctrine may reach it once litigation is reasonably anticipated. Before that, unclear.
What happens when the update introduces a new defect? An update fixes behavior A and changes behavior B in a way nobody validated. Whose defect is the resulting crash?
Can a fleet operator be liable for delaying an available update? For a commercial robotaxi fleet, deployment timing is an operational decision. That looks much more like ordinary negligence than product liability, and it is a theory that reaches a different defendant with different insurance. It overlaps closely with who you sue after a robotaxi crash.
What this means for you
If a vehicle with automated driving features was involved in your crash, three things belong on the list immediately.
Identify the exact vehicle and record its software state. Fleet number, VIN, plate. If it is a consumer vehicle, the software version is often visible in the vehicle’s own settings menu. Photograph that screen.
Check the recall record. NHTSA’s database is public and searchable by VIN. Do it now and save what you find, including the filing date and the defect description.
Get preservation demands out in days. This is the whole case. Once the fleet updates, the artifact that would prove your claim is gone from the vehicle and survives only in the company’s internal systems, if it survives at all.
Robert Law Group is building a practice in emerging technology torts, and this is the center of it: harms where the evidence is proprietary, perishable, and controlled entirely by the defendant. That is not a new problem for us. It is the structure of every product liability claim against a corporate manufacturer, and it is what two decades of complex product and pharmaceutical litigation prepares you to handle. It applies just as directly to conventional Houston car accident claims where a vehicle system is in question.
If a vehicle’s software was involved in your injury, call 832-509-2303.
Future Lawsuits. The law before the law catches up.