How to Clear an EVAP DTC on a 2009 Acura TL After a Repair

If you've fixed an EVAP-related issue on your 2009 Acura TL and the check engine light is still on — or you're trying to verify the repair is complete before an emissions test — understanding how EVAP diagnostic trouble codes (DTCs) work and how they clear is essential. This isn't as simple as erasing a code and driving away.

What the EVAP System Does and Why DTCs Linger

The Evaporative Emission Control (EVAP) system captures fuel vapors from the gas tank and routes them into the engine to be burned, rather than letting them escape into the atmosphere. On the 2009 Acura TL (which uses Honda's J35 V6), the EVAP system includes the fuel tank, a charcoal canister, purge valves, vent valves, and a network of hoses and seals.

When the system detects a leak or malfunction — anything from a loose gas cap to a failed canister vent solenoid — it stores a DTC and illuminates the check engine light. Common EVAP codes on this generation TL include:

• P0442 — Small EVAP leak detected
• P0455 — Large EVAP leak detected
• P0456 — Very small EVAP leak detected
• P0496 — EVAP flow during non-purge condition

Fixing the underlying cause doesn't immediately clear the code. The Powertrain Control Module (PCM) needs to confirm the repair by running its own diagnostic self-test — called a readiness monitor — under specific driving conditions.

Two Ways to Clear an EVAP DTC

1. Use an OBD-II Scanner to Erase the Code

The most direct method is connecting an OBD-II scanner to the diagnostic port (located under the dash on the driver's side) and using the "clear codes" or "erase DTCs" function. This immediately:

• Turns off the check engine light
• Clears the stored fault code
• Resets all readiness monitors to "not ready"

That last point matters enormously if you're heading toward an emissions inspection. Most states require readiness monitors to show "complete" before a vehicle will pass. Immediately after clearing codes, your TL's monitors will be incomplete, and the car may fail a smog check — even if the repair was successful.

2. Let the PCM Clear It Automatically

If the EVAP system runs its self-test and finds no fault on two consecutive drive cycles, it will automatically extinguish the check engine light and mark the EVAP monitor as complete. This takes longer but avoids the readiness monitor reset problem if you haven't already cleared codes manually.

Running the EVAP Readiness Monitor on a 2009 Acura TL

After clearing codes (or after a repair), the PCM needs to complete its EVAP monitor. This system is notoriously particular. Honda/Acura vehicles of this era typically require a specific set of conditions:

There is no single "magic drive cycle" that works every time. Honda publishes a specific EVAP monitor drive cycle procedure — some technicians follow it precisely using a scan tool to watch the monitor status in real time. Others use a general-purpose drive cycle and check back after a day or two of normal driving.

🔧 A live-data capable scan tool is genuinely useful here. It lets you watch whether the EVAP monitor moves from "not ready" to "complete" without guessing.

What Can Prevent the Monitor From Completing

Even after a legitimate repair, several things can prevent the EVAP monitor from running:

• Fuel level outside the acceptable range — too full or too low
• Engine not fully cold at start — partial warm-up doesn't satisfy the cold-soak requirement
• Other pending DTCs — some monitors won't run if another fault is present
• Incomplete repair — a second small leak, deteriorated hose, or faulty solenoid the original diagnosis missed

If the monitor keeps aborting or the code returns after clearing, that's meaningful diagnostic information — not just a glitch. It often points to a repair that didn't fully resolve the fault, or a second fault that wasn't addressed.

The Emissions Test Timing Problem ⚠️

This is where many TL owners get caught off guard. If you clear the codes and immediately go for an emissions test, the incomplete EVAP monitor will likely cause an automatic failure in states that check OBD-II readiness status — which includes most states with emissions programs.

The general guidance is to drive a complete cycle (or multiple cycles) and confirm the EVAP monitor reads "ready" before presenting the vehicle for inspection. How many drive cycles that takes varies based on conditions, driving patterns, and whether the underlying repair was fully successful.

What Shapes the Outcome for Each Owner

How this process plays out depends heavily on:

• Whether the root cause was actually fixed — a cleared code on an unresolved leak will return
• Your driving patterns — short trips, extreme temperatures, and frequent refueling affect monitor completion
• Your state's emissions rules — some states allow one or two incomplete monitors; others don't
• Your scan tool — a basic code reader clears codes but can't monitor readiness status in real time; a more capable tool gives you visibility into what the PCM is doing

The 2009 Acura TL's EVAP system is functional and well-understood, but the path from "repair done" to "monitor complete and code stays gone" depends on variables specific to your vehicle, your climate, your driving, and your state's inspection requirements.