Hit by a Driverless Car Charlotte
ATTORNEY REVIEWED. LEGAL ACCURACY VERIFIED
Reviewer: Cameron Bauer, Esq., Associate Attorney
NC Bar: #63306 | Focus: Autonomous Vehicle Accident Law (N.C.G.S. Article 18), Product Liability
Founded: 1991 | Last Reviewed: September 2026 | Reviewed under N.C.G.S. Sections 20-400 through 20-403, Section 20-279.21, Sections 99B-1 through 99B-11, and Section 1-52
Educational content only, not legal advice. Results vary by case.
Hit by a Driverless Car Charlotte: Your Rights When a Robotaxi Struck You
Reviewed by Cameron Bauer, Esq., NC Bar #63306 | Last updated September 2026
Key Takeaways: Struck by a Driverless Vehicle in Charlotte
- This is the hardest posture in North Carolina, and the reason is the evidence. The company holds a synchronized multi-sensor record of the seconds before impact. You have your memory. Contributory negligence needs only one percent, and the company is looking for it in data you cannot see.
- What you gather in the first hours carries disproportionate weight. Independent witnesses, scene photographs, and your own dashcam footage are the only counterweight to a corporate record you will not obtain for months.
- Section 20-401(g) required the vehicle to stop. If it left the scene, that is a statutory violation and it belongs in the crash report. Photograph the departing vehicle and note the fleet number if you can.
- The same record that threatens you can also prove your case. Perception logs can show the system detected you with time to stop and reacted late, or never classified you correctly at all. The company’s own data is frequently the strongest evidence against it.
- Decline recorded statements. A single casual concession about speed, lane position, or what you did or did not see satisfies the contributory negligence bar and ends the claim.
- Free consultation, available 24/7: call Sofia, our AI intake line, at (980) 238-HELP and get signed up in one call. No fee unless we win.
Free Driverless Vehicle Collision Consultation, Available 24/7
Speak with Sofia, our AI intake line. Answers immediately, any hour, and can sign you up on the same call.
No fee unless we win. Translation services available. Office line: (980) 239-2275
Why Being Hit by a Driverless Car Is Different
Someone hit by a driverless car Charlotte drivers share the road with faces an opponent that already has the evidence. The vehicle recorded the collision from every angle, its engineers read those logs daily, and North Carolina lets it defeat your claim by establishing one percent of fault.
Every ordinary collision claim starts with rough evidentiary parity. Two drivers, two accounts, a police report, and whatever physical evidence survives. Both sides work from incomplete information and the case is built from there.
An autonomous vehicle collision starts with nothing like parity. Before you have called anyone, the company holds lidar returns, radar data, camera video covering every direction, the perception system’s classification of your vehicle, the planning system’s decision log, and continuous vehicle state including speed, steering, and braking. Its people know how to read all of it.
Now add North Carolina’s contributory negligence rule. The operator does not have to prove its system was blameless. It has to establish that you bore one percent of the fault, and it will look for that in a dataset that measures your following distance continuously and your reaction time to a fraction of a second. Our partially at fault page explains the doctrine generally, and the contributory negligence and sensor data page develops how it is attacked.
None of this makes a claim unwinnable. It makes the first hours decisive.
What to Do in the First Hours
Ordered by how quickly the opportunity closes. Independent documentation gathered at the scene is the only evidence you will control, and it is the counterweight to a corporate record you will not see for months.
- Call law enforcement and confirm a report is created. Section 20-401(g) requires the vehicle to remain until registration and insurance information is provided and an officer authorizes removal.
- Photograph vehicle positions before anything moves. Final rest positions establish angles and speeds that reconstruction depends on, and they disappear the moment a vehicle is moved.
- Photograph the autonomous vehicle itself. The sensor housings on the roof and fenders, the fleet number, the plate, and the registration card if it is visible. Section 20-401(h)(5) requires a fully autonomous vehicle to be identified as such on its registration.
- Collect independent witnesses. Names and phone numbers. A neutral account of what the vehicle did is the strongest single counterweight to the company’s internal data.
- Preserve your own dashcam footage immediately. Including the minutes before impact. Many systems overwrite on a loop within an hour when no event triggers a save.
- Photograph the roadway. Skid marks, debris fields, signal timing, sight lines, lane markings, and anything obstructing visibility.
- Get medical attention the same day and decline recorded statements. Treatment gaps are used to minimize injuries, and one concession satisfies the contributory negligence bar.
What the Company Will Look For in Its Own Data
The operator does not need to prove its system drove perfectly. It needs one percent of fault from you. Knowing which variables it will examine is the first step in preparing to answer them.
| What the data shows | The argument built from it | What answers it |
|---|---|---|
| Your speed, continuously measured | You were exceeding the limit, even slightly | Posted limits, traffic flow, reconstruction of the full approach |
| Lane position over time | You drifted or failed to maintain your lane | Lane width, markings, road condition, what the vehicle itself was doing |
| Following distance | You were too close to stop safely | Whether the vehicle braked abnormally or stopped without cause |
| Reaction interval | You had time to avoid the collision and did not | Sight line obstruction, perception-reaction time, what was actually visible |
| Signaling | You changed lanes or turned without warning | Signal records from your own vehicle, witness accounts |
Each of these is answerable, and each answer requires evidence gathered early. That is why scene documentation and independent witnesses matter more in these cases than in an ordinary collision, where the opposing driver has no comparable record to draw from.
The Same Record Can Prove Your Case
Perception and planning logs are not one-sided. They can establish that the system detected you with time to stop and reacted late, classified you incorrectly, or executed a maneuver no reasonable driver would have chosen. The company’s own data is frequently the strongest evidence against it.
Autonomous systems record what they perceived and what they decided, with timestamps. That creates categories of proof unavailable in a conventional case:
- Detection timing. If the log shows your vehicle was detected and tracked several seconds before impact, a claim that the collision was unavoidable becomes difficult to sustain.
- Classification failure. If the system misclassified your vehicle or lost track of it, that is a perception defect, and it supports a product liability claim under Chapter 99B alongside operator negligence.
- Planning choice. The decision log shows which maneuver the system selected and which alternatives it evaluated. A choice a competent driver would not have made is visible here in a way it never is with a human defendant.
- Remote assistance. If a human operator was consulted and instructed the vehicle, that shifts the analysis toward direct corporate conduct rather than software behavior.
This is why preservation is urgent rather than merely advisable. The robotaxi data preservation page sets out the demand that secures it.
Collision Patterns That Recur With Autonomous Vehicles
Autonomous systems fail in characteristic ways, and several of those failure modes produce collisions with other motorists. Identifying which pattern matches your crash shapes what the perception and planning logs need to be examined for.
- Unexpected or excessive braking. A system that perceives a hazard that is not there, or misjudges one that is, can brake hard without apparent cause. The driver behind is then blamed for following too closely. The planning log shows what the system believed it was reacting to, which is the entire case.
- Unprotected left turns. Judging a gap in oncoming traffic is among the hardest tasks in autonomous driving. A misjudged gap produces a high-energy collision, and the log records exactly what closing speed the system calculated.
- Merging and lane changes. The system must predict what surrounding vehicles will do. A prediction error during a merge results in a sideswipe or a forced evasive maneuver by the other driver.
- Stopping in an inappropriate place. Vehicles have stopped in travel lanes, in intersections, and in other positions a human driver would avoid, creating an obstruction other motorists must react to.
- Construction zones and unusual road geometry. Temporary lane shifts, hand signals from workers, and markings that conflict with mapped data all present conditions these systems handle inconsistently.
- Emergency vehicles and unusual traffic control. Interactions with police activity, stopped school buses, and emergency scenes have produced documented problems across multiple operators.
Each pattern points the investigation somewhere specific. A phantom braking case turns on the perception log and what the system classified. A left turn case turns on the planning log and the closing speed calculation. Knowing which one applies before discovery begins is what makes the demand precise rather than generic.
Who Pays After a Driverless Vehicle Strikes You
There is no driver to sue, so the claim runs at companies. Section 20-401(e) makes the registered owner responsible for moving violations committed while the automated driving system is engaged, which routes liability to the operator rather than to a person who does not exist.
| Defendant | Theory | Evidence |
|---|---|---|
| Fleet operator | Negligent operation, deployment, and maintenance; owner responsibility under Section 20-401(e) | Deployment criteria, maintenance logs, remote assistance records, prior incidents |
| Manufacturer or software developer | Design defect, manufacturing defect, or failure to warn under Chapter 99B | Perception and planning logs, validation testing, known failure modes |
| Maintenance contractor | Negligent maintenance where a mechanical or sensor failure contributed | Service records, inspection history, calibration logs |
| Another human driver | Ordinary negligence where a third vehicle contributed | Reconstruction, witnesses, the autonomous vehicle’s own sensor record |
North Carolina does not recognize strict liability in product cases, so a Chapter 99B claim must prove negligence in design, manufacture, or warning rather than simply that the system failed. Our Charlotte product liability team develops that track alongside the operator negligence analysis. The Waymo and Tesla robotaxi pages address the two operators testing in Charlotte.
When the Driverless Vehicle Leaves the Scene
Section 20-401(g) imposes a duty to stop and sets four specific conditions. A vehicle that left your collision violated the statute, and documenting that departure changes the posture of the claim.
The statute requires that the vehicle or its operator promptly contact law enforcement, promptly request medical assistance where appropriate, and in a reportable crash remain at the scene until registration and insurance information has been provided to the affected parties and an officer authorizes removal. Those obligations do not disappear because no human was aboard.
If the vehicle left, do three things. Photograph it departing if you safely can, including the plate and any fleet number. Report the departure explicitly to the responding officer so it appears in the crash report rather than in your recollection alone. And note the exact time and location, because fleet dispatch records can identify which vehicle was in that position at that moment.
A statutory violation at the scene is evidence a jury can weigh, and it also creates leverage in preservation. A company whose vehicle failed a clear statutory duty has a weaker position when resisting discovery into what that vehicle recorded.
What Insurance Applies When a Robotaxi Hits You
Section 20-401(h)(4) requires only the ordinary private-motorist minimum. North Carolina sets no elevated insurance floor for autonomous fleets, so identifying every applicable layer falls to your lawyer rather than to a regulator.
The statutory floor under Section 20-279.21, confirmed by the North Carolina Department of Insurance, has been 50,000 dollars per person, 100,000 dollars per accident, and 50,000 dollars in property damage since July 1, 2025, with uninsured and underinsured coverage required at matching limits.
A collision serious enough to involve an attorney frequently exhausts 50,000 dollars during the hospital admission. Our catastrophic injury and traumatic brain injury practices deal with that gap constantly. Commercial fleet policies and excess layers typically sit above the required coverage, and none of it is disclosed voluntarily.
Where the available limits still fall short, the underinsured coverage on your own policy becomes relevant. Our uninsured and underinsured motorist page explains how that layer works and why notice requirements matter.
Vehicle Damage and Diminished Value
Property damage runs on the same liability analysis as the injury claim. Where a robotaxi is at fault, the operator’s property damage coverage applies, and a repaired vehicle with an accident history on its record may support a diminished value claim.
North Carolina’s minimum property damage coverage is 50,000 dollars, which covers most repairs and many total losses. The practical difficulty is timing. Property damage is usually resolved quickly while the injury claim is still developing, and a property settlement signed without care can contain language affecting the larger claim.
Do not sign a release for vehicle damage without reading what it releases. Have the language reviewed before signing, particularly where an operator’s claims department handles both the property and injury sides of the file.
Preserve your vehicle until it has been inspected. Its damage pattern is physical evidence of impact angle and speed, and it is the one piece of physical evidence in these cases that you control. Once it is repaired or salvaged, that evidence is gone.
Deadlines That Apply to Your Claim
Three years for personal injury, two years for wrongful death, and a separate three-year product liability period measured from discovery. These are jurisdictional and no court can extend them.
A personal injury claim carries three years under N.C.G.S. Section 1-52, measured from the date of the collision. Where the crash caused a death, Section 1-53 imposes a two-year period, and that shorter window is the one families miss most often while an estate is being opened. Our Charlotte wrongful death practice manages that sequencing.
A product liability claim against the manufacturer or software developer carries its own three-year period, running from when the claimant discovered, or reasonably should have discovered, both the injury and its cause. In an autonomous vehicle case the causal link is rarely apparent at the scene, because nothing visible reveals whether a perception failure or a planning error produced the maneuver.
The deadline that actually governs is much earlier. Data retention runs on company schedules measured in weeks, so the window for preserving the evidence that proves the claim closes long before any filing deadline is near.
How a Charlotte Driverless Vehicle Collision Lawyer Helps
This claim is won or lost on two things: whether the record is preserved before it cycles, and whether the contributory negligence attack is anticipated rather than answered after it lands.
- Preservation demands within days, identifying the date, location, vehicle, and every category of sensor, perception, planning, and remote assistance data.
- Independent reconstruction, built from scene evidence and witness accounts rather than accepting the company’s summary of its own logs.
- Contributory negligence defense from day one, documenting your speed, position, and sight lines before the operator’s version becomes the only account in the file.
- Federal record retrieval, including standing general order crash reports, defect investigation files, and any NTSB materials on the system.
- Expert retention, reconstruction and autonomous systems specialists who read raw perception and planning logs directly.
- Full coverage identification, locating commercial, excess, and manufacturer layers above the statutory minimum, and your own underinsured coverage where limits fall short.
Charlotte NC Car Accident Lawyers Group has represented injured people in this region since 1991. No fee unless compensation is recovered. Translation services available. See our Charlotte car accident practice or contact us at any hour.
Start your free consultation right now
Sofia is our AI intake line. She answers on the first ring at any hour, takes the details of your collision, and can book your free consultation on the same call. Preservation demands can go out the next business day.
(980) 238-HELP (980) 238-4357
Frequently Asked Questions: Struck by a Driverless Vehicle in Charlotte
A driverless car hit me in Charlotte. What do I do first?
Call law enforcement and make sure a report is created, because Section 20-401(g) requires the vehicle to remain until information is exchanged and an officer authorizes removal. Photograph vehicle positions before anything moves, then the autonomous vehicle itself including its sensor housings, fleet number, and plate. Collect witness names and phone numbers. Preserve your own dashcam footage immediately. Get medical attention the same day, and decline any recorded statement until you have spoken with a lawyer.
Who is liable when a driverless car causes a crash?
Companies, because there is no driver. N.C.G.S. Section 20-401(e) makes the registered owner responsible for moving violations committed while the automated driving system is engaged, which routes the claim to the fleet operator. The manufacturer or software developer may also face product liability under Chapter 99B for a design defect, manufacturing defect, or failure to warn. A maintenance contractor and any other human driver involved can share responsibility depending on the facts.
Why is contributory negligence such a threat in these cases?
Because the company can measure your conduct precisely and needs only one percent of fault. North Carolina bars recovery entirely when an injured person bears any share of responsibility. The vehicle recorded your speed continuously, your lane position over time, your following distance, and the interval between a hazard appearing and your brakes engaging. Proving one percent against an ordinary driver is hard. Proving it against someone with that dataset is considerably easier.
Can the robotaxi data help my case too?
Frequently it is the strongest evidence you have. Perception logs record what the system detected and when, so a log showing it tracked your vehicle several seconds before impact makes an unavoidability defense hard to sustain. A classification failure, where the system misidentified or lost track of your vehicle, supports a product liability claim. The planning log shows which maneuver it chose and which alternatives it evaluated, exposing decisions a competent driver would not have made.
How do I get the company’s crash data?
Through a preservation demand backed by litigation, not by asking. The company holds the data, controls retention, and produces it in formal discovery. A written demand identifying the date, location, vehicle, and each specific data category needs to go out within days. Federal sources run in parallel without the company’s cooperation: crash reports filed under the NHTSA standing general order, defect investigation records, and any NTSB materials on the system are independently obtainable.
What if the driverless vehicle left the scene?
That violates Section 20-401(g) and it belongs in the crash report. The statute requires the vehicle or its operator to promptly contact law enforcement, promptly request medical assistance where appropriate, and in a reportable crash remain until registration and insurance information is provided and an officer authorizes removal. Photograph the departing vehicle if you safely can, note the plate and fleet number, and report the departure explicitly to the responding officer.
Should I give a recorded statement after a robotaxi hit me?
No, not before speaking with a lawyer. In a state where one percent of fault bars recovery entirely, a recorded statement is where that one percent is usually found. Saying you were going about the speed limit, that you did not see the vehicle until late, or that you might have been a little close all sound harmless and all supply the concession the defense needs. You are not required to give one, and declining is not an admission.
How much is my driverless vehicle collision claim worth?
That depends on your injuries, the strength of the liability evidence, and how much coverage is reachable above the statutory minimum. No lawyer can promise a number, and anyone who does should be treated with suspicion. What can be said is that value in these cases turns heavily on whether the sensor and decision record was preserved, because that record is what establishes fault and defeats the contributory negligence attack.
What insurance covers a robotaxi that hit me?
Only the ordinary minimum is required. Section 20-401(h)(4) requires a fully autonomous vehicle to carry a policy meeting N.C.G.S. Section 20-279.21, which since July 1, 2025 has been 50,000 dollars per person, 100,000 dollars per accident, and 50,000 dollars in property damage. North Carolina sets no elevated floor for autonomous fleets. Operators generally carry commercial and excess layers above that, but none of it is disclosed voluntarily and locating it is legal work.
How long do I have to file after a driverless car hit me?
Three years for personal injury under N.C.G.S. Section 1-52, measured from the date of the collision. If the crash caused a death, the wrongful death period under Section 1-53 is two years. A product liability claim against the manufacturer carries its own three-year period measured from discovery of the injury and its cause. The practical deadline is far earlier, because data retention runs on company schedules measured in weeks rather than years.
What happens to my car after a robotaxi collision?
Preserve it until it has been inspected. The damage pattern is physical evidence of impact angle and speed, and it is the one piece of physical evidence in these cases that you control rather than the company. Once the vehicle is repaired or salvaged that evidence is gone. Property damage runs on the same liability analysis as the injury claim, and a repaired vehicle carrying an accident history may support a diminished value claim.
Can I settle the car damage before the injury claim?
Often yes, but read what you are signing. Property damage is usually resolved quickly while the injury claim is still developing, and a property release can contain language affecting the larger claim. This matters more when one claims department at the operator handles both sides of the file. Have the release language reviewed before signing, and do not release the vehicle for repair or salvage until the damage has been documented and inspected.
Do I need a lawyer if the robotaxi admitted fault?
An early statement that a vehicle was not at fault, or was, is a company position rather than a legal determination. Operators issue statements quickly after incidents because they hold the data and can characterize it before anyone else sees it. That position can change once independent reconstruction and formal discovery begin. Treat any early characterization as the opening of a negotiation rather than the end of the fault analysis.
What if another human driver was also involved?
Then you may have claims against both, and the autonomous vehicle’s data becomes valuable in an unexpected way. Its sensor record captures the other driver’s conduct with the same precision it captures yours, which can establish that driver’s fault far more convincingly than witness memory. Expect the operator and the other driver’s insurer to each argue the other bears responsibility, and expect both to look for a share of fault to assign to you.
Will my own insurance cover this?
Possibly, in two ways. Your collision coverage can repair your vehicle while liability is being sorted out, subject to your deductible, which your insurer then seeks to recover. More importantly, if the available liability limits do not cover your losses, the underinsured motorist coverage on your own policy becomes relevant.
