Symptom
Reduced engine power or limp mode
The control module has deliberately restricted power to protect the engine or because it no longer trusts a critical signal. Usually accompanied by a warning message and a hard ceiling on speed or revs.
Also described as: limp mode, limp home, reduced power, restricted performance, safe mode, engine derate, power restricted, limp, حالت اضطراری موتور, قدرت موتور محدود شد, لنگ مود, modo emergencia, modo averia, potencia reducida, modo seguro, modo limitado, وضع الطوارئ, وضع الأعرج, قوة محدودة, السيارة دخلت وضع الحماية
Some causes mean you should stop driving
107 of the 814 codes that produce this symptom indicate a fault where continuing to drive risks damage or is unsafe. If the symptom is sudden or severe, treat it as one of those until a scan says otherwise.
What this usually means
Nothing has broken down here in the ordinary sense: the car has decided. Limp mode is a deliberate act, and it happens for one of two reasons — the management measured something outside the range it considers safe, or it stopped trusting a signal it needs and will not run at full power on a guess. Both are protective, and it is worth telling a driver so, because the experience is alarming and the usual instinct is to press on and find out.
What it does varies more than people expect. A torque ceiling, a rev limit, a throttle opening cap, a fixed gear — Japanese references describe a transmission fail-safe holding a five-speed in third, which feels exactly like an engine fault and is not one. So the first useful question is what has been limited, because a car limited to one gear and a car limited to 2,500 rpm are pointing at different modules.
Whether it clears on an ignition cycle is the second question and it is diagnostically strong. A limit that lifts on restart and returns under the same conditions is an intermittent reading going briefly out of range — a boost overshoot on a steep climb, a sensor whose signal drops out when hot. A limit that survives a restart is a hard fault the module has confirmed and will not release. The first is very often gone by the time anybody looks, which is why the freeze-frame data matters more than the road test.
On a modern diesel two causes dominate and both are ordinary: boost control, and the particulate filter. On a petrol engine the throttle system is the classic — two pedal position sensors exist precisely so the module can cross-check them, and when they disagree it stops believing either and falls back to a cautious map. Russian references note that the resistive track on a high-mileage throttle position sensor wears through and drops the signal, which puts the engine straight into its emergency programme.
Do not clear the code to see if it comes back. That is the one action that destroys the evidence you need, and the car will re-limit itself the moment the condition recurs.
Working through it
| What you find | Likely cause | How to confirm it | What fixes it |
|---|---|---|---|
| Warning message with a hard rev or speed ceiling, engine otherwise smooth | A deliberate torque limit — the management is protecting something or distrusting a signal | Read codes *and* freeze-frame data before clearing anything, then note which parameter the frame shows out of range. The frame is often the only record. | Diagnose the named code. Clearing without reading loses the one snapshot of the conditions that triggered it. |
| Clears on restart, returns under the same conditions — a long climb, a hot day | An intermittent reading briefly out of range rather than a failed part | Reproduce with live data logging under those exact conditions. Static testing in a workshop will find nothing, which is why the driver's account of when it happens is evidence. | Repair what the logged excursion names. Resist replacing parts on the code alone when the fault is conditional. |
| Survives a restart and is present every time | A hard fault the module has confirmed — it will not release the limit until the fault is repaired | Read codes; the fault is current rather than historic and should be reproducible on the bench or at idle. | Diagnose normally. This is the easier of the two cases, because the evidence is still in front of you. |
| Diesel, with boost or particulate filter codes stored | Boost control or a loaded filter — the two dominant triggers on a modern diesel | Compare requested against actual boost, and read soot and ash load with differential pressure across the filter. Check the variable-geometry actuator moves through its travel. | Free or renew the vane mechanism and actuator, repair charge leaks, and regenerate or replace the filter. Find why regenerations were failing. |
| Petrol engine, throttle or pedal sensor codes, power cut abruptly | The two pedal or throttle position signals disagree, so the module trusts neither | Watch both sensor tracks live through the pedal's full travel — they should move together in a fixed relationship. A worn resistive track shows as a dropout at one point in the sweep, which a static measurement misses. | Renew the pedal or throttle assembly. An oscilloscope shows the dropout that a multimeter reads straight through. |
| Stuck in one gear, engine revving freely | A transmission fail-safe, not an engine limit — the gearbox has locked to a safe ratio | Read transmission codes rather than engine ones, and check which gear it holds. Free revving with a fixed ratio is the tell. | Diagnose the transmission fault. Fitting engine sensors for this is a common and expensive misdirection. |
| Began immediately after work on the engine or its wiring | A connector not remade, a sensor disturbed, or an air leak introduced during the job | Retrace exactly what was touched. Compare live values against plausibility rather than against the code. | Remake the connection or repair the leak. Cheapest cause on the page and routinely diagnosed last. |
-
Warning message with a hard rev or speed ceiling, engine otherwise smooth
- Likely cause
- A deliberate torque limit — the management is protecting something or distrusting a signal
- How to confirm it
- Read codes *and* freeze-frame data before clearing anything, then note which parameter the frame shows out of range. The frame is often the only record.
- What fixes it
- Diagnose the named code. Clearing without reading loses the one snapshot of the conditions that triggered it.
-
Clears on restart, returns under the same conditions — a long climb, a hot day
- Likely cause
- An intermittent reading briefly out of range rather than a failed part
- How to confirm it
- Reproduce with live data logging under those exact conditions. Static testing in a workshop will find nothing, which is why the driver's account of when it happens is evidence.
- What fixes it
- Repair what the logged excursion names. Resist replacing parts on the code alone when the fault is conditional.
-
Survives a restart and is present every time
- Likely cause
- A hard fault the module has confirmed — it will not release the limit until the fault is repaired
- How to confirm it
- Read codes; the fault is current rather than historic and should be reproducible on the bench or at idle.
- What fixes it
- Diagnose normally. This is the easier of the two cases, because the evidence is still in front of you.
-
Diesel, with boost or particulate filter codes stored
- Likely cause
- Boost control or a loaded filter — the two dominant triggers on a modern diesel
- How to confirm it
- Compare requested against actual boost, and read soot and ash load with differential pressure across the filter. Check the variable-geometry actuator moves through its travel.
- What fixes it
- Free or renew the vane mechanism and actuator, repair charge leaks, and regenerate or replace the filter. Find why regenerations were failing.
-
Petrol engine, throttle or pedal sensor codes, power cut abruptly
- Likely cause
- The two pedal or throttle position signals disagree, so the module trusts neither
- How to confirm it
- Watch both sensor tracks live through the pedal's full travel — they should move together in a fixed relationship. A worn resistive track shows as a dropout at one point in the sweep, which a static measurement misses.
- What fixes it
- Renew the pedal or throttle assembly. An oscilloscope shows the dropout that a multimeter reads straight through.
-
Stuck in one gear, engine revving freely
- Likely cause
- A transmission fail-safe, not an engine limit — the gearbox has locked to a safe ratio
- How to confirm it
- Read transmission codes rather than engine ones, and check which gear it holds. Free revving with a fixed ratio is the tell.
- What fixes it
- Diagnose the transmission fault. Fitting engine sensors for this is a common and expensive misdirection.
-
Began immediately after work on the engine or its wiring
- Likely cause
- A connector not remade, a sensor disturbed, or an air leak introduced during the job
- How to confirm it
- Retrace exactly what was touched. Compare live values against plausibility rather than against the code.
- What fixes it
- Remake the connection or repair the leak. Cheapest cause on the page and routinely diagnosed last.
Codes that produce this symptom (814)
Listed with the codes that most typically present this way first — the likeliest place to start.
- P0045 Turbocharger/Supercharger Boost Control A Circuit/Open Typical of this code High
- P0046 Turbocharger/Supercharger Boost Control A Circuit Range/Performance Typical of this code High
- P0047 Turbocharger/Supercharger Boost Control A Circuit Low Typical of this code High
- P0048 Turbocharger/Supercharger Boost Control A Circuit High Typical of this code High
- P0049 Turbocharger/Supercharger A Turbine Overspeed Typical of this code Stop driving Critical
- P0068 Manifold Absolute Pressure/Mass Air Flow — Throttle Position Correlation Typical of this code Stop driving High
- P0087 Fuel Rail/System Pressure — Too Low Bank 1 Typical of this code Stop driving High
- P0088 Fuel Rail/System Pressure — Too High Bank 1 Typical of this code Stop driving High
- P0090 Fuel Pressure Regulator A Control Circuit/Open Typical of this code Stop driving High
- P0091 Fuel Pressure Regulator A Control Circuit Low Typical of this code Stop driving High
- P0092 Fuel Pressure Regulator A Control Circuit High Typical of this code Stop driving High
- P00AF Turbocharger/Supercharger Boost Control A Module Performance Typical of this code Moderate
- P0120 Throttle/Pedal Position Sensor/Switch A Circuit Typical of this code Stop driving High
- P0121 Throttle/Pedal Position Sensor/Switch A Circuit Range/Performance Typical of this code Stop driving High
- P0122 Throttle/Pedal Position Sensor/Switch A Circuit Low Typical of this code Stop driving High
- P0123 Throttle/Pedal Position Sensor/Switch A Circuit High Typical of this code Stop driving High
- P0124 Throttle/Pedal Position Sensor/Switch A Circuit Intermittent Typical of this code Stop driving High
- P0148 Fuel Delivery Error Typical of this code Stop driving High
- P016F Closed Loop Fuel Pressure Control At Limit - Pressure Too Low Typical of this code High
- P0190 Fuel Rail Pressure Sensor Circuit Bank 1 Typical of this code Stop driving High
- P0191 Fuel Rail Pressure Sensor Circuit Range/Performance Bank 1 Typical of this code Stop driving High
- P0192 Fuel Rail Pressure Sensor Circuit Low Bank 1 Typical of this code Stop driving High
- P0193 Fuel Rail Pressure Sensor Circuit High Bank 1 Typical of this code Stop driving High
- P0194 Fuel Rail Pressure Sensor Circuit Intermittent/Erratic Bank 1 Typical of this code Stop driving High
- P0217 Engine Coolant Over Temperature Condition Typical of this code Stop driving Critical
Information, not instruction
CarGeek is a reference, not a service manual. Its pages are written from public sources and from what other people have found, never from a manufacturer's own service information, so they can be wrong or incomplete for your particular vehicle. Some of what they describe carries real risk: high voltage, fuel under pressure, stored energy, hot and moving parts.
Have anything you intend to act on checked by a trained person against the manufacturer's own procedure for your vehicle. Nothing here replaces that procedure.
Others with this symptom
Be the first to write this up
Nothing posted about this yet. Whatever you found is worth writing down — even a dead end saves someone the same afternoon.
What makes one worth reading:
- The car — make, model, year and engine. The same fault behaves differently on each.
- What you measured, not only what you replaced.
- What actually fixed it — or that nothing did, which is worth knowing too.
Sign in or create an account to add what you found about Reduced engine power or limp mode.