Adaptive cruise control is the most widely deployed piece of real driver-assistance technology on the road. Unlike the futuristic promises that attach to “self-driving,” ACC is mundane and ubiquitous: it reads the vehicle ahead, modulates throttle and braking to hold a set gap, and hands a slice of the longitudinal control loop to software. That ordinariness is exactly why a defect inside it deserves scrutiny. When a feature most drivers use on every highway commute can fault in a way that removes propulsion, the failure mode is not exotic — it is statistically likely to occur at speed, in traffic, with the driver's attention relaxed because the system was, by design, doing the driving.
NHTSA campaign 24V076000, reported by Lucid USA on February 7, 2024, describes precisely that scenario. Lucid recalled certain 2022-2024 Air vehicles “running software release versions 2.1.2 through 2.1.26.” The defect, in Lucid's own description, is that “the software may cause a fault while the adaptive cruise control is on, resulting in a loss of drive power.” The consequence statement is one sentence and it is blunt: “A sudden loss of drive power increases the risk of a crash.”
A software-versioned recall, not a parts recall
The first thing that distinguishes this campaign from a traditional recall is how the affected population is defined. Lucid does not scope the recall by a defective component, a supplier lot, or a build date in the conventional sense. It scopes it by software version: every Air running release 2.1.2 through 2.1.26 is in the population, and a car outside that band is not. This is what a recall looks like when the defect is a bug. The “part” that failed is a specific range of firmware, and the boundary of the recall is a version string.
That framing matters because it reflects how driver-assistance features are actually built. ACC is not a discrete box; it is a control function distributed across sensing, perception, and actuation software that ships in versioned releases. A fault introduced in one release and present through a span of subsequent releases defines a contiguous affected range — exactly the 2.1.2-to-2.1.26 window Lucid identifies. The discipline of versioning, which lets a manufacturer ship features quickly, is the same discipline that lets it draw a precise boundary around a defect after the fact.
Why “loss of drive power” is the dangerous phrase
The recall does not say the car brakes unexpectedly or that ACC disengages with a warning. It says the fault results in a “loss of drive power.” In an electric vehicle, drive power is delivered by inverters and motors under continuous software command; if a fault in the control stack interrupts that command, the propulsion simply stops responding. A driver expecting the car to hold its speed under ACC instead finds it decelerating or coasting without the input they intended. On a highway, an unexpected loss of propulsion is its own hazard — vehicles behind close the gap, and the affected car may lose the ability to accelerate out of a developing conflict.
What makes this a driver-assistance failure rather than a generic powertrain fault is the trigger condition: the problem manifests “while the adaptive cruise control is on.” The fault lives at the intersection of the ADAS control loop and the propulsion command path. ACC has authority over how much power the car requests moment to moment; a fault in that software, under the right conditions, can corrupt or interrupt the request. This is the quiet risk of letting assistance software hold the throttle — when it works, the driver offloads attention, and when it faults, the consequence lands during exactly the relaxed-attention state the feature created.
The OTA remedy, and the timeline that reveals it
The remedy is an over-the-air software update, which is the natural fix for a software-versioned defect: replace the buggy releases with a corrected one, delivered without a service visit. But the timeline in 24V076000 contains a detail worth pausing on. Lucid states that it “released an over-the-air (OTA) software update in October 2023,” while owner notification letters were “expected to be mailed March 8, 2024,” and the recall itself was reported in February 2024. The corrective software, in other words, went out months before the formal recall paperwork caught up.
This ordering is increasingly common with OTA-capable fleets and it surfaces a real regulatory question: the engineering fix can propagate to cars long before the formal recall is filed and owners are notified. From a safety standpoint, an earlier fix is unambiguously good — the cars were patched in October. From a transparency standpoint, the recall record is what gives owners a verifiable, VIN-checkable account of what was wrong and what was done. The recall framework exists so that a fix is not merely pushed silently but documented; 24V076000 is that documentation arriving after the patch it describes.
For owners, the practical guidance is straightforward. A Lucid Air that has received the OTA update is moved out of the affected software range; the way to confirm is to verify the current software version and the recall status. Lucid identifies this campaign internally as SR-24-02-0 and directs owners to customer service at 1-888-995-8243. NHTSA maintains the canonical recall record, searchable by VIN, at its recalls portal.
The broader signal in 24V076000 is a maturing one. As more longitudinal control is handed to software, the recall system is learning to speak in version numbers, and the fix is learning to travel over the air faster than the paperwork. Both shifts are improvements — but the lesson of a feature that can cut power while you are trusting it to drive is that the assistance is only as safe as the release running on the car, and the only authoritative record of which releases were unsafe is the recall itself.