The driver is responsible. Advanced driver assistance systems (ADAS) like lane-keeping assist, adaptive cruise control, and automatic emergency braking are designed to back you up, not replace you. The National Highway Traffic Safety Administration is clear on this point: ADAS features “do not perform the driving function,” and “the driver must remain fully engaged in the driving task at all times.” NHTSA’s guidance goes further, recommending you drive as if the technology isn’t there and let it serve as a safety net.
That said, responsibility isn’t always black and white. When an ADAS-equipped vehicle is involved in a crash, the question of fault can extend beyond the driver to the manufacturer, the software developer, or even the dealer, depending on what went wrong.
Why the Driver Is Still the Default
Nearly every ADAS feature available on consumer vehicles today falls under what engineers call Level 1 or Level 2 automation. At these levels, the system can handle specific tasks like steering within a lane or maintaining a set following distance, but a human must stay alert, keep hands on the wheel, and be ready to act at any moment. Even Tesla’s Autopilot and GM’s Super Cruise, which combine steering and speed control, are Level 2 systems. They require continuous driver supervision.
In most jurisdictions, drivers are the default defendant in crash lawsuits. Courts have consistently held that the mere presence of ADAS technology does not exempt you from liability. If you ignore a warning alert, take your eyes off the road because you assume the car “has it,” or deactivate a safety system and then crash, the responsibility falls squarely on you. Legal analysts describe this pattern as “automation complacency,” and it’s increasingly used as an argument against drivers who lean too heavily on their vehicle’s features.
When the Manufacturer Shares Blame
Responsibility can shift toward the manufacturer when the technology itself is at fault. Product liability law recognizes three main paths to holding a manufacturer accountable. A design defect means the system’s overall architecture was flawed in a way that made it dangerous. A manufacturing defect means a specific unit deviated from the intended design. And a failure to warn means the company didn’t adequately explain the system’s limitations or alert drivers to hidden risks.
European courts have been especially active in this area. Cases involving Tesla vehicles in Autopilot mode have emphasized that manufacturers must provide clear, sufficient information about what their systems can and cannot do. Vague marketing language that implies a car can “drive itself” could become evidence of a failure to warn if a crash occurs while the system is engaged. In practice, each incident requires a detailed look at the interaction between driver and technology, whether the system failed, whether the manufacturer met safety standards, and what information the driver received about the system’s capabilities.
Crash data recorders built into modern vehicles play a growing role in sorting out these questions. These devices store information like vehicle speed, steering input, and brake application in the seconds before and during a collision. That data can reveal whether the driver was paying attention, whether they attempted to intervene, and whether the ADAS system behaved as designed.
How Automation Levels Affect Responsibility
The SAE International standard (J3016) defines six levels of driving automation, numbered 0 through 5. At Level 0, there is no automation at all: the driver handles everything. Levels 1 and 2 add increasing assistance, but the driver remains responsible for monitoring the road and the system’s performance at all times. This is where virtually every car on the road today sits.
Level 3 is where things get legally interesting. At this level, the automated system handles all driving tasks within certain conditions, and the driver is expected to respond when the system requests a takeover, but is not required to monitor the road continuously while the system is active. This creates a gray zone: if the system fails to request a takeover soon enough, or the driver fails to respond when asked, determining fault becomes far more complex. Only a handful of vehicles worldwide have received Level 3 approval, and they’re restricted to specific driving scenarios like highway traffic under a certain speed.
Levels 4 and 5, which involve full automation with little or no human input, remain largely experimental. At those levels, responsibility would shift almost entirely to the system operator or manufacturer. But for the foreseeable future, the vehicles you can buy and drive fall under Levels 1 and 2, meaning the responsibility stays with you.
What This Means for Insurance
Insurance companies still treat the driver as the primary responsible party in ADAS-equipped vehicles. If you’re in a crash while using adaptive cruise control or lane-centering assist, your insurer will evaluate the incident much the same way they would any other collision: what were you doing, were you negligent, and could you have prevented it?
Where things diverge is in the potential for a third-party claim against the manufacturer. If evidence from the vehicle’s data recorder suggests the ADAS system malfunctioned, your insurer or attorney may pursue the manufacturer under product liability theories. But this doesn’t remove you from the equation. Courts regularly assess both driver behavior and system performance, and it’s entirely possible for fault to be shared between driver and manufacturer.
Your Practical Obligations
Owning a vehicle with ADAS features comes with a few responsibilities beyond just paying attention while driving. You should understand what each system does and, just as importantly, what it doesn’t do. Lane-keeping assist, for instance, may nudge you back into your lane but won’t navigate a sharp curve. Adaptive cruise control maintains a gap to the car ahead but may not detect a stationary object in the road.
Keeping your vehicle’s software current matters too. Manufacturers increasingly push over-the-air updates that can fix bugs, improve sensor calibration, or address safety issues identified after the vehicle was sold. When your car notifies you of an available update or a recall notice arrives, acting on it promptly helps ensure your systems perform as intended. NHTSA tracks crash data from ADAS-equipped vehicles through a standing reporting order that requires manufacturers to disclose incidents where automation was active. This data feeds into defect investigations and recalls, so staying on top of manufacturer communications keeps you connected to that safety pipeline.
The bottom line is straightforward: ADAS is a tool, not a co-pilot. The technology can reduce your workload and catch mistakes, but it doesn’t take the wheel in any legal, practical, or engineering sense. Until vehicles reach higher levels of automation and regulations catch up, the person in the driver’s seat bears primary responsibility for everything the car does.