Will an Engine Management Light Fail Your MOT? The Rules, Explained Properly

Yes — an illuminated engine light is a major defect under DVSA rule 8.2.1.2(h). Which cars are exempt, what testers check, and what to do first.

Yes. If your engine management light (EML) stays on with the engine running, your car will fail its MOT. Since May 2018 an illuminated or inoperative engine malfunction indicator lamp has been a major defect under section 8.2.1.2(h) of the DVSA inspection manual — an automatic fail with no tester discretion. Here is exactly how the check works, who is exempt, and the sensible order of action.

What the tester actually does

The engine malfunction indicator lamp (MIL) check is a defined step in the MOT, not something a tester notices in passing. From the DVSA inspection manual, the tester must:

1. Turn the ignition on and confirm the MIL illuminates — a lamp that never lights is itself a fail, because the car can no longer warn you of a fault.
2. Start the engine (on some vehicles the lamp goes out only after start-up) and confirm the MIL extinguishes.
3. If the lamp stays on — steady or flashing — record defect 8.2.1.2(h), “engine MIL inoperative or indicating a malfunction”. Category: major. Result: fail.

There is a persistent belief on UK car forums that the light “only counts as an advisory”. That was broadly true before the defect categories changed in May 2018, which is why you will still find contradictory answers online. Under the current manual there is no grey area: lamp on equals major defect equals fail.

Which cars are covered

The MIL inspection applies to:

• Petrol cars first used on or after 1 July 2003
• Diesel cars first used on or after 1 July 2008

Older vehicles are not subject to the MIL check itself — but do not celebrate too early. The emissions measurement still applies to them, and the underlying fault that lights an engine lamp (a failed lambda sensor, a tired catalytic converter) is often exactly the kind of thing that pushes a car over the emissions limits anyway. The lamp check and the tailpipe test are two nets for the same fish.

Steady versus flashing: how urgent is it?

• Steady amber: the engine control unit has logged a fault that affects engine management or emissions. The car is usually safe to drive short distances, but it is an MOT fail in waiting and often burns more fuel while unresolved.
• Flashing: the ECU has detected an active misfire severe enough to damage the catalytic converter. Stop driving beyond what is necessary and deal with it promptly — a destroyed catalytic converter turns a £150 fix into a repair bill many times that size.

The right order of action (and the trap to avoid)

Step 1 — read the code before anyone else does. The fault behind the lamp is stored in the car’s OBD2 system as a diagnostic trouble code. A plug-in reader such as the MotoPower V310 shows the stored code and a plain-English description in under a minute, with no app or subscription. Knowing whether you are looking at a loose fuel cap (EVAP code) or a catalyst efficiency code (P0420) changes everything about what you do next — and it means a garage cannot hand you a vague, open-ended diagnosis. You can look up what your code means in our fault code checker.

Step 2 — fix the cause, not the symptom. Some causes genuinely are DIY: a fuel filler cap that was not clicked shut, a split vacuum hose you can see and replace. Others — misfires, catalyst efficiency, EGR flow — need parts or a workshop. Either way, walking in with “it’s logging P0171, system too lean” gets you a better conversation than “the light’s on”.

Step 3 — do not just clear the code and book the test. This is the trap. A code reader can erase the lamp, but if the fault is real the lamp returns — sometimes within miles. Worse, clearing codes resets the car’s readiness monitors, the self-tests the OBD system runs to confirm its emissions equipment is working. Testers can see incomplete monitors, and a car that arrives with everything freshly wiped looks exactly like what it is. We cover this mechanism in depth in can clearing codes get you through an MOT?

What it costs if you ignore it

UK garages typically charge £50–£150 for a diagnostic session — often the first line on the invoice after a failed MOT. The repair itself ranges from nothing (tighten the fuel cap, clear the code, drive normally) to significant money for catalyst or DPF work. The one certainty: finding out on MOT day is the most expensive way to find out. A £37.95 code reader that lives in the glovebox pays for itself the first time it replaces a single diagnostic fee, and it turns the annual test from an ambush into a formality. Our 30-minute pre-MOT checklist shows where the code scan fits into the wider test-day routine.

Frequently asked questions

Does an ABS or airbag light also fail the MOT? Yes — those are separate defined checks with their own defect codes. Any of the major warning lamps staying on (engine, ABS, airbag, brake fluid, steering) is a failure item. Note that the V310 reads engine codes only; ABS and airbag faults need a multi-system tool or a garage.

My light went off by itself. Will the stored code fail me? No — the MIL check is about the lamp’s behaviour during the test. If the lamp goes out and stays out, the stored historical code does not itself fail the car. But an intermittent fault tends to come back, so it is still worth reading the code and understanding it.

Can I drive to the MOT with the light on? Legally you can drive a booked-in car to a test, but you already know the result. Read the code first, fix the cause, then book.