Engine Warning Light: What It Means and What to Do

Amber, red, steady or flashing

Dashboard lights follow a loose colour code. Amber or orange generally means a fault has been logged and needs attention soon. Red generally means something serious or safety-related, such as low oil pressure, a brake system fault or an overheating engine. If a red light comes on while you are driving, find a safe place to stop and switch off rather than pressing on to see how far you get.

Behaviour matters as much as colour. A steady amber engine light usually means the engine-management system has stored a fault but the car is still running acceptably. A flashing engine light is different. It often points to a misfire, where fuel is being burnt unevenly or not at all, and unburnt fuel can overheat and damage the catalytic converter. If it flashes, ease off the throttle, avoid hard acceleration and get the car looked at promptly.

• Steady amber: book a diagnostic check soon and keep an eye on how the car drives.
• Flashing amber: reduce load and speed and have it checked as a priority.
• Red: stop safely and do not continue driving until the cause is known.
• Light that comes and goes: still worth checking, as the fault code stays stored.

Why a fault code is only the starting point

When the light comes on, the engine control unit stores a fault code. A diagnostic reader can pull that code out in seconds, and plenty of people buy a cheap reader for exactly that reason. The trouble is that a code describes the symptom the computer noticed, not necessarily the broken part.

A code pointing at a lean mixture, for example, might be caused by a failing sensor, a split vacuum hose, an air leak after the meter, or a fuel delivery problem. Replacing the part named in the code is a common way to spend money and still have the light return. Proper engine-management diagnostics means reading the codes, looking at live data from the sensors, and testing the suspect circuit before anything is replaced.

Common causes behind the light

The causes range widely, which is why guessing is unwise. Some of the usual suspects are oxygen sensors, mass airflow sensors, ignition coils and spark plugs, EGR valves, and diesel particulate filters that have become clogged by too many short trips. Wiring faults and corroded connectors can also trigger codes when the part itself is perfectly healthy.

Sometimes the light follows a simple event. A fuel cap that was not tightened after filling can set an evaporative emissions code. A flat or weak battery can cause odd electrical behaviour and several unrelated lights at once, which is worth ruling out early.

Can you keep driving with the light on?

It depends on the colour, the behaviour and how the car feels. If the light is steady and the car drives normally, a short, gentle journey to a garage is usually reasonable. If the car is hesitating, losing power, running roughly, smelling of fuel, or the light is flashing, the safer choice is to stop and arrange for it to be checked, or recovered if necessary.

Many modern cars drop into a reduced-power mode, sometimes called limp mode, to protect the engine. That is a deliberate safety response, not a sign the car has fixed itself. Treat it as a request to get the fault diagnosed rather than something to work around.

Warning lights and your MOT

Warning lights can matter at MOT time. As far as we are aware, an engine management light that stays on is something testers are expected to record as a defect, and certain other warning lights, such as those for the airbags or braking system, are treated seriously too. The rules are updated from time to time, so check the current MOT guidance if you are unsure how a particular light is classed.

The practical point is simple: fix the cause before the test rather than hoping the light behaves on the day. Clearing the code with a reader without fixing the fault only delays the problem, because the car will usually relog it after a short time on the road.

Frequently asked questions