California Lemon Law for Check Engine Light Errors

When your check engine light keeps coming back after multiple trips to the dealership, it’s more than an annoyance—it may be a sign of a defect covered by California’s Lemon Law. California gives consumers strong protections when a vehicle has persistent issues under warranty that the manufacturer can’t fix within a reasonable number of attempts. Below, ZapLemon explains how check engine light problems can trigger lemon law rights and what steps to take to document your repair history.

When Check Engine Light Issues Trigger California Lemon Law

In plain terms, California’s Lemon Law (part of the Song-Beverly Consumer Warranty Act) applies when a vehicle has a defect covered by the manufacturer’s warranty and the dealer can’t repair it after a reasonable number of attempts. “Reasonable” depends on the situation—generally more attempts are expected for non-safety issues, and fewer for safety-related problems. The law can also apply if your car spends a significant number of days in the shop for warranty repairs. The check engine light (CEL) can be the warning sign of both kinds of problems, from emissions faults to drivability and stalling.

Common check engine light issues that may rise to lemon-level concerns include repeated catalytic converter efficiency faults (for example, P0420), misfire codes that cause rough running or loss of power (P0300-series), transmission control errors leading to hard shifts, and sensor failures that trigger limp mode. If these defects substantially impair the vehicle’s use, value, or safety and the dealership can’t fix them within a reasonable number of attempts, lemon law remedies may be available. A flashing check engine light, frequent stalling, or inability to pass a smog test are red flags of a potentially substantial issue.

Timing matters. California has a “presumption” that helps consumers if problems arise within the first 18 months or 18,000 miles (whichever comes first) and meet certain repair-attempt or days-out-of-service thresholds. But even if your vehicle falls outside those early windows, you may still have rights under the broader warranty protections if the defect existed or arose during the warranty period and wasn’t fixed after reasonable attempts. The key is that the defect must be covered by warranty and persist despite the manufacturer’s opportunities to repair.

How to Document Check Engine Light Repair Attempts

Start by keeping a clean paper trail. Each time the check engine light comes on, note the date, mileage, driving conditions, and any symptoms (loss of power, rough idle, stalling, poor fuel economy). Take a photo or short video of the dashboard with the CEL illuminated. If you have an OBD-II scanner, record the trouble codes and freeze-frame data; if not, ask the service advisor for a printout of the codes attached to your repair order.

Every dealership visit should generate a detailed repair order (RO). Make sure the “customer states” section lists your exact complaint (for example: “Check engine light on; vehicle hesitates when accelerating; was unable to pass smog”). Confirm that the RO includes the mileage in/out, diagnostic steps taken, parts replaced, software updates performed, and whether the light was verified and cleared. Before leaving, ask for a copy of the final RO—even if “no problem found” is written—because those “no-fault-found” visits still count as repair attempts.

Track downtime. Note every day the vehicle is at the dealership for warranty repairs, including parts wait times. Save related expenses such as towing or rental car receipts if provided by the warranty or manufacturer program. Keep all records in a single folder or digital drive: purchase/lease paperwork, warranty booklet, all ROs, photos, emails or texts with the dealer or manufacturer, and any case numbers. A clear timeline helps show the pattern of a recurring defect and supports your discussion with ZapLemon or with the manufacturer about potential next steps.