Parts for your 2002 Mitsubishi Lancer-Crank angle sensor

2002 Mitsubishi Lancer Crank Angle Sensor

Yes, the 2002 Mitsubishi Lancer is fitted with a crank-angle sensor (commonly called a crankshaft position sensor or CKP). This is documented in Mitsubishi Motors’ Lancer 2002 (CH/CS) Service Manual, Group 13A – Engine Electrical, under “Crankshaft Position Sensor – Description and Operation”, it’s also listed in the Mitsubishi ASA electronic parts catalogue for the 4G94 engine as “Sensor, Crankshaft Position”. Independent references such as Autodata Engine Management technical data and the Haynes Mitsubishi Lancer 2002–2011 manual also describe the CKP’s role and location on this model.

The crank-angle sensor on a 2002 Lancer keeps the engine running sweet by tracking the crank’s exact position and speed, so the ECU knows when to fire the coils and inject fuel. Without a clean signal from this little bloke, the car can be hard to start, misfire under load, or conk out randomly. On CH/CS Lancers with the 2.0‑litre 4G94, the sensor reads a toothed wheel on the crank—precision that lets the ECU control spark and fuelling down to the degree.

It’s not a regular “service item” like filters or plugs, but it’s smart to give it a once‑over during major services or when chasing rough running. Typical warning signs include a no‑start with a dead tacho, intermittent stalling when hot, and fault codes like P0335 or P0336. Before replacing, check the basics: look for chafed wiring near the crank pulley, loose connectors, and oil contamination from front seal weeps. A squirt of contact cleaner on the plug and clipping the harness away from the belt path can save headaches.

If replacement is needed, it’s a straightforward job for a competent home mechanic: disconnect the battery, lift the front, remove the splash shield, unplug the sensor, and undo the retaining bolt. Fit the new OEM‑quality sensor, route the loom exactly as factory, and snug the bolt to light fastener torque. No timing reset is required—the ECU relearns on start‑up. Clear any stored codes and take it for a gentle drive to let trims settle. Given how crucial timing data is, cutting corners with cheap aftermarket sensors can bite—genuine or reputable brands are worth it. Many workshops in Australia and New Zealand treat CKP inspection as part of diagnostics when a Lancer presents with hot‑stall, crank/no‑start, or misfire complaints.

• Common symptoms: hard starting, random stalling, misfire, no‑start, Check Engine Light with P0335/P0336.
• Service tip: inspect wiring near the crank pulley and lower timing cover, heat and road grime are the usual culprits.
• Best practice: use OEM‑spec sensors and confirm signal with a scan tool or oscilloscope if available.

Where is the crank-angle sensor on a 2002 Mitsubishi Lancer?

On CH/CS Lancers with the 4G94 engine, it’s mounted low at the front of the engine, reading a trigger wheel on the crankshaft behind the lower timing area. Access is usually from underneath after removing the front splash shield.

If unsure, follow the wiring from the lower front of the block near the crank pulley—look for a small two or three‑pin connector running to a sensor secured by a single bolt.

What are the signs the crank-angle sensor is failing?

Classic giveaways include intermittent stalling when hot, extended cranking or a complete no‑start, misfires, and a Check Engine Light with codes P0335/P0336. The tachometer may not move while cranking. These symptoms can mimic coil or cam sensor faults, so scanning and basic tests help narrow it down.

Before condemning the sensor, inspect the harness for damage and make sure the connector is clean and tight, as wiring faults are common.

Is it safe to drive with a dodgy crank-angle sensor?

Not really. A failing CKP can cause sudden stalling and a no‑restart, which isn’t ideal in city traffic or on the motorway. If the Lancer still runs, head straight to a workshop or home to sort it. Keep trips short and avoid heavy traffic until it’s repaired.

Leaving it can also make diagnostics messier, as intermittent failures can throw multiple unrelated codes.