California Lemon Law for Random Power Loss Events

Experiencing sudden loss of power while accelerating, merging, or climbing a hill can be alarming—and dangerous. In California, these “random power loss” events can be more than just frustrating; depending on the circumstances, they may point to a warranty-covered defect. This article explains, in plain language, when these issues may fall under the California Lemon Law and how to document them to protect your rights. It’s general information only and not legal advice.

When Random Power Loss May Qualify as a Lemon

Under California’s Lemon Law (part of the Song-Beverly Consumer Warranty Act), a vehicle may qualify as a “lemon” if it has a defect that is covered by the manufacturer’s warranty, substantially impairs the vehicle’s use, value, or safety, and the manufacturer or its authorized dealer cannot fix it after a reasonable number of repair attempts. Random power loss—like sudden hesitation, stalling, or the vehicle slipping into “limp mode”—often impacts safety and use, which can satisfy the “substantial impairment” aspect. What matters is that the problem happens during the warranty period and that the manufacturer has reasonable opportunities to repair it.

California also has helpful presumptions within the first 18 months or 18,000 miles (whichever comes first): for example, if a serious safety defect isn’t fixed after two or more attempts, or other defects after four or more attempts, or the car is out of service for 30 or more cumulative days for warranty repairs, the law presumes the manufacturer had a reasonable chance to fix it. Random power loss that creates safety risks—like losing acceleration while crossing an intersection—can fall into the “serious safety” category, but every situation is fact-specific. Even if your case falls outside the presumption period, you may still have rights if the defect started (or repair attempts began) within the warranty.

Power loss can stem from many systems: fuel delivery (high-pressure pumps, injectors), ignition and sensors (mass airflow, throttle body, cam/crank sensors), turbo or hybrid/electric components (inverters, battery management), or software issues requiring updates. You don’t need to know the technical cause to preserve your rights. What you do need is to ensure the issue is documented as occurring under warranty and that the dealer writes down your symptoms clearly, even if the problem is intermittent or the check engine light turns off before service.

Steps to Document Random Power Loss and Repairs

Start by describing the symptoms the same way every time you visit the dealer. Note whether the loss of power happens at highway speed, during acceleration, on hot days, after cold starts, or while the air conditioning is on. If you safely can, capture short videos of the tachometer, speedometer, warning lights, or messages like “reduced power” when the issue occurs. Write down dates, mileage, fuel level, outside temperature, and whether any warning lights flashed—even briefly.

Always request a detailed repair order and final invoice at each visit. Make sure they accurately state your complaint (e.g., “customer reports sudden power loss while merging, nearly stalled; check engine light flashed, then went off”) and list any diagnostic codes, test drives, parts replaced, software updates, and “could not duplicate” notes. Ask the advisor to include freeze-frame data, OBD-II codes, and mileage in/out. Keep copies of tow receipts, rental or rideshare expenses related to the repair, and any recall or Technical Service Bulletin (TSB) notices you receive.

If the issue continues, consider notifying the manufacturer in writing, following the instructions in your warranty booklet, and keep proof of delivery. Track total days your vehicle is in the shop for warranty repairs, as those days can add up quickly with intermittent problems. Before any out-of-pocket repairs, check whether the vehicle is still within the basic or powertrain warranty or has extended coverage. If a dealer suggests a software update or sensor replacement, return promptly for follow-up if the problem returns—consistent, timely documentation helps show a pattern.