Ford Ranger 3.2 TDCi Auto: Common Problems & Reliability Guide (South Africa)

Symptoms to watch for

• Ticking noise from the engine, low oil pressure, or an oil pressure warning light (oil pump)
• Reduced performance or power, sometimes linked to carbon-fouled turbo vanes sticking (worse with DPF/short-trip driving)
• Rough idle, misfires, or reduced performance from injector wear at higher mileage
• Any of the above alongside an EGR-related warning light or split intercooler hose (a visible boost leak)
• VERIFIED FINDING (added 2026-08-06): a coolant temperature warning light and/or the engine control light illuminating together with a genuine, noticeable drop in power - if this coincides with a stored cooling-fan-circuit fault code, the low power is very likely the vehicle's own protective thermal-derate response, not a separate, unrelated fault (the specific fault code and what it means are covered in the full report). The cooling fan itself may be silently stuck off (or stuck on) well before the derate response is ever triggered - a coolant temperature gauge running higher than normal, especially at idle or in slow traffic, is a real, earlier warning sign worth checking before power loss ever occurs
• VERIFIED FINDING (added 2026-08-06, second code investigated): random, sometimes intermittent loss of power, possible stalling, delayed acceleration, or sudden transmission-shift irregularities occurring alongside a stored CAN-bus data-integrity fault code - real sources describe this as the PCM entering a protective mode specifically because it can no longer trust data it's receiving over the CAN bus (the specific fault code and what it means are covered in the full report). Unlike the cooling-fan-derate pathway above, this does NOT require the engine to have run hot first - it's a direct, live response to bad/implausible network data, meaning power loss can appear suddenly rather than building up gradually
• VERIFIED FINDING (added 2026-08-19, third code pattern investigated): a genuine crank-but-no-start condition (engine turns over on the starter but does not fire) with P0335 and/or P0341 stored, where fuel rail pressure at the HPFP matches the commanded/desired value but no injectors are being pulsed - real, multi-source research confirms this is a mechanically coherent, real pattern on this engine, not a contradictory or confusing set of symptoms. The HPFP is cam-driven and can mechanically achieve correct rail pressure independent of the PCM's injection-timing logic; injector PULSE commands, however, require the PCM to have a plausible combined crank+cam sync to know each cylinder's actual position in its cycle - without that plausible sync, the PCM will withhold injector pulses entirely as a protective measure, even with a fuel system that is otherwise ready. This is a different, more serious symptom picture than the P0480/U0401 power-loss findings above (which affect a running engine); this is a genuine no-start.
• REAL, DOCUMENTED VARIANT (added 2026-09-12): the SAME underlying cam/crank correlation fault can instead present as a RUNNING engine in a restricted-power/limp strategy rather than a no-start - engine starts and idles normally, will not rev beyond approximately 2,000rpm, and the automatic transmission does not shift normally in Drive, though selecting Sport/manual mode still allows the driver to manually command gear changes (the engine itself remains capped at roughly 2,000rpm regardless of which mode is selected). P0341 is stored, but there is often NO check-engine/MIL and NO spanner/wrench warning light displayed - do not treat the absence of a warning light as evidence the code isn't real or isn't the cause.
• REAL, DOCUMENTED VARIANT, CONTINUED: fuel rail pressure (demanded vs actual) and manifold/boost pressure (demanded vs actual) both closely agree at idle and near the 2,000rpm ceiling - these systems are working correctly and are not the cause. MAF, however, shows a large gap: demanded around 75g/s at idle against an actual of only around 15g/s, rising to only around 48-53g/s approaching 2,000rpm. IMPORTANT, RESEARCHED FINDING: do NOT jump to condemning the MAF from this gap alone. A same-engine-family Ford Transit Forum thread (2.2 TDCi, a smaller-displacement relative of this 3.2, unrelated fault-free vehicle) reported an almost identical pattern - MAF desired ~89g/s vs actual ~17-19g/s at idle - with NO fault codes stored and no driveability complaint at all, and several other owners on that same thread independently reported similarly large gaps with healthy vehicles. This means a large MAF desired-vs-actual gap may be a normal characteristic of how this specific PID reads out on this PCM family generally (the 'desired' figure likely reflects a computed EGR/air-charge model target rather than a literal simple fresh-air-mass demand, though the exact Ford PID definition was not independently confirmed), NOT proof of a failed MAF - this could not be fully resolved either way in this research pass and is recorded as a genuinely open question, not a confirmed explanation. Solve the cam/crank correlation fault first; only pursue the MAF independently if the discrepancy persists after correlation is confirmed correct.

What To Check

Early-stage oil pump/turbo/injector wear may not be obvious on a short test drive. Service history and a specialist inspection are more reliable.