Tesla Autopilot and Full Self-Driving (FSD) features sit in a legal gray area that marketing language does not resolve. California’s Vehicle Code draws a line between true “autonomous vehicles” and driver-assistance systems that still require a human’s active control or monitoring. When a crash happens with Autopilot or FSD engaged—or when someone claims it was engaged—the case often turns on logs, settings, and driver conduct as much as on slogans about “self-driving.”
This guide covers practical steps and evidence to preserve after a Tesla Autopilot or FSD-related collision in California. It does not promise any outcome against Tesla or any other defendant. Related reading: AI car accident attorney and car accident lawyer.
Autopilot / FSD vs. “autonomous vehicle” under California law
Vehicle Code section 38750 defines autonomous technology as technology capable of driving without active physical control or monitoring by a human operator. It expressly states that vehicles equipped with collision-avoidance and similar assistance systems—adaptive cruise, lane keep, automated emergency braking, and comparable features that are not capable of driving without active human control or monitoring—are not “autonomous vehicles” under that division.
That statutory carve-out matters for regulatory classification. It does not end civil liability analysis. A driver-assist crash can still involve:
- Negligence by the human driver who was supposed to supervise the system
- Negligence or product theories aimed at design, warnings, or performance of the assistance features
- Negligence by other motorists, pedestrians, or roadway actors
- Comparative fault among some combination of the above
Whether Autopilot or FSD was “on,” what mode it was in, how the driver was interacting with the wheel and pedals, and what alerts the car issued are factual questions. They belong in the evidence file, not in assumptions.
Immediate steps after the crash
- Safety and medical care. Call 911 when there are injuries or a dangerous scene. Get evaluated even if you feel “mostly okay.” Delayed symptom onset is common in collision cases.
- Scene documentation. Photograph vehicle positions, damage, roadway markings, weather, lighting, and any screen or display that still shows system status—if it is safe and lawful to do so.
- Information exchange. Comply with California post-accident duties, including exchanging identifying information when required under the Vehicle Code.
- Avoid speculation in statements. Do not guess on the roadside about whether Autopilot “caused” the crash. Stick to what you observed. Recorded statements to insurers can lock in incomplete theories before the data is reviewed.
- DMV reporting. When Vehicle Code section 16000 applies (injury, death, or property damage above the statutory threshold), file the SR-1 within the required time. A police report alone may not satisfy the DMV filing.
Evidence that often matters in Autopilot / FSD claims
Tesla vehicles and related systems can generate substantial digital evidence. Preservation should start early—vehicles get repaired, sold, or overwritten.
Priority items commonly include:
- Vehicle logs and event data showing speed, braking, steering inputs, Autopilot/FSD engagement status, driver monitoring alerts, and disengagement events around the collision window
- Infotainment / settings screenshots or records reflecting the feature version, software build (when available), and configuration
- Cabin and forward camera footage, if retained and obtainable through proper legal process
- Mobile app history tied to the vehicle account, where relevant
- Prior service and repair records for sensors, cameras, windshield replacements (which can affect camera calibration), and recalls or software updates
- Police downloads, airbag control module data, and any third-party EDR imaging done with a proper chain of custody
- Witness statements about driver attention, hands on wheel, and vehicle behavior in the seconds before impact
- Roadway evidence: construction zones, faded lane lines, sun glare, and other conditions that interact with camera-based systems
Do not attempt DIY “hacking” of modules. Improper downloads can destroy authenticity arguments. Use qualified technicians and counsel-directed preservation letters to Tesla, insurers, and any third-party custodians.
If another vehicle was involved, preserve that vehicle’s data too. Comparative facts—another driver’s phone use, speeding, or failure to yield—still matter under Civil Code section 1714.
How liability theories are typically framed
Every case is fact-specific. Broadly, California claims after an Autopilot/FSD crash may involve:
Driver negligence. The human driver remains responsible for operating the vehicle with ordinary care. Distraction, impairment, speeding, or ignoring system prompts can support negligence theories against the driver—whether that driver is you, a family member, or someone else.
Other road users. Rear-end collisions, unsafe lane changes, and pedestrian path conflicts remain classic negligence cases even when a Tesla’s assistance features were active.
Product liability. California’s strict products liability doctrine, rooted in cases such as Greenman v. Yuba Power Products, Inc. (1963) 59 Cal.2d 57 and design-defect analysis in Barker v. Lull Engineering Co. (1978) 20 Cal.3d 413, can apply when a defect in design, manufacture, or warnings causes injury. Proving a software or sensor-related defect is technical work. It is not automatic from the mere fact that Autopilot was named in a police report.
Failure-to-warn / marketing-interaction issues. How features were described, what the owner’s manual and in-car prompts required, and whether warnings were adequate can become part of a products or negligence case—again, on proof, not on advertising rhetoric from either side.
None of these theories assures a particular result against Tesla or any manufacturer. Defendants contest engagement status, driver misuse, comparative fault, and causation. Treat early “we’ll take care of it” messages from any company or insurer as claims handling, not as an admission.
Insurance realities
Expect multiple claim files: the Tesla driver’s liability coverage, your own first-party coverages (med-pay, UM/UIM, collision), and, in some cases, product or corporate liability channels once litigation or formal claims mature. Insurers may press for early recorded statements focused on “were you watching the road?” Answer carefully. Inconsistent or speculative answers are hard to walk back after the logs arrive.
If your own carrier unreasonably delays or denies first-party benefits you are owed, that can raise separate good-faith issues. The underlying injury lawsuit against private tort defendants is generally subject to the two-year period in Code of Civil Procedure section 335.1. Public-entity claims can require much earlier administrative filings.
Practical timeline
Days 1–7: Medical care, scene documentation, police/DMV reporting, notice to your insurer, and a litigation hold / preservation request for vehicle data.
Weeks 2–8: Follow-up treatment, obtain the traffic collision report, identify all insurance policies, and avoid repairing or disposing of the Tesla (or other critical vehicles) until data extraction is addressed.
Ongoing: Calendar suit deadlines; evaluate whether qualified technical consultants are needed; do not settle away claims you have not fully investigated.
Advo Law, APC handles California motor vehicle and advanced-driver-assistance crash matters on a contingency fee basis, with offices in Glendale and La Cañada Flintridge.
Contact Advo Law
If you were hurt in a crash involving Tesla Autopilot, FSD, or similar driver-assist technology, preserve the vehicle and the data before they slip away.
Advo Law, APC
Glendale: 111 E. Broadway, Suite 210, Glendale, CA 91205
La Cañada Flintridge: 1433 Foothill Blvd., Suite 207, La Cañada Flintridge, CA 91011
Phone: (800) 808-4613
Contact us · AI / Autopilot accident claims · Car accident lawyer
Contingency fee representation. Serving clients throughout California.
Attorney advertising. This article is for general information only and is not legal advice. Reading it does not create an attorney-client relationship. No outcome is promised against any manufacturer or insurer. Consult counsel about your specific situation.
