Virginia · Maryland · Washington, D.C.
The car was driving.
Who answers for your injuries?
A Waymo, Tesla, or other automated vehicle was involved. You are hurt, and everyone may have a different explanation. I help you examine what happened, identify the potentially responsible parties, and build a claim around the evidence.
You do not need to understand the technology before you call.
Hero artwork and scenario graphics are illustrative. They do not depict firm case results or establish local service availability.
The short answer
A human driver, an automated-vehicle operator, a manufacturer, or another party may be responsible, depending on what caused the crash. The investigation must identify the actual system and mode in use, the duties or alleged defects involved, and their connection to your injuries. No company becomes liable simply because its name is on the car. More than one cause and more than one defendant may be involved.
Driver assistance and driverless operation create different questions.
Video, vehicle records, and trip information can be time sensitive.
Location, claim type, and your role in the crash all matter.
01 / Start with the crash
After a collision, the questions are painfully practical. How will you pay for treatment? What happens if you cannot work? Who should receive the claim when an insurance adjuster says the driver blames the car and the company blames the driver?
I start by separating those questions. First, what happened on the road? Second, who had responsibility for the relevant decisions? Third, what evidence connects a wrongful act or a defective product to your injuries?
The software may matter a great deal. So may a red light, an unsafe turn, or a driver looking away. I want the technical record and the physical evidence to explain the same seconds.
Tell Us What Happened02 / Know what was actually driving
A Tesla with supervised driver assistance, a robotaxi, and a test vehicle with a safety operator should not be treated as the same fact pattern.
When an automated driving system performs the driving task within its approved operating conditions, passengers may have no driving role. A vehicle being mapped or tested with a human operator presents a different question.
I identify the entity operating the vehicle, whether the system was engaged, the applicable permissions, and any human or remote involvement in the trip.
Tesla states that Full Self-Driving (Supervised) requires active driver supervision and does not make the vehicle autonomous. A driver cannot assume that a supervised feature has taken over their responsibilities.
Cybercab and a Robotaxi service operation require their own investigation. The vehicle’s branding does not prove which system was active or who controlled a particular maneuver.
The feature may control steering and speed while the driver supervises. Driver conduct, warnings, feature limits, and any alleged product defect require review.
The system drives under defined conditions, with the driver available to take over when requested. The request, timing, and response need analysis; liability does not simply switch at a notification.
Within its operating domain, the system performs the driving task without a passenger taking over. Operator conduct, system performance, and deployment conditions may matter.
Technology references: NHTSA automation levels (opens in a new tab); Tesla Full Self-Driving (Supervised) (opens in a new tab). Automation levels describe technical capabilities, not automatic legal outcomes.
03 / Follow the evidence to the right parties
I look at each party’s actual role. Naming a well-known company is not a substitute for identifying a supported legal claim.
Attention, speed, supervision, steering or braking inputs, and the response to warnings may be relevant.
The entity controlling the service, test program, deployment, maintenance, or operating conditions may require investigation.
The vehicle manufacturer, system developer, or component supplier may be relevant if an actionable defect caused harm.
Another road user, a repair provider, or another entity may have contributed. The crash may have several causes.
Under D.C. Code § 50-2352.01(e), the associated AV testing entity is treated as the operator while the vehicle is under autonomous operation. The statute also addresses testing permits and conditions. I would examine whether that framework applies to the actual vehicle and trip, then assess the evidence of fault and causation.
D.C. Autonomous Vehicle Testing Program (opens in a new tab). Operator status does not by itself prove that the entity caused an injury.
04 / Four illustrated scenarios
These hypothetical examples show the questions an investigation may need to answer. They are not actual cases, case results, or liability determinations.
An automated vehicle crosses an intersection and strikes another vehicle. The accounts of the signal phase conflict.
A supervised driving feature is engaged. The driver fails to react, and the vehicle enters a hazardous situation.
A vehicle brakes sharply and the vehicle behind it strikes it. One driver describes the stop as “phantom braking.”
A pedestrian or cyclist is struck during a turning movement. The parties disagree about the signal and who entered first.
What if the vehicle had a green light?
A green signal is important, but turning duties, pedestrians, vehicles already in the intersection, speed, and the sequence of events can still matter. I review the entire movement, not one fact in isolation.
Examples are simplified. Relevant references include Virginia traffic-signal law (opens in a new tab) and D.C.’s vulnerable-user protection (opens in a new tab).
05 / Human error and system behavior
A manufacturer may point to a distracted driver. A driver may point to the vehicle. I would test both explanations against the same timeline.
A human mistake can be a cause without necessarily being the only cause. Equally, the presence of automation does not establish that the system was defective. The case needs evidence showing what each alleged act or defect contributed.
Attention, speed, inputs, and response to warnings.
Detection, braking, steering, design, and warnings.
Your conduct may be central to a negligence defense. A warranty or strict-liability theory, where available, has different elements and defenses. I would evaluate those theories separately rather than assume that one allegation defeats everything or that relabeling the claim solves the problem.
References: Virginia civil jury instructions, causation (opens in a new tab); Evans v. NACCO (opens in a new tab); Ellsworth v. Sherne Lingerie (opens in a new tab); East Penn Manufacturing v. Pineda (opens in a new tab).
06 / Test the explanation
These are potential arguments, not statements that every manufacturer will make. My response is to identify what evidence would support or undermine them.
“The driver was supposed to supervise.”
That duty matters. So do the warnings, the opportunity to respond, the feature’s limitations, and any independently supported defect. I would examine the interaction instead of treating a warning as the end of the case.
“The system operated as designed.”
A system operating as intended can still face a supported design claim, but functioning as designed does not itself prove a defect. The legal standard and appropriate technical evidence remain essential.
“Our fleet is safer than human drivers.”
A fleet statistic does not decide what happened to you. I would examine the data’s scope and the evidence of this particular maneuver, vehicle, system version, and injury.
“You caused your own injuries.”
The allegation must be tested against the applicable law and facts. Your role, the claim type, and D.C.’s vulnerable-user statute may change the analysis.
“There was no relevant system problem.”
Records of defects or recalls may help identify questions. Their relevance depends on the vehicle and software involved, the condition addressed, and whether that issue contributed to this crash.
“This amount should close the claim.”
A quick settlement can arrive before the medical picture is clear. I would evaluate the supported losses, available coverage, repayment issues, and the rights being released before advising on an offer.
07 / Virginia, Maryland & Washington, D.C.
General rules are a starting point. The crash location, parties, claim type, and applicable choice-of-law rules still need individual review.
| Issue | Virginia | Maryland | Washington, D.C. |
|---|---|---|---|
| General personal injury filing period | 2 yearsGenerally from accrual. § 8.01-243 (opens in a new tab). | 3 yearsGenerally from accrual. § 5-101 (opens in a new tab). | 3 yearsGenerally under the catchall limitation period. § 12-301(8) (opens in a new tab). |
| Your own negligence | Negligence that proximately contributes to the injury can bar an ordinary negligence claim. Exceptions require review. | Contributory negligence can bar an ordinary negligence claim. The rule is addressed in Coleman (opens in a new tab). | Contributory negligence may bar an ordinary negligence claim, subject to exceptions including the vulnerable-user statute below. |
| Product theories | Negligence and warranty theories may apply. Virginia has not adopted strict products liability. Evans (opens in a new tab). | Strict products liability may be available. Ordinary contributory negligence is not its defense, but misuse and assumption of risk can matter. Ellsworth (opens in a new tab). | Strict products liability may be available, with defenses distinct from ordinary negligence. East Penn (opens in a new tab). |
| A rule that needs special attention | The elements and defenses of each negligence or warranty theory must be established separately. | A statutory noneconomic-damages limit may apply; the injury date and claim affect the calculation. § 11-108 (opens in a new tab). | Qualifying pedestrians and vulnerable users receive protection under § 50-2204.52 (opens in a new tab). Optional PIP elections can also restrict suit rights. |
This table does not list every exception, tolling rule, notice requirement, or defense. Wrongful-death and survival claims require a separate deadline analysis. An insurance claim is not a filed lawsuit.
08 / Preserve what can explain the crash
An automated vehicle can generate useful information, but there is no guarantee that it recorded every event or retained every sensor stream. Some material may be stored in the vehicle, some with a company, and some with independent witnesses.
I would identify the likely custodians and seek preservation of relevant material. Obtaining it may require cooperation, technical work, formal discovery, or a court order. A preservation request is an important step, not a promise that the data exists or will be recovered.
Dashcam footage, nearby cameras, original photos, damage patterns, road markings, signal information, and witness observations.
Available event data, speed and braking information, feature engagement, warnings, interventions, software version, and diagnostic records.
App receipts, pickup and drop-off details, vehicle identifiers, support messages, dispatch records, and any relevant remote-assistance records.
Medical records, treatment costs, work restrictions, missed income, continuing limitations, and the effect on your daily life.
A relevant crash report, investigation, or recall can point to evidence worth examining. It is not an automatic finding that a company caused your injuries. NHTSA identifies limitations in its crash-reporting data, and the absence of a public report does not establish that no crash or defect occurred.
I would match any relevant issue to the specific vehicle, software, conditions, and alleged failure. A recall covering another version is not a substitute for that work.
NHTSA Standing General Order on Crash Reporting (opens in a new tab).
09 / After an automated-vehicle crash
Protect your health first. Then preserve the information you already have and get advice about the next steps.
Call 911 in an emergency, seek appropriate medical evaluation, and report the collision as required. Do not put yourself in traffic to collect evidence.
If safe, save the plate, vehicle number, make, model, company, report number, and witness contacts. If you were a rider, retain the trip receipt and app messages.
Save original photos, video, messages, and records. Do not reset, alter, or discard potential evidence. Ask about preservation before vehicle repair or disposal.
Get advice before a release, benefit election, or statement to the other side. Be truthful and do not guess. Follow applicable duties to notify and cooperate with your own insurer.
Do not wait until you have every document.
A date, location, short account, and the vehicle information you know are enough to begin discussing a consultation.
10 / Your losses, supported by evidence
A technology headline is not a valuation method. I focus on your medical picture, financial losses, daily limitations, and the recovery available under the applicable law.
Medical expenses and supported future care, rehabilitation, or assistance needs.
Missed pay, work restrictions, and a supported impact on future earning capacity.
The injury’s physical and emotional consequences, including supported continuing limitations.
Wrongful-death and survival claims involve their own questions about who may bring the case, which losses may be recovered, and when the action must be filed. A family should receive advice specific to those issues.
For every claim, coverage, statutory limits, expenses, and repayment obligations may affect the practical recovery. Punitive damages require a separate legal showing. A verdict from another state is not a prediction of your result.
11 / Service availability and legal authority
I would verify what the vehicle was authorized to do in the place and on the date of the crash. A rollout announcement, an app listing, or the absence of a driver is not enough to answer that question.
As checked September 29, 2026, Waymo’s updates page places Washington, D.C. and Baltimore in its “Up Next” list rather than its list of cities serving riders. That company listing is not a legal determination about every operator or every form of testing.
Check the actual entity, jurisdiction, permit or other authority, operating mode, and approved conditions. D.C.’s testing statute includes in-vehicle and remote-operator provisions, with conditions for operation without a physically present test operator.
Availability and regulatory permissions change. Proposed legislation is not the same as enacted law, and permission to operate does not resolve civil liability for a crash.
12 / How we help
I want you to understand the disputed issues, the evidence we need, and the decisions ahead.
Discuss your role in the crash, your injuries, immediate requests, and the consultation process.
If retained, identify the relevant parties, records, deadlines, coverage, and technical questions.
Use the evidence and, where appropriate, qualified experts to connect conduct, system behavior, and injuries.
Evaluate offers with you and pursue the appropriate legal process when a supported dispute requires it.
A note from Anthony
The name on the vehicle matters less than the facts we can establish. I want to know what it did, what the people involved did, and how the crash changed your life. Then I can evaluate the legal path supported by that record.
Anthony I. Shin, Esq.
Principal, Shin Law Office
Serving injury clients in Virginia, Maryland, and Washington, D.C., from offices in Leesburg and Fairfax. Tell us where the collision occurred so we can discuss jurisdiction and next steps.
13 / Answers before you call
Clear starting points for Waymo, Tesla, Cybercab, and Autopilot injury questions.
Tell Shin Law Office what vehicle was involved, where the crash happened, and how you were hurt. We can discuss the issues, the consultation process, and what may need attention next.
Contacting the firm does not by itself create an attorney-client relationship.
Attorney advertising and general information, not legal advice. Outcomes depend on the facts, applicable law, and evidence; no result is guaranteed. Technical features, service availability, and legal requirements can change. Hypothetical scenarios do not describe Shin Law Office case results. Consultation and fee terms should be confirmed with the firm.
Reproduction of any content on this site is prohibited except for individual, non-commercial, informational use. This limited permission does not allow modification, distribution, or incorporation of any content into other works or publications in any medium. You may not reproduce or distribute content from this site to any third party.
Copyright © 2026 Shin Law Office, PLC. All rights reserved.
Powered by HILARTECH, LLC
Copyright © 2026 Shin Law Office, PLC. All rights reserved.
Reproduction of any content on this site is prohibited except for individual, non-commercial, informational use. This limited permission does not allow modification, distribution, or incorporation of any content into other works or publications in any medium. You may not reproduce or distribute content from this site to any third party.