The Check Engine Light Does Not Tell You What Is Broken

The most expensive misunderstanding in car ownership is the belief that a trouble code names a failed part. It does not.

What a code actually is

A diagnostic trouble code records that a monitored value went outside its expected range. It identifies the circuit or the system that reported it. It does not identify the cause.

A code for an oxygen sensor circuit, for example, can be caused by the sensor, by its wiring, by a connector, by an exhaust leak upstream of it, or by a genuine fuelling problem the sensor is correctly reporting. Replacing the sensor addresses one of five possibilities.

Why free code reading is not diagnosis

A parts store scan gives you the code. That is a starting point, and it is worth having. What it is not is a diagnosis, and the gap between the two is where people spend money on parts that did not need replacing.

Steady light versus flashing

• Steady — a fault has been recorded. Get it looked at reasonably soon, but it is generally not an emergency.
• Flashing — an active misfire severe enough to damage the catalytic converter. Reduce load, avoid high speed, and get it dealt with promptly. This one is genuinely urgent.
• Light on with drivability symptoms — treat as more urgent than the light alone.
• Light on with no symptoms — still worth diagnosing, because it will also fail an emissions test and it may be masking a second fault.

Things that turn it on that are not expensive

A loose or failed fuel cap is a genuinely common cause of an evaporative system code. So is a cracked vacuum hose. Neither is expensive and both produce a light that looks alarming.

What to tell a mechanic

The symptom, not your diagnosis. When it happens, what the vehicle was doing, whether anything changed recently, and what work has been done. That is more useful than a code number on its own.