P10D1 – PHEV Engine Fail (1)

The Mitsubishi fault code P10D1 – PHEV Engine Fail (1) is a manufacturer-specific diagnostic trouble code stored by the PHEV Control Unit (PCU) on Mitsubishi plug-in hybrid vehicles, most commonly the Outlander PHEV and Eclipse Cross PHEV. This code indicates that the PCU has detected a critical failure condition within the internal combustion engine (ICE) side of the hybrid drivetrain — preventing normal hybrid operation and triggering a drivetrain warning or EV-restricted mode. Understanding P10D1 is essential for both workshop technicians and informed owners, as it can affect vehicle safety, drivability, and high-voltage system behaviour.

What Does P10D1 Mean on a Mitsubishi PHEV?

P10D1 is a Mitsubishi-proprietary code outside the standard SAE OBD2 range. It is generated by the PHEV Control Unit — the central brain that coordinates the petrol engine, front and rear electric motors, battery pack, and charging systems. “PHEV Engine Fail (1)” means the PCU has identified a fault condition specifically related to the combustion engine subsystem that is severe enough to compromise normal hybrid powertrain coordination.

Depending on the sub-fault that triggered P10D1, the underlying issue may range from an engine start failure and abnormal crankshaft signal to a coolant temperature out-of-range condition or an engine torque delivery discrepancy detected by the PCU. Because the PCU monitors the petrol engine indirectly through CAN bus signals from the Engine Control Module (ECM), P10D1 is often accompanied by additional engine-side DTCs that pinpoint the root cause more precisely.

Symptoms of P10D1 – PHEV Engine Fail (1)

When the PCU stores P10D1, the vehicle’s behaviour changes noticeably. Common symptoms include:

• Orange or red drivetrain warning light illuminated on the instrument cluster
• EV mode restricted or vehicle locked into EV-only operation (petrol engine will not start)
• Reduced power or “limp home” mode — acceleration severely limited
• Petrol engine cranking but failing to fire, or refusing to crank at all
• Unusual vibration or stalling when the PCU attempts to start the engine under load
• “Check Hybrid System” or “Stop Vehicle — Service Required” message on the MID
• Loss of regenerative braking in some cases
• Charging system operating normally (the HV battery may still charge via cable) but range is limited

Common Causes of P10D1

Because P10D1 is a summary fault from the PCU, it can be triggered by a wide variety of underlying conditions. The most frequently encountered root causes are:

• Engine start system fault — the generator motor (MG1/front motor used as a starter) fails to spin the engine to a start RPM, often due to an inverter fault or HV contactor issue
• Crankshaft position sensor (CKP) fault — the PCU receives no or erratic RPM signal from the ECM, triggering engine fail status
• Engine coolant temperature (ECT) sensor out of range — extreme temperatures cause the PCU to inhibit engine operation as a protection measure
• Fuel system faults — low fuel pressure, failed fuel pump, or clogged injectors preventing combustion
• Ignition system faults — failed coil packs or spark plugs on one or more cylinders
• PCU–ECM CAN communication loss — a break in the CAN bus between the PCU and ECM causes the PCU to set engine fail status due to loss of torque data
• HV battery state of charge too low — if the HV pack cannot supply enough energy to motor-start the engine, the PCU logs an engine fail event
• Inverter overtemperature — thermal protection shuts down engine-start capability
• Software/calibration mismatch — after battery replacement or ECM reprogramming, PCU calibration may need resetting

Affected Mitsubishi Vehicles

Tools & Equipment Required

Step-by-Step Diagnosis

Follow this structured diagnostic sequence to identify the root cause of P10D1 efficiently:

• 1
  Full Multi-Module ScanConnect MUT-III or equivalent. Scan ALL modules — PCU, ECM, EV-ECU, ETACS, ABS/ASC. Record every DTC present. P10D1 in the PCU is almost always accompanied by a more specific code in the ECM or EV-ECU. Note freeze frame data for P10D1: engine coolant temp, battery SOC, vehicle speed, and ignition status at time of fault.
• 2
  Prioritise ECM DTCsAny P0xxx or P1xxx codes in the ECM take diagnostic priority. Common companions to P10D1 include P0335 (CKP sensor), P0300–P0304 (misfires), P0087 (fuel pressure), P0016 (cam/crank correlation). Diagnose these first — resolving the ECM fault will typically clear P10D1.
• 3
  Check HV Battery SOC & 12V SystemIn MUT-III live data, verify HV battery SOC is above 20% and 12V auxiliary battery voltage is above 12.4V (engine off). A low 12V battery causes widespread CAN communication faults that mimic engine failure from the PCU’s perspective. Charge or replace the 12V battery if below spec.
• 4
  Verify CAN Bus IntegrityIf no specific ECM codes are present, inspect the CAN bus between ECM and PCU. Check for corroded connectors at the ECM (under bonnet), PCU (behind instrument panel / firewall area), and the gateway module. Use an oscilloscope on the CAN H/L lines — look for clean differential signals at 2.5V ± 1V with no missing frames.
• 5
  Perform Engine Start Actuator TestUsing MUT-III, perform the forced engine start actuator test. Observe whether the engine cranks via the generator motor (MG1). If no crank attempt occurs, the fault lies in the HV inverter, contactor, or MG1 circuit. If it cranks but doesn’t fire, the fault is fuel/ignition side.
• 6
  Check Fuel Pressure & IgnitionConnect a fuel pressure gauge to the Schrader valve on the fuel rail. Key-on pressure should be 350–400 kPa. Crank pressure should hold. Also remove and inspect spark plugs — on high-mileage Outlander PHEVs, plugs are frequently overlooked because the engine runs infrequently in pure city EV use.

Scanner Readout Explained

Below is a representative MUT-III diagnostic readout for a first-generation Outlander PHEV presenting with P10D1, accompanied by a CKP sensor fault in the ECM. This output is typical of the format produced by Mitsubishi’s MUT-III SE diagnostic tool.

====================================================
  MITSUBISHI MUT-III SE — DIAGNOSTIC REPORT
====================================================
  Vehicle:     2017 Outlander PHEV (GG3W)
  VIN:         JMBXNGA3WGZ0XXXXX
  Date:        2025-03-14  09:42:11
  Technician:  Workshop Bay 2
====================================================

MODULE: PCU (PHEV Control Unit)
----------------------------------------------------
  P10D1  PHEV Engine Fail (1)
         Status:       Confirmed / Current
         Freeze Frame:
           Engine Coolant Temp:   82°C
           HV Battery SOC:        41%
           Vehicle Speed:         0 km/h
           Engine Speed:          0 RPM
           IG Status:             ON

MODULE: ECM (Engine Control Module)
----------------------------------------------------
  P0335  Crankshaft Position Sensor (CKP) — Circuit Malfunction
         Status:       Confirmed / Current
         Freeze Frame:
           Engine Speed:          0 RPM
           Coolant Temp:          82°C
           Battery Voltage:       12.6V
           Fuel Trim (ST):        0.0%

MODULE: EV-ECU
----------------------------------------------------
  No faults stored.

MODULE: ETACS
----------------------------------------------------
  No faults stored.

====================================================
  LIVE DATA SNAPSHOT (Key On, Engine Off)
====================================================
  HV Battery Voltage:          296.4V
  HV Battery SOC:              41%
  12V Auxiliary Battery:       12.6V
  Inverter Temperature:        38°C
  Front Motor (MG1) Speed:     0 RPM
  Engine Coolant Temp:         82°C
  CKP Signal:                  NO SIGNAL
  Fuel Rail Pressure:          372 kPa
====================================================

In this case the readout makes the diagnosis clear: the ECM is reporting no CKP signal, which means the PCU cannot confirm engine rotation during a start attempt — hence P10D1. The HV system and fuel pressure are both healthy, pointing to the crankshaft position sensor or its wiring as the root cause.

Step-by-Step Repair Guide

Repair pathway depends on the root cause identified during diagnosis. The two most common scenarios are covered below.

Repair Path A: Crankshaft Position Sensor (CKP) Replacement

• 1
  Locate the CKP SensorOn the 4B11 engine (1st Gen Outlander PHEV), the CKP sensor is located on the rear of the engine block, near the transmission bellhousing, on the driver’s side. Access is tight — removal of the undertray is recommended.
• 2
  Inspect Wiring FirstBefore replacing the sensor, inspect the connector and harness for chafing against the engine mount or bellhousing. This is the most common failure point on high-mileage examples. Repair any chafed wiring with adhesive-lined heat shrink.
• 3
  Replace the SensorDisconnect the connector, remove the single M6 bolt, and withdraw the sensor. Install the new sensor (Mitsubishi OEM part: MD303152 or equivalent), torque to 9 Nm. Reconnect the connector — ensure the locking tab clicks fully.
• 4
  Clear Codes & VerifyClear all DTCs in all modules using MUT-III. Start the vehicle and allow the PCU to attempt an engine start. Confirm P0335 and P10D1 do not return. Check live data to confirm CKP signal is present at cranking RPM.

Repair Path B: 12V Auxiliary Battery Replacement

• 1
  Test the 12V BatteryLoad-test the 12V auxiliary battery (located in the engine bay on 1st Gen, boot area on some variants). A battery showing 12.4V open-circuit but dropping below 10V under load is failing and will cause widespread CAN faults including P10D1.
• 2
  Use a Memory KeeperBefore disconnecting, connect a 12V memory keeper to the OBD2 port or a spare fuse slot. This preserves all module memory and avoids the need for full PHEV system re-initialisation after battery swap.
• 3
  Replace & ReinitialiseFit a quality AGM battery of the correct spec (typically 45Ah / 400CCA for GG3W). After reconnection, use MUT-III to perform the battery registration procedure to inform the charging system of the new battery. Clear all DTCs and test drive.

Repair Cost Estimates

Prevention & Maintenance Tips

Because Mitsubishi Outlander PHEV owners often drive predominantly in EV mode — particularly in urban environments — the petrol engine can go weeks without running. This unusual usage pattern accelerates certain failure modes that directly contribute to P10D1:

• Run the engine regularly: Allow the petrol engine to run for at least 20–30 minutes every 2–3 weeks, especially in cold climates. The PCU will do this automatically via its engine maintenance mode, but manual drives on A-roads help more thoroughly warm all components.
• Replace spark plugs on schedule: Mitsubishi specifies iridium plugs at 48,000 km intervals. PHEV owners who rarely use the engine often exceed this significantly — worn plugs cause hard starts that stress the entire engine-start system.
• Monitor 12V battery health annually: The 12V battery in a PHEV is critical but rarely charges as thoroughly as in a conventional car. Load-test annually, especially after 3 years or 60,000 km.
• Keep the HV battery above 20% SOC: Allowing the HV pack to deplete fully regularly accelerates cell degradation and can leave insufficient energy to motor-start the engine.
• Inspect the CKP wiring harness: During any service, check the CKP sensor harness routing for contact with the engine mount or hot surfaces. Re-route and secure with fresh cable ties if needed.
• Keep software up to date: Mitsubishi releases PCU and ECM software updates that address known engine-start coordination issues. Ask your dealer to check for open TSBs at each service.

Frequently Asked Questions

Can I still drive my Mitsubishi Outlander PHEV with P10D1 stored?

It depends on the warning light colour. If the vehicle shows an orange hybrid system warning and is operating in EV-only mode, limited driving may be possible to reach a workshop — but range will be restricted to HV battery capacity only. If a red warning light is displayed or the vehicle instructs you to stop, do not continue driving. Have the vehicle recovered and diagnosed immediately.

Will clearing P10D1 with a generic OBD2 scanner fix the problem?

No. Clearing the code without repairing the underlying fault will only cause it to return — often within the same drive cycle. A generic OBD2 reader cannot access the PCU module where P10D1 is stored; you need a Mitsubishi-capable scanner such as MUT-III or a professional aftermarket tool. More importantly, the root cause in the ECM or another module must be identified and repaired.

Is P10D1 covered under Mitsubishi’s PHEV warranty?

If the vehicle is within Mitsubishi’s standard warranty period (typically 5 years / 100,000 km in most markets, with the HV battery warranted separately for 8 years / 160,000 km), the repair should be covered. If P10D1 is caused by a standard wear component such as spark plugs or a 12V battery, warranty coverage may not apply. Check your specific market warranty terms and consult an authorised Mitsubishi dealer.

Why does P10D1 appear alongside P0335 so often?

The PCU relies on receiving a valid engine RPM signal from the ECM via CAN bus to confirm a successful engine start. When the CKP sensor (which feeds RPM data to the ECM) fails, the ECM cannot report engine rotation to the PCU. The PCU therefore concludes that the engine has failed to start and sets P10D1. This is a logical cascade: fix P0335 and P10D1 resolves automatically.

Can a software update fix P10D1?

In some cases, yes. Mitsubishi has released PCU software updates (via Technical Service Bulletins) for early Outlander PHEVs that address engine-start coordination logic, particularly for cold-weather starting conditions. If the vehicle presents with P10D1 intermittently with no clear hardware fault, ask your dealer to check for open TSBs and perform any available ECM or PCU reflash before replacing components.

How do I know if the PCU itself is faulty?

PCU failure as the primary cause of P10D1 is rare. It is typically confirmed only after all engine-side hardware faults, CAN bus issues, 12V battery problems, and software updates have been eliminated. Symptoms pointing more specifically to PCU failure include multiple simultaneous PCU-internal DTCs (not just P10D1), failure of MUT-III to communicate with the PCU at all, or confirmation via Mitsubishi dealer-level diagnostics that the PCU is outputting incorrect command signals to the engine system.

Does the Outlander PHEV have a timing chain or belt, and can it cause P10D1?

The 4B11 and 4J12 engines used in Mitsubishi PHEVs use a timing chain — there is no cambelt to replace. However, a stretched or worn timing chain can cause cam/crank correlation faults (P0016/P0017) which the ECM will report to the PCU, potentially triggering P10D1. If your vehicle has very high mileage and exhibits rattling on cold start alongside P10D1, a timing chain inspection is warranted.

Can I use an aftermarket scanner instead of MUT-III to diagnose P10D1?

Yes, with caveats. Professional-grade aftermarket tools such as the Autel MaxiSYS MS909, Launch X431 PAD VII, or iCarsoft MB V3.0 can read P10D1 and access most Mitsubishi PHEV modules. However, certain PCU actuator tests — particularly the forced engine start test and HV contactor relay tests — may only be available on MUT-III. For a complete diagnostic, dealer-level access is recommended at least for the initial scan.

Conclusion

Mitsubishi P10D1 – PHEV Engine Fail (1) is a PCU-level summary fault that signals the hybrid control system has lost confidence in the petrol engine’s ability to operate normally. While the code sounds alarming, it is most commonly caused by straightforward, affordable repairs — a worn crankshaft position sensor, chafed CKP wiring, a weak 12V auxiliary battery, or neglected spark plugs. Expensive PCU or inverter failure is the exception, not the rule.

The key to resolving P10D1 efficiently is a thorough multi-module scan with a capable diagnostic tool. P10D1 rarely stands alone — the companion DTCs in the ECM or EV-ECU will almost always point directly to the true fault. Address those first, clear all codes, and verify the repair with a live data check and a test drive that allows the PCU to attempt a full engine start cycle.