Which OBD2 Codes Fail Inspection (And Why Clearing Them Fails Too)

An imported car sits on your driveway. You have a registration appointment and an inspection slot booked for next week, the seller handed it over with a spotless dashboard, and the check engine light is off. You also watched the light flicker once during the test drive before it went dark again, which is the detail that should worry you. Somebody switched that light off, and switching it off is not the same as fixing what turned it on.

If the fault behind it was an emissions code, the car you are about to present for inspection will most likely fail. Worse, the act of clearing it has probably set up a second, independent reason to fail.

Which OBD2 codes fail an emissions inspection?

Two different things fail you. The first is any emissions-related code that keeps the malfunction indicator lamp (the check engine light) on. Inspection stations treat an illuminated MIL as an automatic fail, no matter how minor the code looks, because the lamp is the car's own declaration that an emissions system is not working. The second is incomplete readiness, covered further down.

The code families that fail an inspection most often:

• Catalyst efficiency: P0420 (bank 1) and P0430 (bank 2). These say the catalytic converter is no longer cleaning the exhaust well enough. A genuine P0420 is one of the most common single-code fails on a higher-mileage petrol car.
• Fuel system: P0171 (too lean, bank 1), P0172 (too rich), and P0174 (too lean, bank 2). A car running far off its target mixture is also producing emissions outside spec.
• Misfire: P0300 (random) through P0306 (cylinder-specific). A misfiring cylinder dumps unburned fuel into the exhaust and can wreck the catalyst, so the test treats it seriously.
• EVAP leak: P0442 (small leak), P0455 (large leak), and P0446 (vent control). These are evaporative emissions faults, raw fuel vapour escaping rather than being captured.
• EGR flow: P0401 (insufficient flow). Exhaust gas recirculation is an emissions-control device in its own right, so a flow fault fails the test.

Codes that do not light the check engine light, such as many ABS, airbag, or comfort-system faults, do not fail an emissions inspection. They may still fail a separate safety inspection, which is a different part of the same visit in most countries. If you are buying the car to drive home and register, work through the full check engine light guide so you know which lit lamp means what before you commit.

Why does clearing codes before inspection not work?

This is the part sellers get wrong, and the part that protects you as a buyer. Clearing the codes does switch the light off. It also wipes every readiness monitor back to "incomplete" in the same operation, and that second effect is the one that fails the car.

Readiness monitors are the self-tests the engine computer runs on each emissions system: catalyst, oxygen sensor, oxygen sensor heater, EVAP, EGR, and the rest. Each one only reports "complete" after the car has driven through the specific conditions that monitor needs. Clear the codes and all of them drop back to incomplete at once. They do not refill instantly. Depending on the car and how it is driven, a full set can take anywhere from 50 to 150 km of varied driving to finish.

Inspection stations know this, and the rule is deliberately strict. On vehicles from model year 2001 onward, more than one incomplete monitor is an automatic fail. (Older 1996 to 2000 cars are allowed two.) So the seller who cleared the light an hour before the viewing has not hidden the fault. They have swapped a code fail for a readiness fail, and the inspector sees a freshly reset car that has obviously had its memory wiped. The detailed mechanics of this, and why all eight monitors sitting at incomplete on a high-mileage car is the single loudest tell, are in the recently cleared codes and readiness monitors guide.

There is a slower failure too. If the underlying fault is real, it comes back. A worn catalyst that earned a P0420 will earn it again once the catalyst monitor runs, usually within that same 50 to 150 km. Clearing the code resets the countdown; it does not stop the clock.

How long after clearing codes can you pass emissions?

There is no fixed number of hours, because monitors complete on driving conditions, not elapsed time. The catalyst monitor wants a stretch of steady cruising at constant speed. The EVAP monitor wants a cool start with the fuel tank somewhere between roughly 15 and 85 percent full. The oxygen sensor monitor wants a mix of town and faster road driving. Hit those conditions and the monitors set; sit in traffic for an hour and they may not.

For a healthy car with no real fault, plan on 50 to 150 km of mixed driving after any code clear before the monitors are complete enough to pass. For a car with a genuine emissions fault, the honest answer is that it never passes cleanly, because the fault reappears and relights the lamp before the monitors finish. Clearing the code only delays the inevitable, and it leaves the readiness gap open in the meantime.

This is exactly why the trick fails on an imported car. A seller can clear the light the morning of the viewing, and the dashboard looks perfect for the test drive. By inspection day a week later you have driven it, the monitors have started to set, and either they are still incomplete (readiness fail) or the original fault has returned (MIL fail). The dark dashboard at handover bought a few quiet days, nothing more.

Before you wire the money, you want to know whether that clean dashboard is real or freshly cleared. The Skanyx app runs the full 8-step Pre-Purchase Inspection (initial code scan, idle 90s, cruise 60s, acceleration 45s, final scan, fraud detection including recently cleared codes and incomplete readiness monitors, multi-specialist analysis) and produces a Buy / Negotiate / Caution / Walk Away verdict with a PDF and negotiation script. Run it on the car before you commit

What is a permanent code and why can't a scan tool clear it?

There is a category of code that makes the whole clearing game pointless on newer cars. A permanent diagnostic trouble code, or PDTC, is an emissions fault the car copies into protected memory the moment it confirms it. Cars built from roughly 2010 onward set these alongside the normal stored code.

A scan tool cannot erase a permanent code. Disconnecting the battery does not touch it either. The only way a PDTC clears is for the car itself to remove it, and it only does that after the actual fault is fixed and the relevant monitor has run again without finding the problem. In other words, the car has to prove to itself that the fault is gone before it lets go of the record.

Permanent codes exist precisely to stop pre-inspection clearing. Many inspection stations read the permanent-code memory specifically, and a permanent P0420 sitting there after the seller swears the car is fault-free tells the inspector, and tells you, that the catalyst issue is real and recent. On a 2010-or-newer car, "I just cleared it, give it a few days" is not an option the seller has, whether they understand that or not.

What does the OBD2 scan actually show, and not show?

A generic OBD2 scan with any ELM327 adapter and an app like Skanyx reads exactly the data the inspection regime cares about, which is what makes it the right pre-purchase tool. You get stored fault codes (Mode 03) and pending codes (the early-warning ones the car has seen once but not yet confirmed), the freeze frame data attached to each stored code, and the full readiness monitor status (Mode 01). That covers both ways a car can fail: the code that lights the lamp, and the incomplete monitors that betray a recent clear. On cars new enough to use them, the scan also surfaces permanent codes.

What a generic OBD2 scan does not give you is the pass-or-fail tailpipe gas reading itself. Inspection stations that sniff the exhaust directly (a tailpipe probe measuring CO, HC, and NOx) are taking a physical measurement no OBD2 tool reproduces, and a borderline-but-not-coded emissions problem can in principle slip past the code scan and still fail the sniffer, or the reverse. For that confirmation you need the inspection itself or a workshop emissions bench, typically 30 to 50 euros. The OBD2 scan tells you whether the car will fail on codes and readiness, which is where the overwhelming majority of imported-car failures actually happen; the sniffer is the backstop the station runs anyway.

The practical takeaway: the scan reads the same code and readiness data the inspector reads, so you can sit in the seller's driveway and see the result before they do.

The buyer's workflow before you commit

Run this in order, during or right after the test drive, with your own adapter plugged in.

1. Read stored and pending codes. Note every code. A single aged P0420 on a 200,000 km petrol car is one conversation; a P0420 next to a P0171 and a misfire code is a car with an active fault feeding the catalyst, which is another conversation entirely. Cross-check anything you are unsure about against the check engine light guide.
2. Check readiness monitor status. If a high-mileage car shows most or all monitors incomplete and a spotless dashboard, the codes were cleared recently. That is a readiness fail waiting to happen and a reason to slow the deal down.
3. Look for permanent codes on a 2010-or-newer car. A permanent code the seller cannot explain is an emissions fault they cannot clear away.
4. Decide whether it is even legal to register where you live. A car that fails your local emissions test is a car you cannot put on the road until it is fixed, and on an import the repair lands on you.

Different regimes weight these differently. In Germany, the HU/AU inspection (the TÜV or DEKRA test) fails an illuminated check engine light outright, and the AU emissions portion reads OBD data. In Spain, the ITV runs an OBD2 scan and fails an active MIL or incomplete readiness. In Lithuania, the techninė apžiūra (TA) includes the on-board diagnostics check and applies the same readiness logic. In Poland, the SKP przegląd techniczny fails any active check engine light and, on diesels registered from 2009, also looks for the physical particulate filter. Knowing which gate your country uses tells you whether a cleared code is a delay tactic or a dead end.

Once you have the data, it turns into money. A stored P0420 on a car the seller called fault-free is a known repair cost you can subtract from the asking price, the same way the negotiate with OBD2 evidence playbook treats every other stored code. The wider import checklist, including the diesel-specific traps, lives in the German used car OBD2 checklist.

Is it safe to drive a car that would fail inspection?

A car that fails on a P0420 or an EVAP leak is usually drivable in the short term; the emissions are out of spec but the car runs. A car failing on an active misfire is a different matter, because a misfire can damage the catalyst quickly and points to a fault you want diagnosed before any distance is covered. If you are weighing whether to drive an imported car home before fixing it, the is it safe to drive with the check engine light on guide separates the codes you can nurse from the ones you cannot.

What this means before you hand over the money

A switched-off check engine light on an imported car tells you nothing on its own, and a freshly cleared one tells you something is being hidden. Read the codes and the readiness monitors yourself before you commit: if the monitors are wiped clean or a permanent code is sitting in memory, the car will fail inspection no matter how dark the dashboard looks today. Clearing a code is a stall, not a repair, and the inspection station is built to see straight through it.

---

Skanyx is built by people who actually own, drive, and import the cars we write about, including high-mileage EU diesels and petrol cars bought sight-unseen from German auction portals. Editorial reflects that.