What Is a Robotaxi, and Which Ones Operate in Charlotte?

A robotaxi is a vehicle that drives itself with no human responsible for the driving task. North Carolina calls it a fully autonomous vehicle and authorized it in 2017. Two operators, Waymo and Tesla, are already on Charlotte streets in testing, and neither carries paying public passengers here yet.

The legal definition matters more than the marketing. Under N.C.G.S. Section 20-400, a fully autonomous vehicle is one whose automated driving system performs the entire dynamic driving task without expecting any occupant to respond to a request to intervene, and in which any equipment permitting a person to drive is stowed or rendered unusable. That language captures a purpose-built vehicle with no steering wheel precisely. The engineering community describes the same threshold as SAE Level 4 or 5 under SAE International standard J3016.

Charlotte reached this point quickly. Waymo named Charlotte as a destination in February 2026, with the Governor and the Mayor both appearing in the announcement. By mid-July the company had completed street mapping and advanced to driving autonomously with a trained employee aboard. In late July, Tesla staged Cybercabs and Model Y vehicles at a Charlotte-area site and posted openings for local test operators. On the first day of Waymo operations here, one of its vehicles was involved in a minor collision uptown with a trainer aboard, which the company said was not its vehicle’s fault. That is the first documented autonomous vehicle crash in this city.

Two other names matter for context. Zoox, owned by Amazon, operates purpose-built vehicles with no steering wheel in Las Vegas and the San Francisco Bay Area but has no announced North Carolina presence. Cruise, once General Motors’ robotaxi arm, had its California driverless permit suspended in 2023 and was wound down as a robotaxi operator, which is a reminder that state regulators elsewhere hold authority North Carolina never created. For scale, Waymo alone reported roughly 400,000 paid rides per week across ten United States cities in 2026, so the volume arriving in Charlotte is not experimental.

What follows on this page is the law that will govern the next one. If your collision involved a Tesla operating on Autopilot or Full Self-Driving with a licensed driver in the seat, that is a different legal framework, and our Tesla Autopilot and FSD accident page addresses it. The dividing line is whether a human remained legally responsible for the vehicle.

Are Robotaxis Legal in North Carolina?

Yes. Session Law 2017-166 authorized fully autonomous vehicles statewide, codified at N.C.G.S. Sections 20-400 through 20-403. The statute requires no driver license for the operator, and it strips Charlotte of any power to regulate these vehicles locally.

North Carolina acted early. House Bill 469, enacted as Session Law 2017-166, created Article 18 of Chapter 20 and made this state one of the first to authorize driverless operation by statute rather than by executive order or agency rule. The operative provisions sit in Section 20-401:

• No license required. Subsection (a) removes the driver license requirement for the operator when the automated driving system is engaged. The statute defines operator to exclude an occupant who merely selects a destination.
• Operating conditions. Subsection (h) requires that the vehicle be capable of achieving a minimal risk condition if the system fails, that it be covered by a liability policy, and that it be registered and identified on the registration card as a fully autonomous vehicle.
• Owner responsibility. Subsection (e) makes the registered owner responsible for moving violations committed while the system is engaged.
• Local preemption. Subsection (i) bars local regulation. Charlotte cannot cap fleet size, require a city permit, or restrict operating areas.

Preemption is worth pausing on. Residents who assume the City Council can respond to a local safety problem are mistaken. Any change has to come from the General Assembly or from federal regulators. Section 20-402 separately addresses partial automation, where a system may issue a request to intervene and a human must respond, and Section 20-403 creates a Fully Autonomous Vehicle Committee within NCDOT that meets at least quarterly and makes recommendations.

Who Is Liable When a Robotaxi Causes a Crash?

With no driver to sue, liability moves to companies. Four categories of defendant typically appear, and Section 20-401(e) gives an injured person a statutory route to the registered owner rather than a search for a driver who does not exist.

Every ordinary car accident claim in North Carolina begins with a person. A robotaxi claim begins with a corporate structure, and the parties inside it have every incentive to point at one another.

The product liability track deserves particular attention. North Carolina does not recognize strict liability in product cases, so a claim under Chapter 99B must be built on proof of negligence in design, manufacture, or warning rather than on the bare fact that the system failed. That raises the evidentiary burden and makes the company’s internal validation records central. Our Charlotte product liability team works these claims alongside the motor vehicle analysis.

Spoke pages address the two largest operators directly: Waymo accident claims in Charlotte and Tesla robotaxi and Cybercab claims.

What North Carolina’s Autonomous Vehicle Statute Does Not Require

Article 18 is a permission framework, not a protection framework. It authorizes driverless operation and then omits four safeguards that other states attached to the same authorization: an elevated insurance floor, autonomous-specific crash reporting, a manufacturer liability provision, and any passenger-carrier permitting regime.

This is the single most important thing an injured person in Charlotte should understand, and it is the reason this page exists. Compare North Carolina to Nevada, which authorized the same technology and built a regulatory structure around it.

Read together, the practical effect is this. A multi-billion-dollar autonomous fleet can satisfy North Carolina’s statutory insurance requirement with the same coverage the statute demands of a private motorist driving to work. No state agency issues a robotaxi an operating authority that could be conditioned or revoked. No autonomous-specific crash report reaches the DMV. A passenger in a Charlotte robotaxi is relying on the operator’s voluntary commercial coverage and on the federal reporting obligations administered by NHTSA, not on anything Article 18 requires.

None of that makes a claim unwinnable. It means the claim has to be built rather than assumed, and that the work of identifying every responsible party and every applicable layer of coverage falls to the injured person’s lawyer rather than to a regulator.

What Insurance Actually Covers a Charlotte Robotaxi Crash

Section 20-401(h)(4) points only to the ordinary minimum at N.C.G.S. Section 20-279.21. Since July 1, 2025 that floor has been 50,000 dollars per person, 100,000 dollars per accident, and 50,000 dollars in property damage, with uninsured and underinsured coverage required at matching limits.

North Carolina raised its minimum limits effective for policies issued or renewed on or after July 1, 2025. The current floor under Section 20-279.21, confirmed by the North Carolina Department of Insurance, is 50,000 dollars for bodily injury to one person, 100,000 dollars for bodily injury per accident, and 50,000 dollars for property damage. Uninsured and underinsured motorist coverage must now be offered at limits matching the liability coverage.

Three consequences follow for a robotaxi claim:

• The statutory floor is low relative to the injuries these cases produce. A serious brain or spinal injury exhausts 50,000 dollars during the hospital stay. Our catastrophic injury practice and traumatic brain injury practice deal with the gap between statutory minimums and actual lifetime cost constantly.
• Operators generally carry far more, but you have to find it. Commercial fleet policies, excess layers, and manufacturer coverage often sit above the required policy. None of it is disclosed voluntarily.
• Your own underinsured coverage may matter. Where the available liability limits do not cover the loss, the UIM coverage on your own policy becomes relevant. Our uninsured and underinsured motorist page explains how that layer works in North Carolina.

Contributory Negligence: Why the Same Rule Helps Passengers and Hurts Drivers

North Carolina bars recovery entirely when an injured person bears any share of fault. In robotaxi cases that rule produces opposite outcomes depending on where you were sitting, and the asymmetry is sharper here than in any other kind of collision.

North Carolina is one of a small handful of jurisdictions still applying pure contributory negligence. One percent of fault defeats the claim completely. Our general explainer on whether you can sue when partially at fault covers the doctrine, and North Carolina is not a no-fault state, which surprises many people. What follows is specific to autonomous vehicles.

If you were a passenger, the rule barely reaches you. You did not steer, brake, accelerate, or select a route. There is no conduct to characterize as negligent. In an ordinary rideshare case a defendant can at least argue about seatbelt use or distracting the driver. In a robotaxi there is no driver to distract. This is close to the cleanest liability posture available in a state with the harshest fault rule in the country, and it is why the robotaxi passenger injury claim is a materially different case from the one below.

If you were driving and were struck, the rule becomes the central battleground. The company holds a continuous, timestamped, multi-sensor record of the seconds before impact. It will be reviewed for your speed, your lane position, your following distance, your reaction time, and whether you signaled. The operator does not need to prove you caused the crash. It needs one percent. That is a lower bar than most people believe, and it is met with data you do not have and cannot independently verify without formal discovery. The struck by a driverless vehicle and contributory negligence and sensor data pages develop this in detail.

The practical instruction is the same in both postures and it is unusually important here. Do not give a recorded statement to an operator, an insurer, or a manufacturer representative before speaking with an attorney. A single casual concession is enough.

The Evidence a Robotaxi Records, and Why Preservation Is Urgent

These vehicles generate a richer record than any conventional crash produces, and the company that may be liable is the party holding all of it. Retention runs on internal schedules, which is why a written preservation demand needs to go out within days rather than weeks.

A robotaxi involved in a Charlotte collision will typically hold some or all of the following:

• Sensor returns. Lidar, radar, and camera data covering the full field around the vehicle, usually from every direction at once.
• Perception output. What the system classified each object as, and when. This is where a failure to recognize a pedestrian or a cyclist becomes visible.
• Planning and decision logs. What maneuver the system selected, what alternatives it evaluated, and what triggered the choice.
• Vehicle state. Speed, steering angle, throttle, and brake application on a continuous timeline.
• Remote assistance records. Whether a human operator was consulted, what was asked, and what was instructed.
• Disengagement and fault history. Whether this vehicle or this software build had known problems in similar conditions.

That record is powerful in either direction. It can demonstrate that the system saw a hazard and chose badly. It can also be assembled into a contributory negligence argument against you. Either way, it is the case. A preservation demand identifying the trip, the vehicle, and the specific data categories should be served on the operator, the manufacturer, and any dispatch platform as early as possible, and federal sources including the NHTSA standing general order crash reporting program and NTSB investigation materials should be pursued in parallel. The robotaxi data preservation page sets out the full demand.

Injured as a Passenger Inside a Robotaxi

A robotaxi passenger claim is structurally simpler than an ordinary rideshare claim. There is no independent contractor driver standing between the injured person and the company, and almost nothing for a contributory negligence defense to attach to.

In a conventional Uber or Lyft injury claim, the first question is the driver’s employment status and which of three coverage periods applied. Neither question exists here. The vehicle is owned and operated by the company. The software making every driving decision was written by the company or its partner. When that vehicle causes a crash, the path runs directly to a corporate defendant carrying commercial coverage.

Practical steps that matter in the first days: save the trip identifier and the ride receipt, screenshot any in-app messages or incident reports, photograph the interior including where you were seated and the condition of any restraint, and seek medical evaluation the same day. Injuries from these collisions follow the same patterns as any other serious crash, and delayed presentation is used against claimants regardless of how the crash occurred.

Struck by a Driverless Vehicle While Driving

This is the hardest posture in North Carolina. The company holds the evidence, contributory negligence is a complete defense, and one percent is enough. Independent documentation collected in the first hours often decides the outcome.

The asymmetry is the problem. The operator has a synchronized multi-sensor record and in-house engineers who read it daily. You have your memory and whatever you gathered at the scene. That imbalance is why what you do in the first hours carries disproportionate weight:

• Photograph vehicle positions before anything moves, along with skid marks, debris, signals, and sight lines.
• Collect witness names and phone numbers. Independent witnesses are the strongest counterweight to a company’s own data.
• Preserve your own dashcam footage immediately if you have one, including the minutes before impact.
• Get medical attention the same day and describe every symptom, including those that seem minor.
• Decline recorded statements until you have spoken with a lawyer.

Standard Charlotte car accident principles still apply. What changes is the sophistication of the opponent and the fact that the decisive evidence sits on the other side from the first minute.

Robotaxi Pedestrian and Cyclist Injuries

Pedestrians and cyclists face the most consequential version of this technology’s failure modes, because a perception error involving a person on foot or on a bicycle has no protective structure between the vehicle and the body.

Autonomous perception systems classify what they detect, and classification can fail. A person pushing a bicycle, a pedestrian partly hidden by a parked vehicle, a cyclist in low light, or someone crossing outside a marked crosswalk each present recognition problems that the logs will document precisely. That documentation is the case. It is also the reason these claims are worth pursuing rather than assuming a jaywalking allegation ends them.

Contributory negligence is where these claims are usually attacked, since North Carolina’s rule applies to pedestrians and cyclists exactly as it applies to drivers. Our Charlotte pedestrian accident and Charlotte bicycle accident practices handle that defense, and the robotaxi pedestrian and cyclist page addresses the perception-failure evidence specifically.

Robotaxi Claims Compared to Uber and Lyft Claims

The two look similar from the back seat and share almost no legal machinery. A rideshare claim turns on which coverage period a human driver was in. A robotaxi claim has no driver, no periods, and no personal auto policy underneath it.

If your crash involved a human rideshare driver rather than a driverless vehicle, our Charlotte rideshare accident practice covers that framework. If you are not certain which you were in, the registration card is determinative: Section 20-401(h)(5) requires a fully autonomous vehicle to be identified as such on its registration.

What the Litigation Record Shows So Far

Juries have already found an automated driving system defective. In August 2025 a Miami federal jury returned a 243 million dollar verdict against Tesla over a fatal crash involving Autopilot, and in February 2026 the trial judge refused to disturb it. That case involved driver assistance rather than a driverless vehicle, and the distinction matters.

In Benavides v. Tesla, tried in the United States District Court for the Southern District of Florida, jurors found Tesla 33 percent responsible for a 2019 Key Largo collision that killed 22-year-old Naibel Benavides and catastrophically injured Dillon Angulo. The jury awarded 129 million dollars in compensatory damages and 200 million dollars in punitive damages. On February 20, 2026, United States District Judge Beth Bloom denied Tesla’s motion to overturn the verdict or grant a new trial, writing that the evidence admitted at trial more than supported it, as reported by CNBC.

About that figure: this was not our case and not our result. It was tried in Florida, under Florida law, by other lawyers, and it is cited here only because it is a matter of public record that shaped how these claims are evaluated nationally. Florida applies comparative fault, which is why a 33 percent allocation still produced a recovery. In North Carolina the same allocation against a plaintiff would have barred the claim entirely. Past results, whether this firm’s or anyone else’s, do not predict or guarantee the outcome of any other case.

Two things about that case are worth separating carefully, because most coverage runs them together. It concerned Autopilot, a Level 2 driver assistance system with a licensed human responsible for the vehicle, not a fully autonomous vehicle under Section 20-400. The legal theory, however, transfers directly. The plaintiffs proved that a manufacturer can be held responsible for how an automated system was designed, how its limits were communicated, and what the company knew about its failure modes. That is precisely the theory that applies to a robotaxi, where there is no driver left to absorb the blame.

The regulatory record points the same direction. NHTSA operates a standing general order requiring manufacturers and operators to report crashes involving automated systems, and those filings, along with defect investigation and recall records, are obtainable and usable in an individual claim. A company that reported similar failures before your crash is in a materially different position than one facing an isolated event.

What to Do After a Robotaxi Crash in Charlotte

Autonomous vehicle evidence sits on company servers under retention schedules you cannot see. The steps below are ordered by how quickly the opportunity closes, not by how obvious they seem.

1. Call law enforcement and make sure a report is created. Section 20-401(g) requires the vehicle to remain until information is exchanged and an officer authorizes removal. If it left, document that.
2. Photograph everything before anything moves. Vehicle positions, the autonomous vehicle’s sensor housings, its registration and markings, the roadway, and your injuries.
3. Capture the trip and vehicle identifiers. If you were a passenger, save the trip record and receipt. If you were struck, photograph the vehicle number and plate.
4. Collect independent witnesses. Their accounts are the strongest counterweight to a company’s internal data.
5. Get medical attention the same day. Gaps in treatment are used to argue injuries were minor or unrelated.
6. Contact a lawyer within days, not weeks. Preservation demands must reach the operator, the manufacturer, and the platform before retention cycles run. Call Sofia, our AI intake line, at (980) 238-HELP. She answers immediately at any hour and can start your free consultation on the same call.

Deadlines That Apply to a Charlotte Robotaxi Claim

Two and sometimes three deadlines run at once. Personal injury is three years from the crash. Wrongful death is two. A product liability claim against the manufacturer runs on the same three-year clock and is cut off separately by a twelve-year statute of repose measured from the date the vehicle was first purchased.

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 most often miss while an estate is being opened.