SAE Level 2: What Autopilot and FSD Actually Are – and What That Means for Liability

Tesla Autopilot and Full Self-Driving are SAE Level 2 driver assistance systems. Understanding what Level 2 means – and, critically, what it does not mean – is the essential starting point for both the driver’s liability and Tesla’s manufacturer liability in any Charlotte Autopilot accident case.

The Society of Automotive Engineers defines six automation levels (0-5):

The Level 2 liability paradox: At Level 2, the system controls steering and speed while the law requires the human driver to remain attentive and responsible. This creates a legal fault structure where the driver is responsible for the outcome, but the manufacturer can still be liable if the system’s design creates a foreseeable risk that driver supervision will lapse. The key product liability question is not whether the driver should have been paying attention – they should have been – but whether Tesla designed a system that predictably creates conditions where inattention occurs, and failed to adequately guard against it.

NHTSA’s Autopilot Investigation Record: Public Evidence Your Attorney Must Retrieve

NHTSA has conducted more investigations into Tesla’s Autopilot and FSD systems than into any other driver assistance system in history – and the public records generated by those investigations are available through FOIA requests and NHTSA’s online database. In a Charlotte Tesla Autopilot accident case, these records are among the most powerful evidence available.

Key NHTSA investigations relevant to Charlotte Tesla Autopilot accident claims:

• PE 21-020 and follow-on investigations – Autopilot and stationary vehicles: NHTSA’s investigation into Tesla crashes involving Autopilot-engaged vehicles colliding with stationary emergency vehicles. The investigation covered hundreds of incidents and resulted in a NHTSA consent order requiring Tesla to submit crash data. The investigation records establish NHTSA’s documented concern about Autopilot’s failure to detect and respond to stationary objects in its path.
• PE 23-002 – Phantom braking: NHTSA’s investigation into thousands of Tesla consumer complaints about sudden, unprovoked emergency braking events in Autopilot mode. Investigation records document the frequency, speed conditions, and road type patterns associated with phantom braking – evidence directly applicable to any Charlotte I-485 or I-77 phantom braking incident.
• FSD Beta performance reviews: NHTSA’s monitoring of Tesla’s FSD Beta deployment, including specific documented scenarios where FSD behavior at intersections, crosswalks, and construction zones created safety concerns. These records support failure-to-warn claims based on Tesla’s knowledge of specific FSD performance limitations.

Your attorney accesses these records through NHTSA’s Complaints and Investigations database, FOIA requests for specific investigation communications, and the detailed consent order documentation that Tesla has filed with NHTSA. The existence of these investigations – and Tesla’s knowledge of the specific defects they document – is powerful evidence under the knew or should have known standard applicable to both design defect and failure to warn claims under N.C.G.S. §§ 99B-4 and 99B-5.

Tesla Phantom Braking: A Design Defect Claim Under N.C.G.S. § 99B-4

Tesla phantom braking – sudden emergency braking events triggered by Autopilot’s false perception of obstacles that do not exist – is not a driver complaint. It is a product defect claim: the Autopilot system’s perception algorithm generates false-positive obstacle detections that trigger emergency braking in highway traffic, creating rear-end chain collisions that Tesla’s design, not driver behavior, caused.

On Charlotte’s I-485 outer belt and I-77 corridor – where Autopilot is most commonly engaged in highway cruise mode – a phantom braking event at highway speed creates a specific accident pattern:

1. Tesla vehicle with Autopilot engaged decelerates sharply from 65-70 mph to 25-35 mph in seconds
2. Following vehicle traveling at highway speed has insufficient time to react
3. Rear-end collision occurs with a closing speed of 30-45 mph
4. Chain collision may involve additional following vehicles

Under N.C.G.S. § 99B-4, a product design is defective when: (1) the product as designed was unreasonably dangerous; (2) a safer alternative design was available at reasonable cost; and (3) the failure to adopt the safer design rendered the product unreasonably dangerous. For phantom braking, the design defect analysis examines: whether Tesla’s perception algorithm’s false-positive rate exceeded what reasonable engineering practice permits; whether alternative perception architectures (sensor fusion improvements, confidence threshold adjustments) were available; and whether Tesla’s over-the-air update history shows the company knew of and attempted to patch the phantom braking defect – evidence that the company itself recognized the design was inadequate.

Who is liable in a Charlotte phantom braking rear-end crash? The following driver who struck the Tesla may bear liability to a third vehicle, but may also have a phantom braking claim against Tesla if the sudden deceleration created an unavoidable situation. The Tesla occupants injured by rear-end impact have a claim against the following driver (respondeat superior if that driver was on employment duty) and potentially against Tesla if the phantom braking was the proximate cause of the collision.

FSD at Charlotte Intersections: Documented Failure Scenarios and Claim Value

Tesla’s Full Self-Driving system performs differently at intersections than on highways – and FSD’s intersection behavior in Charlotte’s specific road environment, with its mix of older signal timing infrastructure, non-standard lane markings, and high pedestrian-bicycle crossings, creates documented failure scenarios that support both design defect and failure to warn claims.

FSD Beta’s documented intersection failure scenarios include:

• Unprotected left turns: FSD’s handling of unprotected left turns across oncoming traffic is one of the most frequently cited failure scenarios in consumer reports and NHTSA complaints. Charlotte’s high-traffic intersections on Providence Road, Rea Road, and the Independence Boulevard corridor have exactly the intersection geometry where FSD unprotected left-turn failures occur most frequently.
• Construction zone behavior: Charlotte is in a period of active road construction on I-485, I-77, and multiple surface street corridors. FSD’s behavior in active construction zones – where lane markings are temporarily altered, barriers are present, and standard traffic flow patterns are disrupted – is a documented failure category that NHTSA has specifically investigated.
• Pedestrian and cyclist detection inconsistency: FSD’s pedestrian and cyclist detection in mixed urban environments – such as Charlotte’s NoDa, Plaza Midwood, and South End corridors where cyclists and pedestrians are highly present – has generated consumer reports of inconsistent system behavior.
• Software version variability: Tesla deploys FSD updates over-the-air, and different software versions have significantly different performance characteristics at intersections. The specific FSD software version running at the time of a Charlotte accident is critical evidence – a version with known intersection behavior issues supports a stronger design defect claim than a version without documented problems.

Tesla Autopilot Design Defect Claims Under N.C.G.S. § 99B-4

North Carolina’s design defect standard under N.C.G.S. Section 99B-4 provides the specific legal framework for Charlotte Tesla Autopilot accident claims that DeMayo’s Charlotte Tesla coverage does not analyze – and it requires examination of both what Tesla designed and what safer alternatives were reasonably available.

Under N.C.G.S. § 99B-4, Tesla’s Autopilot design defect claim requires establishing:

• The product was unreasonably dangerous as designed: Tesla’s Autopilot system – specifically its combination of capability, naming, interface design, and attention monitoring system – foreseeably creates driver over-reliance that results in preventable crashes. The NHTSA investigation record documents regulators’ concern about this exact risk at scale.
• A safer alternative design was available: Competitor Level 2 systems (GM Super Cruise, Ford BlueCruise) use driver-facing cameras and mandatory eye-tracking to enforce continuous driver attention before the system will operate. Tesla’s attention monitoring relies on steering wheel torque detection, which has been documented as easier to defeat than camera-based attention monitoring. The existence of more restrictive attention monitoring in comparable products at comparable cost is evidence of a feasible, safer alternative design.
• The failure to adopt the safer design rendered the product unreasonably dangerous: Tesla’s choice to use torque-based rather than camera-based attention monitoring, combined with its marketing of Autopilot as near-autonomous, created a system that predictably produced inattentive drivers – the exact accident pattern NHTSA has documented in over 1,000 Autopilot-related crash reports.

Note: N.C.G.S. § 99B-4 also requires that the plaintiff not have misused the product in a way Tesla could not reasonably anticipate. Using Autopilot on a highway for which it is designed, while maintaining basic attentiveness, is the intended and marketed use of the product. This is not misuse that defeats the design defect claim.

Tesla Failure to Warn: ‘Full Self-Driving’ as the Defective Warning Itself

Tesla’s product name ‘Full Self-Driving’ is arguably the most consequential product naming decision in automotive history from a liability standpoint – it attributes a capability the product does not have, contributes to documented driver over-reliance, and has been cited by NHTSA as a concern in its enforcement actions against Tesla. Under N.C.G.S. Section 99B-5, this is a failure to warn claim.

Under N.C.G.S. § 99B-5, a manufacturer is liable for failure to warn when: (1) the product was in a defective condition unreasonably dangerous because of a lack of adequate warning; and (2) the adequate warning would have reduced or eliminated the danger. Applied to Tesla FSD naming:

• The “Full Self-Driving” name conveys autonomy the system lacks: Consumer research has consistently shown that “Full Self-Driving” leads users to attribute Level 4-5 capabilities to a Level 2 system. Tesla’s own engineers have used the term “supervised full self-driving” to describe the system – acknowledging that “full” is inaccurate without supervision qualification.
• Tesla’s known-limitation disclosure has been inadequate: The specific scenarios where FSD will disengage without warning, where Autopilot will fail to detect stationary objects, and where phantom braking is most likely to occur are not disclosed in Tesla’s consumer-facing materials at a level commensurate with the safety risk those scenarios create. Tesla’s over-the-air update changelogs implicitly acknowledge these limitations, but most users do not read update changelogs.
• NHTSA’s enforcement creates the “knew or should have known” element: Once NHTSA initiates a formal investigation and issues a consent order, Tesla’s knowledge of the specific defect is established beyond dispute. A Charlotte Tesla Autopilot accident that occurred after NHTSA’s investigation findings were published – and while Tesla had not issued adequate warnings about the identified failure modes – creates a strong failure to warn claim.

Autopilot Log Evidence: What to Demand and How to Use It in Your Charlotte Case

The Autopilot engagement logs stored in a Tesla vehicle involved in a Charlotte accident are the most important single piece of evidence in any FSD or Autopilot liability case – because they simultaneously establish the driver’s behavior and the system’s behavior in the minutes before the crash, and can support or defeat claims on both sides of the multi-party liability analysis.

What Autopilot logs record and how your attorney uses each data point:

• Autopilot engagement status: Whether Autopilot or FSD was engaged at the time of the crash, and at what sub-level (Traffic-Aware Cruise Control, Autosteer, FSD Navigate on Autopilot, etc.). Establishes the system’s role in the pre-crash vehicle behavior.
• Attention warning count and timing: The number of attention prompts issued to the driver in the period before the crash and the driver’s response or non-response to each. Used both to establish driver inattention (supporting at-fault driver liability) and to evaluate whether the warning system’s design was adequate (supporting Tesla design defect claim if the warnings were insufficient to actually compel attention).
• Hands-on-wheel detection history: Tesla detects steering wheel contact through torque sensors. Log data showing the driver’s hands were not on the wheel for extended periods immediately before the crash is evidence of over-reliance – and also evidence that Tesla’s torque-based detection system failed to compel re-engagement when camera-based detection might have.
• System disengagement timing: If Autopilot disengaged immediately before the crash, the logs show exactly when disengagement occurred, the disengagement trigger, and the time available to the driver between disengagement and impact. A disengagement with less than one second of driver reaction time available supports the argument that the system’s disengagement design was unreasonably dangerous.
• Software version: The specific FSD or Autopilot software version running at crash time. Cross-referenced with NHTSA complaint data and Tesla’s own over-the-air update release notes, the software version establishes what known issues were present in the version running at the time of the Charlotte accident.

NC Contributory Negligence and Multi-Party Autopilot Accident Claims

NC’s contributory negligence rule applies with full force to the at-fault driver analysis in a Charlotte Tesla Autopilot accident – but product liability claims against Tesla under N.C.G.S. Sections 99B-4 and 99B-5 provide a parallel recovery path that a victim’s contributory negligence does not automatically bar.

The multi-party liability structure of a Charlotte Tesla Autopilot accident often involves three distinct defendant categories:

1. The inattentive Tesla driver: If the Tesla driver’s inattention while Autopilot was engaged caused the collision, the driver is a negligent defendant. Your claim against this driver is subject to NC contributory negligence – if you had any fault, this claim is barred.
2. Tesla Corporation as manufacturer: If Autopilot’s design created the conditions for driver inattention, or if a phantom braking or FSD failure directly caused the crash, Tesla faces product liability under N.C.G.S. §§ 99B-4 and 99B-5. Your contributory negligence in the collision generally does not bar this product defect claim – the question is whether the product defect, not your conduct, caused or contributed to your injuries.
3. Third-party negligent parties: In multi-vehicle crashes involving Tesla Autopilot, additional parties (other drivers, road design defects) may share liability. Each is evaluated separately, and each can be pursued simultaneously with the Tesla manufacturer claim.

Charlotte NC Car Accident Lawyers Group structures all available claim tracks from the first day, ensuring that the product liability claim against Tesla proceeds in parallel with any driver negligence claim – maximizing recovery options regardless of how NC contributory negligence affects the at-fault driver claim.

Frequently Asked Questions: Tesla Autopilot FSD Accident Lawyer Charlotte NC

Related Tesla Autopilot FSD Accident Resources

• Charlotte Electric Vehicle Accident Lawyers
• Tesla Accident Charlotte
• EV Battery Fire Accident Charlotte
• EV Charging Station Accident Charlotte
• Rivian Accident Charlotte
• Chevy Bolt GM EV Recall Accident Charlotte
• Charlotte Car Accident Lawyer
• Charlotte Catastrophic Injury Lawyers
• Charlotte Wrongful Death Lawyers
• Can I Sue If Partially at Fault in NC?
• Is North Carolina a No-Fault State?

Your Charlotte Tesla Autopilot FSD Accident Lawyers

Steve Hayes, J.D. – Founder & Managing Attorney

Steve Hayes has represented personal injury clients in Charlotte since 1991, including complex product liability cases requiring technical expert analysis and regulatory record retrieval, bringing this expertise to Charlotte Tesla Autopilot and FSD accident claims.

Bar: NC (#18224) | SC | Education: UNC Greensboro, B.A. | Campbell University School of Law, J.D.

Cameron Bauer, Esq. – Associate Attorney

Cameron Bauer represents personal injury clients in North Carolina EV accident cases including Tesla Autopilot product liability claims, building the NHTSA investigation record and design defect analysis needed to pursue Tesla manufacturer liability under N.C.G.S. Sections 99B-4 and 99B-5.

Bar: NC (#63306) | Education: University of South Carolina, B.A. | Elon University School of Law, J.D.

Authoritative Sources

• N.C.G.S. §§ 99B-1 through 99B-11 – NC Products Liability Act
• N.C.G.S. § 1-139 – Contributory Negligence
• N.C.G.S. § 1-52 – Statute of Limitations
• N.C.G.S. § 1D-1 – Punitive Damages Act
• 49 C.F.R. § 571.305 – FMVSS 305 Electric Vehicles
• National Highway Traffic Safety Administration
• U.S. Consumer Product Safety Commission
• North Carolina State Bar
• NHTSA Automated Vehicles Safety – Tesla Investigations
• SAE J3016 – Levels of Driving Automation