Flashing glow plug light on a TDI: what it is telling you
If the coil-shaped glow plug symbol on your dashboard is flashing while the engine is running, it is usually not telling you that a glow plug has failed. On most VW, Audi, Skoda and SEAT diesels a flashing coil light is the engine management system's way of saying it has detected a fault and stored a code in memory — doing much the same job a check engine light does on a petrol car. The car is often still driveable, sometimes with noticeably reduced power, but the fault will not clear itself and the stored code is the only thing that will tell you what is actually wrong. Below is what causes it most often on VAG TDIs, whether you should keep driving, and how to get the fault read properly.
Steady means glow plugs. Flashing usually means a fault.
The coil symbol has two separate jobs, and telling them apart is the whole thing.
Steady, before you start: normal. Turn the key or press start and the light comes on for a few seconds while the glow plugs warm the combustion chambers. It stays on longer on a cold morning and may barely appear at all when the engine is already warm. Once it goes out the pre-heat phase is finished, and many modern diesels will crank happily before that anyway. Nothing is wrong.
Flashing, with the engine running: a fault. The ECU has spotted a reading it does not like, logged it, and is warning you. The flash rate is only a way of getting your attention — it does not encode a fault code and there is nothing to be gained from counting the flashes. Exactly how it behaves varies between models and model years: some cars start flashing the moment the fault appears, others only show it on the next start, and it may stop flashing after a restart while the code stays quietly in memory. Many later VAG diesels also have a separate amber engine symbol, and you may see one, the other, or both. If you are not sure what a symbol on your particular car means, the handbook for that model is the authority.
What the car is actually doing when it flashes
When the ECU logs certain faults, it does two things at once: it lights the warning and it protects the engine. That protection is what owners call limp mode, and it is why the light so often turns up alongside a car that suddenly feels flat.
In limp mode the engine will typically pull cleanly from low revs and then simply stop pulling. The turbo does not seem to spool, overtaking feels hopeless, and the car may not want to rev past a certain point. Some faults limit power hard, some barely at all, and some do not limit anything — a sensor circuit fault can flash the light while the car drives exactly as it always did.
Switching off and restarting will often restore full power temporarily. That is genuinely useful for getting home, but it is not a repair, and it is not something to lean on for weeks. The reading that triggered it will drift out of range again, the code is still stored either way, and repeatedly resetting and driving hard on a boost, fuel pressure or injector fault is how a sensor-sized bill becomes a mechanical one.
Should you keep driving?
A flashing coil light on its own is an amber-level warning rather than a red one on most VAG diesels. Here is a sensible way to decide, and if you are in any doubt, recovery is cheaper than an engine.
- Stop as soon as it is safe, and call for recovery, if the flashing light is joined by any red warning — oil pressure, coolant temperature, charging — or if the engine is running roughly, misfiring, making a new mechanical noise, or producing heavy white, blue or black smoke.
- Stop immediately if you have just filled up and the problem started straight afterwards. Petrol in a diesel is one of the few faults where running the engine is what does the damage. Do not restart or crank it — have it recovered and the fuel system drained.
- Drive gently to somewhere safe and get it looked at soon if the car has lost power but is otherwise smooth. Keep the revs modest, skip the motorway if you reasonably can, and do not tow or carry a heavy load.
- Carry on carefully but book it in if the car drives exactly as it always has. That is the least urgent case, but it is not an all-clear: the fault is real, it will still be there next week, and no dashboard lamp can promise you nothing is wearing out behind it.
- Never treat the light as decorative. Ignoring a boost or fuel pressure fault for months is how a cheap sensor becomes an expensive turbo or injector.
- Red lamps generally mean stop now, amber generally means investigate — but colours and symbols vary between models, so check your handbook for the car in front of you.
What usually causes it on a VAG TDI
These are the areas that come up again and again on Golfs, Passats, A3s and A4s, Octavias, Leons and the vans. Any one of them can flash the coil light, which is precisely why guessing is a poor strategy — the list below is what to expect, not a diagnosis.
- Boost pressure deviation. The ECU asks for a certain boost, does not get it (or gets too much), and logs it. Behind that sits either the variable-vane turbo actuator sticking with age and soot, or something as simple as a split intercooler hose or a popped-off pipe clamp.
- Mass air flow sensor drift. MAF sensors more often drift than fail outright, and a sensor that under-reads leads the ECU to cut fuelling — so the usual complaint is a flat, gutless car with an air mass fault stored, rather than a smoky one.
- EGR valve and its cooler. Carbon build-up stops the valve reaching the position the ECU commanded, and the mismatch gets logged.
- Fuel pressure regulation. On common rail engines this covers the rail pressure sensor and the metering and regulating valves on the high pressure pump. These faults often cause the sharpest power cuts and sometimes non-starts.
- Injector faults. Uneven contribution between cylinders, or a single injector out of tolerance, on both PD and common rail engines.
- Crankshaft and camshaft position sensors. Classic intermittent causes — the car cuts out or refuses to restart when hot, then behaves perfectly at the roadside.
- Inlet manifold swirl flaps, on the engines fitted with them. The motor or linkage jams and the ECU logs an actuator that will not reach its target.
- Low battery or charging voltage. Weak voltage produces odd sensor readings all over the car and can generate a cluster of unrelated-looking codes.
The one case where it really is the glow plugs
There is an exception worth being fair about. The glow plug circuit is itself monitored, so a failed glow plug, a corroded connector or a faulty glow plug control module can also store a code and flash the light. The distinction still holds: the light is reporting a stored fault, and a glow circuit fault happens to be one of the things it can report.
You can often spot this one from the symptoms. Glow plug problems are cold-start problems. The engine takes several attempts to catch on a frosty morning, runs lumpy and clattery for the first half minute, and blows white smoke that clears as it warms. In mild weather or when the engine is already hot, the car tends to feel completely normal. If instead your car is flat and gutless when fully warm, glow plugs are unlikely to be the answer — though only the stored code will settle it.
Getting the fault read properly
Every one of the causes above produces the same flashing light. The only way to separate them is to read what the engine module has stored, and there is a real difference in what different equipment can see.
A basic OBD reader from a motor factor talks to the emissions side of the engine ECU and will return generic P-codes. That is genuinely better than nothing, and sometimes it lands right on the answer. But a great many VAG faults are stored as manufacturer-specific codes with their own descriptive text, and plenty of them sit in modules a generic reader does not look at. It is entirely possible to plug in a cheap reader, be told there are no faults, and still have a light flashing at you.
VAG-capable equipment — whether that is a specialist independent garage's kit or your own — goes further in two ways that matter. First, it interrogates the individual control modules rather than just the emissions subset, with the manufacturer's own fault text and, on most engine ECUs, the freeze-frame conditions captured when the fault occurred: typically things like engine speed, load and temperature, often with a counter for how many times it has happened. Second, it shows live measuring values, so you can watch requested boost against actual boost, or airflow against the expected figure, while the engine is running. That is what turns "boost deviation" into "the actuator is not moving" rather than a shot-in-the-dark parts order. VAGPULSE is our own Windows software and cable built for this kind of VAG diagnostic work, if you would rather own the capability than pay for a diagnostic hour each time.
Whatever you use, write down the codes exactly as shown before anyone clears anything.
Quick checks worth doing first
None of these need tools beyond a torch, and any of them can save you a diagnostic fee. Do them with the engine off and cool.
- Open the bonnet and look along the intake pipework between the turbo, the intercooler and the inlet. Split rubber elbows and clamps that have worked loose are a common and cheap cause of boost faults. An oily split is often visible from a metre away.
- Check the engine oil level and when it was last changed. Low or long-overdue oil is hard on the turbo and its vane mechanism.
- Look for connectors that are loose, green with corrosion, or hanging off — particularly around the MAF sensor in the intake pipe after the air filter, and anywhere someone has worked recently.
- Think about what changed. A fault that appeared straight after a service, a fuel fill, a jump start or a period of standing is a strong clue.
- Note when it flashes: only when cold, only under load, only on the motorway, or all the time. Tell the garage that — it narrows things down more than most owners realise.
Read every module in your car — $249, one payment
VAGPULSE scans every control module in a VW or Audi, shows the live measuring blocks behind a fault, codes and adapts, and flashes Stage 1–3 maps with your original file backed up first. No subscription, unlimited cars.
Get VAGPULSE — $249Software downloads instantly · cable ships September 30 · cable guarantee
About clearing the code
Clearing is a legitimate diagnostic step. After a repair you clear the memory, drive the car, and see whether the fault returns — that is how you confirm the fix. It is also reasonable to clear a one-off code caused by something you have already dealt with, such as a flat battery or a disconnected sensor.
It is not a repair, and it should not be used as one. Clearing codes to make a warning light go out before you sell a car, or before an emissions or roadworthiness test, hides a fault from someone who has a right to know about it. That is deception, and it is usually also futile: clearing the memory throws away the freeze-frame evidence a diagnostician would have used (and, where the test includes an OBD readiness check, resets the monitors that check is looking for), the light often comes back within a drive cycle or two, and a car with a genuine boost, EGR or fuel fault tends to give itself away on a smoke test regardless. Rules vary by country — in the UK, for example, an engine management lamp that is lit or has been disabled can be a test failure on vehicles the check applies to, which depends on the car's age. A freshly cleared car has not passed anything; it has just forgotten something.
If you are handing the car to a garage, the most useful thing you can do is arrive with the light still flashing, the codes not yet cleared, and a clear description of when the symptoms appear. That combination gets you to an answer faster and cheaper than any amount of parts swapping.
Common questions
The light stopped flashing on its own. Is the problem fixed?
Probably not. Many engine faults are recorded as intermittent: the ECU sees the problem, warns you, then finds the reading back within limits on the next drive and puts the lamp out. The code usually stays in memory, and on many VAG ECUs with a counter showing how many times it has happened. Have it read while it is still there, because once the memory has aged the fault out you are back to guessing. A fault that comes and goes often gets worse — sticking turbo vanes and ageing MAF sensors can both behave like this before they fail properly.
Is a flashing glow plug light the same thing as the check engine light?
In practice it does much the same job on many VAG diesels, but they are not identical. The amber engine-shaped malfunction lamp is primarily an emissions warning, defined by regulation. The flashing coil symbol is VAG's own engine-management warning and can be triggered by faults that are not emissions-related at all — a sensor signal, a fuel pressure deviation, an actuator that will not reach its target. Sometimes both light up together. Sometimes only the coil flashes, which is one reason a generic scan can come back clean while a proper module-by-module scan shows stored faults.
Could it just be the DPF needing a regeneration?
On cars fitted with a diesel particulate filter, a blocked or over-full filter normally has its own warning symbol and its own message in the driver display, and the handbook's advice is usually to drive at a steady speed for a sustained period to let the filter clear itself — follow what your handbook says rather than a figure off the internet. A flashing coil light on its own is a broader engine-management warning, not a DPF-specific one. That said, DPF-related faults — differential pressure readings out of range, regenerations started and never completed — can certainly be among the stored codes, and repeated short journeys make that more likely. Reading the codes will tell you which you are dealing with.
Is it safe to drive to the garage with it flashing?
Often yes, if the car is running smoothly, temperature and oil pressure warnings are normal, and there is no smoke or unusual noise. Drive gently, keep the revs modest and avoid heavy loads, long motorway stints and towing. Stop and get it recovered if the engine is running roughly, misfiring, smoking heavily, losing coolant, making a new mechanical noise, or if a red warning appears. If you are unsure, recovery is the cheap option — you cannot tell a sensor fault from an early mechanical one by feel.
The car has lost power. Will a restart bring it back?
Often, yes — switching off, waiting a moment and restarting will clear a temporary limp mode and give you normal power back. That is a useful way to get home, but treat it as exactly that. The ECU did not limit power arbitrarily; it did it because a measured value was outside limits, and it will do it again. The stored code survives the restart, so get it read rather than assuming the restart repaired anything — and do not make a habit of resetting and driving hard, because on a fuel or boost fault that is how the damage gets done.