
THE SHORT ANSWER
Treat the code as the name of a failed test and the lamp as the severity gauge. Steady means a confirmed fault that needs diagnosis. Blinking once per second means misfire is happening right now at a level that can damage the catalytic converter, so ease off and get the car looked at promptly. Codes stored behind a lamp that is off do not fail an OBD emissions inspection.
- Coverage
- Gasoline cars from model year 1996, diesels from 1997
- Lamp states
- Off, steady, or blinking once per second
- Lamp off, codes stored
- Still passes the OBD inspection
- California, April 2026
- 8.40% failed the initial Smog Check test
A code records a failed test, not a failed part
The engine computer runs self-checks all day. Each one compares a measurement against a limit, and a reading outside that limit gets stored as a diagnostic trouble code. The code identifies the check and stops there. The part behind the failure goes unnamed, and the part you end up replacing is often a different one.
Take P0420, a catalyst efficiency code. The computer reaches it by comparing signals from two oxygen sensors, one ahead of the catalytic converter and one behind it. A worn-out converter produces that result. So does a tired sensor, an exhaust leak upstream, or a long-running misfire that has been sending raw fuel into the converter. The computer sees two voltages and applies a rule, so it cannot separate those causes.
Federal law gives the system three duties: detect emission-control malfunctions, store a code for each, and alert the driver. Diagnosing is not on the list. The system polices the tailpipe, so a worn wheel bearing, a slipping clutch or a leaking shock sets no code at all. A silent code memory does not mean the car is sound.
Who writes the OBD2 rule, and which cars it covers
The federal onboard diagnostics section for newer model years, 40 CFR 86.1806-17, is thin on engineering detail. Its operative paragraph points manufacturers to California's 2013 OBD rules, found in section 1968.2 of California's Title 13 regulations and pulled into federal law by reference. So the document deciding what your car must monitor, and how its lamp must behave, is a California Air Resources Board regulation that anyone can read.
Coverage is no longer a live question. CARB says every gasoline or alternate-fuel passenger car and truck from model year 1996 on has to carry OBD II, and diesels join from 1997. That is 31 model years. Inspection rules draw the same 1996 line: under 40 CFR 85.2207, a 1996 or newer vehicle with a missing diagnostic connector fails the OBD test.
Reading a code from the left, one character at a time
A code is a letter plus four digits. Reading order matters, because each character narrows the one before it.
- The letter picks the system family. P is powertrain, the only family an emissions inspection cares about. B, C and U cover systems outside the powertrain.
- The second character says who defined the code. A zero means the SAE standard fixed the meaning, so it reads identically on every brand. A one means the manufacturer wrote it. Twos and threes exist too.
- The third character groups the fault by area, such as fuel and air metering, ignition, emission controls, idle speed or the transmission.
- The final pair pins down the exact fault inside that area. It is what tells cylinder one's misfire apart from cylinder four's.
Read from the left. The letter tells you whether an inspector would care. The second character shows whether a basic scan tool can interpret the code at all. Only then does the exact fault matter.
Generic does not stop at P0, and the chart behind it is paywalled
Most explainers say P0 codes are generic and P1 codes belong to the manufacturer. That is half right. California's rule tells makers to use SAE-defined codes whenever possible and gives P0xxx and P2xxx as its examples. It allows maker-defined codes, with P1xxx as the example, only with regulator approval. A P2 code is as standardized as a P0 code, so an inexpensive reader can usually explain it on any make.
| Range | Status |
|---|---|
| P0xxx | Defined by SAE, same meaning on every make |
| P1xxx | Defined by the maker, allowed only with approval |
| P2xxx | Also SAE-defined, though often mislabeled as maker-specific |
The letter and subsystem maps come from SAE J2012, which the California rule names and requires but never reproduces. SAE and ISO sell their standards. No government text spells out the letter meanings or the third-character map, so the charts on thousands of sites trace back to copying. They are probably accurate, yet nobody can check them against a public source. Use a chart as a starting point, then check the specific code against the manufacturer's service data before ordering parts.
The lamp is where severity lives
The rule never sorts codes into urgent and routine. It sorts the lamp, and the lamp has three states.
| Lamp | What it tells you |
|---|---|
| Off | No confirmed fault is commanding the lamp right now. Stored codes can remain, and a pending fault is possible. |
| Steady | A fault is confirmed and the lamp is commanded on. It needs diagnosis, and the regulation sets no deadline. |
| Blinking once per second | Engine misfire has reached a level tied to catalyst damage. The rule writes this out as its own requirement. |
No row mentions which code is stored. P0301 and P0442 behind a steady lamp carry the same message about urgency: confirmed, needs attention, not an emergency. A misfire code behind a blinking lamp, though, means something different from the same code behind a steady one. That makes "which codes are serious" the wrong question, and any ranked list answering it is an opinion.
The blinking lamp is the one regulated warning
California's rule has the lamp blink once per second for as long as misfire is occurring, beginning right after a pending misfire code is stored. After a confirmed code is stored, it keeps blinking while the misfire lasts and turns steady if the misfire stops. Two things follow. The blink reports misfire as it happens; it is not a saved condition. And a blink that settles into a steady glow does not mean the problem went away, because the fault is still on record.
The reason is raw fuel reaching the catalytic converter. The rule excuses cars that cut fuel and fall back on default fueling during catalyst-damaging misfire, since those cars protect the converter themselves. CARB tells drivers that a flashing lamp points to a fault that may be harming the converter.
What the rule does not say
Nothing in the regulation orders you to stop driving. CARB's consumer advice is that driving a long time without a fix could damage other components. Easing off and booking a shop promptly is a sensible reading, but that is judgment, not a legal command.
Pending, confirmed, and why the light lags the symptom
A pending code is stored the first time a monitor fails. It is a suspicion. For most faults the computer waits for the same test to fail again on a later drive before it lights the lamp, and that second failure makes the code confirmed. The two-strike design keeps one odd reading, such as a tank of bad fuel or a cold-start quirk, from lighting the dash.
Misfire is the exception. As the blink rule shows, the blinking begins right after the pending code, with no wait for a second opinion, because a converter can be ruined quickly. For anyone holding a scan tool, pending codes behind a dark lamp are real information, just unconfirmed. They show what may light the lamp soon, and on a car you might buy they are often the most useful lines on the screen.
Codes in memory do not fail an emissions inspection
An OBD inspection does not read the code memory and hand down a verdict. Under 40 CFR 85.2222, if the lamp is not commanded on, the car passes, even with codes stored. If the lamp is commanded on, the test system pulls the codes behind it and the car fails. A different paragraph of the same section covers monitors still waiting to complete their runs, a separate problem.
California publishes monthly Smog Check results, which gives a sense of scale. For April 2026, the program counted 948,066 initial tests, with 79,649 of them failing, an initial failure rate of 8.40%. Adding retests, 1,026,118 tests produced 91,385 failures, or 8.91%. Put differently, 91.6% of cars passed on the first attempt. The average repair cost recorded for the month was $776.16, though the Bureau of Automotive Repair cautions that parts of its repair data are incomplete, so read that as a rough marker, not a bill to expect.
Plugging a reader into a car you do not own yet
The code memory is one of the few places where a used car speaks for itself instead of through its seller. When a seller reports that it passed emissions, that proves a dark lamp on test day and nothing about stored, pending or historical codes. A basic reader on a test drive shows more:
- Whether the lamp is lit at this moment, the single thing a test lane asks.
- Which confirmed codes are stored: subsystems that have already failed a check twice.
- Which pending codes are present: faults that have failed once.
- Whether the codes match the age, mileage and story you were given.
- Whether the codes bunch in one subsystem, a sign of one shared cause.
An empty memory on an older, high-mileage car deserves a second look rather than relief. Disconnecting the battery or clearing codes wipes the memory, and the monitors then need time to run again before the car can be tested. Codes describe only the computer's present state, and a computer can be reset. A vehicle history report works from events reported to outside parties, such as title brands, accident and salvage records and odometer readings, which a reset cannot erase. A buyer wants both.
Where this information comes from
- eCFR: 40 CFR 85.2222, inspection program requirements — Backs the point that a car with codes stored but a dark lamp passes the OBD inspection, and that a lit lamp triggers the code check.
- eCFR: 40 CFR 85.2207, OBD test procedures — Source for the 1996 model-year line and for failing a car whose diagnostic connector is missing.
- eCFR: 40 CFR 86.1806-17, onboard diagnostics — Shows the detect, store and alert duties and the hand-off to California's OBD rules.
- California Air Resources Board: Title 13 CCR 1968.2, OBD II regulation — Where the misfire blink, the fuel shutoff exemption and the SAE-defined versus maker-defined fault code language are written down.
- California Bureau of Automotive Repair: Smog Check executive summary, April 2026 — Monthly test counts, failure rates and the average repair cost used for the scale check.
Sources and photos: Facts checked against the sources above in October 2026. Photo by Erik Andersson on Unsplash; diagrams by YourVINHistory.
Keep reading
- Was the light cleared?What a code reset leaves behind, and why an empty memory can be a finding.
- Pre-purchase inspectionA scan tool shows only what the computer logged, so see what a shop adds.
- Smog check historyEmissions test results are kept on a record, and sellers seldom bring them up.
- TSB vs recallA known fault may already have a documented fix, but only one kind is owed to you.
Frequently asked questions
Is it safe to drive with the check engine light on?
With a steady lamp the regulation sets no urgency, though a confirmed fault is still a fault worth diagnosing soon. With a blinking lamp, misfire is happening now and may be harming the catalytic converter, so reduce engine load and have the car checked promptly rather than at your convenience.
Does a stored code mean my car will fail smog?
Not by itself. In an OBD inspection the lamp decides the result: dark means pass even with codes in memory, lit means the test system collects the codes and the car fails. Monitors that have not finished running fall under separate rules, so a freshly cleared car can still be turned away.
What is the most common OBD2 code?
No public agency publishes how often each code appears. Rankings online come from commercial repair-data companies, and their samples are vehicles that went to a shop, not vehicles on the road. They may be sound, but they are not open data, so treat a top-ten list as a rough guide.
Does my used car have OBD2?
Almost certainly. CARB requires it on passenger vehicles from model year 1996 if they run on gasoline or an alternate fuel, and from 1997 if they are diesels. If a 1996 or newer vehicle is missing its diagnostic connector, it fails the OBD test outright.
Is a maintenance reminder the same as the check engine light?
No. The check engine lamp is a warning built around emissions, defined in regulation and tied to stored codes. A maintenance reminder runs off a mileage or time counter the manufacturer picked, carries no regulatory meaning and stores no trouble code. Resetting the reminder does nothing to the code memory.
Now check the car itself
The guide explains what to look for. The report shows what this VIN has on record.