Skip to content
Skip to content

OBD-II Code · Timing

P0022

Camshaft Position Timing Over-Retarded (Bank 1)

Severity

medium

Worth booking. It costs fuel, emissions or comfort until it is fixed.

Can you drive it

Only if running normally

A short trip to a shop may be reasonable if the light is steady and the car runs normally. Stop safely for a flashing light, severe shaking, overheating, loss of power, or another urgent warning. The code alone cannot confirm safety.

Indicative cost (USD)

$150–$800

Varies by vehicle, diagnosis, parts, and local labor. This is not a repair quote.

Bank 1 cam timing too retarded.

How a shop works this

Work from evidence to part, not the other way round. A code names a circuit or a symptom; it does not name the part that failed.

  1. Note every code that is set, not just this one.

    Codes that appear together usually narrow the cause faster than any one of them read alone.

  2. Read the freeze frame — the conditions the fault was recorded under.

    Cold or warm, idle or load, road speed and engine speed. A fault that only appears cold is a different fault from one that only appears under load, even with the same code on the scanner.

  3. Confirm the fault is current rather than history.

    Clear the code and see whether it returns under those same conditions. A code that does not come back may have been logged during a repair, a flat battery, or a bad connection that has since been disturbed.

  4. Then work the likely-causes list in the order shown.

    That order is what a shop checks first for this code — wiring and connections before the component they run to, because a connector costs nothing to inspect and is a common answer.

If the code comes back after a repair, the underlying fault is still there. That is the point to bring in a scanner with live data and freeze-frame, or a shop that has one.

Common symptoms

  • Check engine light
  • Weak power

Likely causes

  • VVT solenoid stuckMost common
  • Dirty oil
Read the full diagnostic procedureBank 2 intake camshaft mechanically OVER-RETARDED.

Bank 2 intake camshaft mechanically OVER-RETARDED. Mirror of P0012 on bank 2. Phaser won't advance off park position, or advances and falls back.

Cheapest-first ladder

  1. Live-data bank 2 intake commanded vs actual at 2500 rpm warm — actual stuck at 0 while commanded climbs means no oil routing or stuck phaser.
  2. Swap bank 2 OCV with bank 1 OCV.
  3. Clean OCV screen.
  4. Hot oil pressure verification. Don't replace the cam phaser before confirming OCV function and oil pressure — bank 2 phaser jobs are the most expensive single-bank cam-timing repair on most V-engines.
Vehicle-specific patterns2007-2013 Nissan Altima/Maxima/Murano VQ35 — bank 2 OCV failure, replace solenoid with updated part.
  • 2007-2013Nissan Altima/Maxima/Murano VQ35 — bank 2 OCV failure, replace solenoid with updated part.
  • 2008-2014Honda Pilot/Odyssey J35 — rear bank VTC OCV stuck closed from oil sludge.
  • 2007-2014Toyota Tundra/Sequoia 5.7L 3UR-FE — bank 2 OCV screen clog, clean before replacing.
  • 2009-2015Cadillac CTS/SRX 3.6L LFX — known bank 2 intake OCV failure pattern, GM bulletin covers replacement.

Estimated repair$60 to $1,800.

Look up another code

P0022 — frequently asked

What does a P0022 code mean?

Bank 1 cam timing too retarded.

What causes a P0022 code?

Common causes: VVT solenoid stuck; Dirty oil.

What are the symptoms of a P0022 code?

Typical symptoms: Check engine light; Weak power.

Is it safe to drive with a P0022 code?

Only if running normally. A short trip to a shop may be reasonable if the light is steady and the car runs normally. Stop safely for a flashing light, severe shaking, overheating, loss of power, or another urgent warning. The code alone cannot confirm safety. Estimated repair: $150-$800.

How do I diagnose a P0022 code?

Work from evidence to part, not the other way round. A code names a circuit or a symptom; it does not name the part that failed. 1. Note every code that is set, not just this one. 2. Read the freeze frame — the conditions the fault was recorded under. 3. Confirm the fault is current rather than history. 4. Then work the likely-causes list in the order shown.

More free tools

See all 9 tools