Code
P1313
MITSUBISHI
P — Powertrain
Lean surge
Views:
UK: 2
EN: 8
RU: 6
AI status
Completed
Completed
100%
Causes
- Intake vacuum leak (cracked hose, loose clamp, leaking intake manifold gasket)
- Contaminated, faulty or misreading MAF sensor
- Low fuel pressure (weak fuel pump, clogged fuel filter, faulty pressure regulator)
- Clogged or leaking fuel injectors (reduced fuel flow, inconsistent spray)
- Slow or failing upstream O2 (lambda) sensor or heater circuit
- Exhaust leak upstream of O2 sensor (fools fuel trim)
Symptoms
- RPM surging or hunting at idle or cruise
- Hesitation or stumble on acceleration
- Intermittent stalling, especially at low load or idle
- Poor drivability under light to moderate throttle
- Higher than normal short-term and long-term fuel trims (positive)
- Decreased fuel economy
What to check
- Scan for stored and pending DTCs and capture freeze-frame / live data during event
- Inspect intake tract, vacuum lines, PCV hoses, and intake manifold for cracks, loose clamps, or missing gaskets
- Perform a smoke/pressure test of intake and vacuum system to locate leaks
- Monitor live PIDs: short-term and long-term fuel trims, MAF frequency/voltage or g/s, MAP, O2 sensor voltages, commanded vs actual fuel injector pulse width
- Measure fuel pressure at the rail at idle and under load; compare to specification
- Inspect MAF sensor element for contamination and wiring/connectors for damage/corrosion
Signal parameters
- Short term fuel trim (STFT): near 0% at steady state; sustained positive STFT > +10% indicates lean
- Long term fuel trim (LTFT): sustained positive LTFT > +10% supports persistent lean condition
- MAF sensor: frequency/voltage or g/s should be consistent for RPM/load (compare to known-good values or data sheet)
- O2 (upstream) sensor voltage: should switch rapidly between ~0.1–0.9 V in closed loop; slow or fixed reading indicates problem
- Fuel rail pressure: manufacturer-specific (typical gasoline systems ~40–60 psi); pressure should not drop under load
- MAP/vacuum: steady vacuum at idle; large fluctuations or lower-than-expected vacuum can indicate leaks or valve timing issues
Diagnostic algorithm
- Retrieve codes and freeze-frame data; attempt to reproduce the surge while monitoring live data (STFT, LTFT, MAF, O2 voltage, fuel pressure).
- Visual inspection: check intake tract, vacuum/PCV hoses, intake manifold gasket, throttle body, and EGR for obvious leaks or damage.
- Perform a smoke test on the intake/vacuum system to find hidden leaks downstream of MAF or at manifold gaskets.
- Check fuel system: measure static and loaded fuel rail pressure and compare to spec; inspect fuel filter and pump operation.
- Test MAF: inspect and clean if contaminated (use proper MAF cleaner), verify correct output vs RPM/airflow. Replace if out of spec or intermittent.
- Monitor upstream O2 sensor: verify switching behavior and heater operation; replace if slow or non-switching.
- If fuel delivery and sensors check OK, perform injector balance or flow test to identify weak or leaking injectors; clean or replace as required.
- Inspect for exhaust leaks upstream of O2 sensor that can cause false lean readings and correct as needed.
- Check sensor wiring and grounds for corrosion, intermittent connections, or damaged shields; repair any faults.
- After repairs, clear codes and perform road test under the same conditions that produced the surge while recording data to confirm issue resolution.
Likely causes
- Intake vacuum leak allowing extra air downstream of MAF
- Low rail fuel pressure under load
- Contaminated MAF giving under-reporting airflow (engine runs lean)
- Slow-switching or biased O2 sensor leading to incorrect closed-loop trims
- Leaking injector or reduced injector flow on affected cylinders
- Exhaust leak near upstream O2 sensor causing false lean readings
Fault status
Status
Lean surge detected — the engine control system observes a lean air/fuel condition causing unstable RPM or surging. Investigate air leaks, fuel delivery, and sensor operation; repair and verify with live-data testing.
Repair difficulty: Medium
Diagnostic time: 1.5-3.0 hours
Similar codes
Your experience will help others
+100 karma for a short comment :)
Was this AI description helpful?
Your feedback helps improve AI descriptions.
👍 Like
0
👎 Dislike
0
Send to email