Skip to content Skip to footer

A steady check engine light on the dashboard means drive carefully to a garage within a few days. A flashing one means stop as soon as it is safe, because flashing signals a misfire severe enough to destroy the catalytic converter within minutes. Either way the car has stored a fault code, so the answer is a diagnostic read rather than guesswork. A lamp indicating a malfunction is also a Major MOT defect under defect 8.2.2.2(g), which is a straight fail.

What the light is doing tells you the urgency:

  • Steady amber: drive carefully, book it in
  • Flashing amber: stop as soon as safe
  • Light plus red warning: stop immediately
  • Light plus limp mode: recover rather than drive

Steady or Flashing?

This is the only distinction that matters in the first thirty seconds.

Steady. The engine management system has logged a fault outside its normal parameters. The car is usually driveable, performance may be slightly reduced, and the problem will not generally worsen in the next few miles.

Flashing. A misfire is dumping unburnt fuel into the exhaust. That fuel ignites in the catalytic converter and can melt the substrate, turning a cheap ignition fault into an expensive one. Pull over when it is safe and arrange recovery.

A flashing light is the one case where continuing to drive reliably makes the bill larger. Where it has already happened, a damaged catalytic converter is a far bigger job than the coil or plug that caused it.

Check These Before Booking Anything

Three causes are free to rule out and account for a fair share of lit lights.

  • The fuel cap. A loose or poorly seated cap triggers an evaporative emissions fault. Remove it, check the seal is clean and undamaged, refit until it clicks, then drive for a few journeys.
  • The fuel you just put in. Misfuelling or contaminated fuel can set a code. If the light appeared immediately after filling up, that is the suspect.
  • A recent jump start or battery change. Momentary voltage irregularities can log codes that are not real faults.

If the light clears by itself over several drive cycles, the fault has not recurred. If it returns, it is real.

What Usually Causes It

Most lit lights trace back to a short list, and several are cheap if caught early.

Oxygen or lambda sensor. Reports exhaust gas composition to the ECU. A lazy or failed sensor raises fuel consumption and emissions, and left alone it damages the catalytic converter by running the engine rich.

Ignition faults. Worn spark plugs, failed coils or coil packs. These are the usual cause of a flashing light.

Mass airflow sensor. Gives the ECU the wrong air reading, producing hesitation, poor starting and rough idle.

Catalytic converter efficiency. Often a consequence of one of the faults above rather than a primary failure.

EGR valve. Sticking or clogged with carbon, causing rough running, poor economy and sometimes a lit light with no obvious symptom.

DPF on a diesel. Repeated short journeys prevent the filter regenerating, so soot accumulates until the system flags it. A DPF clean is cheaper than a replacement filter, but only while the blockage is still clearable.

Carbon build-up on intake valves and ports, particularly on direct-injection petrol engines and modern diesels. Carbon cleaning addresses the cause rather than clearing the code and waiting for it to return.

Why You Cannot Diagnose It by the Light

The lamp is one bulb reporting hundreds of possible faults, which is why guessing is expensive.

The ECU stores a specific fault code, and reading it takes minutes. Without that code you are replacing parts in sequence and hoping, which is how a £40 sensor becomes a £400 afternoon.

Worth knowing: a code names the circuit reporting a problem, not always the part that has failed. A code pointing at a lambda sensor can be caused by an exhaust leak upstream of it, and replacing the sensor changes nothing. That is the difference between reading a code and interpreting it, and why an EML diagnostic involves live data rather than a code reader alone.

Where several codes are stored, engine diagnostics establishes which is the cause and which are consequences.

Do Not Just Clear the Code

Tempting, and it achieves nothing useful.

Clearing a code switches the light off without fixing anything. The fault returns once the system next runs the relevant monitor, usually within a few drives.

It also causes a specific problem at MOT. Clearing codes resets the readiness monitors, and a car presented before those monitors have completed can be rejected on that basis. So clearing the light the morning of the test is a worse strategy than fixing the fault.

Limp Mode

Sometimes the light comes with a hard restriction on performance.

Limp mode caps revs and power to protect the engine or transmission, typically holding the car to a low speed and refusing to change up. It is a protective measure, not a fault in itself.

If the car enters limp mode, do not try to drive it home across the county. Get it off the road and arrange recovery or a short careful journey to a garage. Continuing in limp mode on a motorway is a hazard in its own right because you cannot maintain traffic speed.

When to Stop Immediately

The engine light on its own is amber. Some combinations are not.

  • Flashing engine light. Stop as soon as it is safe.
  • Engine light plus red oil pressure warning. Stop the engine immediately; oil pressure loss destroys an engine in seconds.
  • Engine light plus temperature warning or steam. Stop and let it cool.
  • Engine light plus loss of power steering or brake assist. Stop; the car is not safe to control normally.
  • Engine light plus knocking, rattling or a strong fuel smell. Stop.

Amber means caution and book it in. Red means stop now.

The MOT Consequence

This is the part that turns a postponed job into a failed test.

Under MOT defect 8.2.2.2(g), an engine malfunction indicator lamp that is inoperative or indicating a malfunction is classed as a Major defect, which fails the test. The tester does not need to establish what the underlying fault is; the illuminated lamp is sufficient.

A bulb that does not work at all fails for the same reason, so removing the bulb to hide a fault does not work and is treated as a defect in its own right.

Get the fault fixed before the test rather than after. Where a lit light has already cost you a pass, what to do if your MOT fails covers the retest rules and timescales, and an MOT in Maidstone can be booked after the diagnostic rather than before.

Where the fault turns out to be mechanical rather than a sensor, that becomes a car repair quoted separately from the diagnostic.

Frequently Asked Questions

How long can you drive with the engine light on?

With a steady amber light and normal running, a few days to reach a garage. With a flashing light, stop as soon as it is safe, because catalytic converter damage happens within minutes.

Will the engine management light go off by itself?

It can, if the fault was transient such as a loose fuel cap. It clears after several successful drive cycles. A light that returns is reporting a real fault.

Does an engine management light fail an MOT?

Yes. A lamp indicating a malfunction is a Major defect under 8.2.2.2(g) and fails the test, whatever the underlying cause turns out to be.

Can I clear the light myself before the MOT?

It is counterproductive. Clearing codes resets the readiness monitors, and a car presented before those complete can be rejected on that basis alone.

What is the difference between the engine light and limp mode?

The light reports a stored fault. Limp mode is the ECU actively restricting power and revs to protect the engine, which means the fault is serious enough to warrant recovery.