Who May Be Responsible in a Self-Driving Car Accident in Virginia?
Self-driving cars are no longer something you only see in movies or read about in tech news. They are on Virginia roads right now. And when one of them causes a crash, the question of who is responsible is not as simple as it used to be.
In a regular car accident, you look at what the driver did wrong. In a crash involving a self-driving or semi-autonomous vehicle, the answer can point in several different directions at once. It might be the person behind the wheel. It might be the company that built the car. It might be the team that wrote the software. In some cases, it is more than one of them.
If you were hurt in a crash involving a self-driving vehicle in Virginia, here is what you need to understand.
It Depends on How Much the Car Was Driving Itself
Not all self-driving technology works the same way, and that difference matters when it comes to figuring out who is responsible for a crash.
Vehicles are ranked on a scale from Level 0 to Level 5 based on how much the car can do on its own.
At Levels 0 through 2, the human driver is still fully in charge. The car might help with things like staying in a lane or adjusting speed, but the driver is expected to be watching the road and ready to take over at any moment. If something goes wrong, the person behind the wheel is usually considered responsible.
At Level 3, the car can handle driving under specific conditions, like steady highway traffic, but the driver still needs to be ready to take over when the system asks. Responsibility in a Level 3 crash can fall on the driver, the manufacturer, or both, depending on what actually caused the accident.
At Levels 4 and 5, the vehicle is designed to handle driving completely on its own in certain or all conditions. When a crash happens at this level, the focus shifts heavily toward the manufacturer and the technology itself.
Most vehicles on Virginia roads today fall somewhere between Levels 1 and 3. But understanding where a vehicle falls on that scale is one of the first things that needs to be established after a crash.
Who Could Be Responsible
The driver behind the wheel
Even when a vehicle's self-driving features are active, Virginia law still considers the person in the driver's seat to be responsible for the vehicle. That means if a driver stopped paying attention, ignored a warning from the system, or used the technology in conditions it was not designed for, they may bear responsibility for what happened.
The vehicle manufacturer
If the crash happened because of a problem with the vehicle itself, whether it was a sensor that did not work properly, a camera that failed in certain lighting, or a braking system that did not respond the way it was supposed to, the manufacturer may be responsible.
This is different from a regular car accident. Instead of asking what the driver did wrong, you are asking whether the product was safe. If the technology had a known flaw that was not addressed, or if the system was not designed to handle the conditions it encountered, the company that built it may be the one that owes you compensation.
The software developer
In some cases, the hardware is fine, but the software is the problem. If the system made a bad decision based on faulty code, misread the road, or failed to respond correctly to a situation it should have been able to handle, the company that developed the software may share responsibility.
A maintenance provider or third party
If the vehicle was not properly maintained, if sensor updates were not installed, or if mapping data was out of date and contributed to the crash, whoever was responsible for that maintenance may also play a role.
A commercial fleet operator
If the vehicle was part of a rideshare service or commercial operation, the company running that fleet has its own responsibilities. If they deployed vehicles in unsafe conditions or failed to properly maintain their technology, they may be held responsible for what happened.
Virginia's Strict Fault Rule Makes This Even More Important to Get Right
Virginia follows a rule that most other states have moved away from. If you are found even slightly responsible for a crash, even 1%, you may not be able to recover any compensation at all.
In self-driving car cases, this matters a great deal. The manufacturer's legal team or the other party may try to argue that you contributed to the crash in some way, no matter how small. Establishing exactly what caused the accident and who was responsible for it is not just helpful in these cases. It is essential.
Maryland and Washington D.C. follow the same strict rule, so this applies across the entire DMV.
The Evidence in These Cases Is Technical and Time-Sensitive
Self-driving vehicles generate a significant amount of data. They record speed, steering, braking, what the cameras and sensors detected, and what decisions the system made in the moments before a crash. That information is often the clearest picture of what actually happened.
The challenge is that this data does not stay available indefinitely. Manufacturers and fleet operators have their own teams that move quickly after a crash. A formal written request to preserve all vehicle data, software logs, and camera footage needs to happen as soon as possible. If it does not, the information needed to understand what caused the crash can be gone before anyone has a chance to look at it.
What to Do After a Crash Involving a Self-Driving Vehicle
Call 911 and stay at the scene. Make sure a police report is created. If the vehicle appeared to be operating on its own at the time of the crash, mention that to the responding officer and make sure it is included in the report.
Take photographs immediately. The vehicles, the scene, any visible sensors or cameras on the exterior of the self-driving vehicle, company logos, and the license plate. If you can safely see into the vehicle, note whether anyone was in the driver's seat.
Do not touch or attempt to access the vehicle's technology. The data inside the vehicle is evidence. Leave it alone.
Write down everything you remember while it is still fresh. What the vehicle was doing before the crash, how it was moving, and anything unusual you noticed about its behavior.
See a doctor the same day. Pain does not always appear right away after a crash. A same-day medical record is one of the most important things you can have.
Speak with a personal injury attorney before giving any statement to an insurance company. Crashes involving self-driving technology can involve large manufacturers and their legal teams. Having someone in your corner before you say anything protects you.
In Virginia, you generally have two years from the date of the crash to move forward with a case. But the most important evidence in these cases can disappear much sooner than that.
Virginia Is Still Writing the Rules
Virginia introduced Senate Bill 670 in 2026 to create a formal licensing system for fully autonomous commercial vehicles. The bill passed the Virginia Senate 35 to 4 but did not make it through the full legislative session. Senator Saddam Salim, the bill's sponsor, announced it would be carried over to 2027 to allow more time to work through questions around safety, privacy, and employment impacts. A state work group continues to study how these vehicles should be regulated. As of mid-2026, Virginia has no specific law governing the testing, permitting, or deployment of autonomous vehicles.
That means the law is still catching up to the technology. But that does not mean people who are hurt by self-driving vehicles are without options. It means these cases require someone who understands both where the law currently stands and where it is heading.
At Valor Injury Law, we help people across Virginia, Maryland, and Washington D.C. who have been hurt in crashes involving self-driving and semi-autonomous vehicles. These cases are more complex than standard car accidents, and we know how to investigate them thoroughly, find the right experts, and build a case that delivers our clients the strongest possible outcome.
Call us at (703) 828-0051 for a free, confidential conversation.