Permanent trouble codes are protected copies of confirmed emissions faults that your car’s computer keeps even after someone clears codes with a scan tool. They exist so that a fault cannot simply be erased and forgotten, and they disappear only when the vehicle proves to itself that the problem is gone.
Many owners first meet permanent codes when a car fails an inspection despite having no visible stored codes. This article explains the idea behind them, how they behave, and why they matter for anyone who maintains a modern car. A separate guide covers the step-by-step process for diagnosing one.
A Record Designed to Survive the Clear Button
On-board diagnostics, generation two (OBD-II), has always let technicians clear codes after a repair. That convenience created a loophole. A driver could clear codes just before an emissions test and present a car with no faults recorded, even though the underlying problem was still present.
Readiness monitors, the self-tests that show whether each system has been checked since the last clear, closed part of that loophole. A freshly cleared car shows incomplete monitors. Permanent codes add a second layer by keeping the fault itself visible until the vehicle confirms the repair.
Permanent code support was phased in on newer vehicles, so many early OBD-II cars do not report them at all. If your scan tool shows no permanent code screen, or reports that the service is not supported, the vehicle may simply predate the requirement.
How Permanent Codes Are Created
A permanent code begins as an ordinary fault. A monitor fails, the computer stores a pending code, and if the fault repeats under the required conditions, the code becomes confirmed. For emissions-related faults, the confirmed code also turns on the check engine light.
At that point, a copy of the confirmed code is written into a separate protected memory area. That copy is the permanent code. It carries the same five-character code, such as P0420 for catalyst efficiency below threshold on bank 1, but it follows different rules for removal.
Not every code becomes permanent. Permanent codes are tied to emissions-related faults that command the check engine light on. Pending codes, codes from body or chassis modules, and many manufacturer-specific codes that do not light the lamp are not copied into permanent memory.
How Permanent Codes Differ From Other Code Types
A scan tool may show the same code in up to three lists. Each list answers a different question about the fault, and reading them together gives a clearer picture than any single list.
Pending Codes Show What Was Just Seen
A pending code means a monitor detected a fault during the current or last completed drive cycle but has not yet confirmed it. Pending codes are temporary, can fade on their own and are erased when codes are cleared.
They are useful early warnings and fast feedback after a repair, but they carry no special protection in memory.
Confirmed Codes Show What Was Verified
A confirmed, or stored, code means the fault was verified and, for emissions faults, the lamp was commanded on. It is read through Service $03 and removed by clearing codes through Service $04, or by aging out after the fault stops.
Confirmed codes come with freeze frame data, a snapshot of conditions when the fault was recorded.
Permanent Codes Show What Is Still Unproven
A permanent code means the vehicle has not yet confirmed that the fault is fixed. It is read through Service $0A, often called Mode 10, and it cannot be erased with a scan tool or by disconnecting the battery.
Its job is to stay visible until the vehicle itself verifies the repair.
How the Vehicle Clears a Permanent Code
Because a scan tool cannot erase it, a permanent code must be cleared by the vehicle. The general principle is simple: the monitor that originally detected the fault must run again and pass, showing the problem no longer exists.
If the check engine light was still on at the time of repair, the computer usually needs the monitor to pass on enough consecutive trips to turn the lamp off, and the permanent code clears with it. If codes were cleared with a scan tool after the repair, the vehicle usually needs one full passing run of that monitor.
The exact rules, trip counts and driving conditions depend on the monitor and the manufacturer. Some monitors run quickly, while others, such as catalyst or evaporative system monitors, need specific conditions. The service manual describes the enabling conditions for your vehicle.
Why a Permanent Code Might Stay After a Repair
A permanent code that remains after a repair is frustrating, but it usually has an explanation. Before assuming the scan tool is wrong, consider the most common reasons.
- The related monitor has not run yet because its enabling conditions have not been met during normal driving.
- The repair did not fix the root cause, so the monitor keeps failing and the code stays.
- A second, related fault is now causing the same monitor to fail.
- Codes were cleared repeatedly, restarting the process before the monitor could complete.
Check readiness status and the pending code list. An incomplete monitor means you need more driving. A returning pending code with the same definition means the problem is still present and needs further testing before more parts are replaced.
Permanent Codes and Emissions Inspections
Permanent codes matter most during plug-in OBD inspections. Some state programs fail a vehicle that reports a permanent code, even if the check engine light is off and no stored codes appear. This prevents a freshly cleared car from passing while the fault remains unverified.
Inspection rules vary by state, including which model years are tested and how permanent codes are treated. Your state emissions program website or office is the authoritative source. A licensed inspection station can also explain the local requirements before you test.
Never try to work around a permanent code. Clearing codes, disconnecting the battery or swapping control modules does not remove the record in a legitimate way. The correct path is to repair the fault and let the vehicle complete its monitors through normal driving.
What Permanent Codes Reveal About Vehicle History
When you shop for a used vehicle, a permanent code can reveal more than a quick visual check. A car with no stored codes but a permanent code and several incomplete monitors may have had its codes cleared recently, possibly with an unresolved fault.
That does not prove anything dishonest. A recent battery replacement or repair also resets monitors. It does mean you should ask questions and, ideally, arrange a pre-purchase inspection by a qualified technician who can review the full code and readiness picture.
For owners, permanent codes also act as an honest reminder. If one lingers for weeks, it shows that a monitor has either not run or keeps failing, which is information worth acting on before the next inspection date arrives.
Practical Habits for Living With Permanent Codes
Permanent codes require a little patience, but a few habits make them easier to manage and prevent wasted effort.
- Record all codes, freeze frame data and readiness status before any repair or clearing.
- Fix the cause, then avoid clearing codes again unless a technician advises it.
- Drive normally, including a cold start, city driving and steady highway cruising, so monitors can run.
- Recheck permanent codes and readiness after several days of normal driving.
Keep safety in mind while doing this. Do not watch the scan tool while driving. Check status after parking, or have a passenger read the screen. Run the engine only outdoors or with good ventilation when testing at home.
When Permanent Codes Point to Professional Help
Some permanent codes clear easily after a straightforward repair. Others resist because the root cause is hard to find, such as an intermittent wiring fault or a problem that only appears under specific load or temperature conditions.
If a permanent code persists after you have repaired the obvious cause and driven enough for the monitor to run, a qualified technician can help. Professional scan tools can show monitor test results, manufacturer data and specific enabling conditions that generic tools may not display.
Bring your notes: the original code, freeze frame data, what was repaired, and when codes were cleared. This history saves diagnostic time and helps the technician decide whether the monitor has not run or is still failing.
Keeping Permanent Codes From Becoming a Surprise
Permanent trouble codes are easiest to handle when you know they exist before an inspection does. Checking the permanent code screen alongside stored codes and readiness status gives you an accurate view of what the car is still trying to verify.
Plan repairs well before inspection deadlines so the vehicle has time to complete its monitors. A repair made the day before a test may be correct, but the permanent code may not clear in time, and rushing usually leads to repeat visits.
Treat a permanent code as an open question the car is still asking: has this fault really been fixed? Answer it with proper testing, a sound repair and normal driving, and the code will clear on its own when the vehicle has the proof it needs.