P2009: Intake manifold runner control circuit low, bank 1

What the code tells you on its own

System
Powertrain

Engine, fuel, air, ignition, emissions and transmission. The overwhelming majority of what workshops bring to the AI.

Functional group
Air intake and MAF/MAP
Subsystem
Fuel and air metering
Failure type byte, when the tool sends one
00 (No sub-type information), 77 (Commanded position not reachable)

Scan tools report the same fault as P2009 and as P2009xx, where xx is a sub-type. They are one fault, and whether the sub-type appears at all depends on the tool and the protocol rather than on the car.

Diagnostics

What we see when P2009 turns up

Measured across the diagnostics run through Wrenchlane, not taken from a reference table. Figures as of 2026-10-06.

Diagnostics
9

March 2026 to August 2026

Separate workshops
8

Not one shop meeting it repeatedly

Arrived code only
11%

No symptom description entered at all

Most common marque
Volvo

Where we have seen it most

These are counts from our own work, not a claim about how common the fault is across all vehicles. They describe what independent workshops brought to us, which is a narrower and more specific thing.

Our diagnosis data

What WrenchLane ranked first on P2009

Across 10 real diagnoses of P2009 from 9 workshops (February 2026 to November 2026), this is the cause WrenchLane ranked most likely for the code, grouped by the part it named. Most often: Intake manifold, runners or flaps, in 50% of them.

  1. Intake manifold, runners or flaps 50% (5 of 10)
  2. Wiring, connector or ground fault 20% (2 of 10)
  3. Other causes 30% (3 of 10)

By make, where one make has enough on its own

Make Ranked first most often Diagnoses
Volvo Intake manifold, runners or flaps 50%, Wiring, connector or ground fault 20%, other 30% 10 (9 workshops)

Makes we see it on most: Volvo 10 (of 10)

Codes that came in with P2009

Code What it is Same diagnosis
P2262 Turbocharger boost pressure not detected, mechanical 3 of 10 (30%)

How to read this: these are the causes WrenchLane ranked first from the codes, the car and what the mechanic entered, not confirmed repairs. Each diagnosis is anonymised: no workshop, customer or number plate is used. Our own test accounts, the demo car and repeat runs of the same car are left out. We only publish a figure that rests on at least 10 diagnoses from at least 3 different workshops, with no single workshop above half of them; a code listed alongside needs at least 3. It describes what independent workshops brought to us, not how common a fault is across all cars. Data as of 2026-11-17. How we use diagnosis data

FAQ

Frequently asked questions

How do I run a diagnosis?

Select the vehicle on Start, click the Diagnostic card and choose New diagnostic. Fill in the description, the error codes and the mileage, then click Analyze.

Copy link
Do I have to type the codes from my scan tool?

No. Click the camera button next to Error codes and take or choose a photo of the scan tool's screen; WrenchLane reads the codes and their descriptions into the form. You can also speak them with the microphone.

Copy link
Are the public fault code pages built from my diagnostics?

They use diagnostics run in WrenchLane, with no workshop, customer, registration number or VIN shown. Each fault code page shows how often the code was seen and in how many workshops.

Copy link

Run P2009 against the car in front of you

Enter the code and the symptoms and get ranked probable causes for that specific vehicle, with the checks in the order worth doing them.