DOBD DashX ☰ Browse all codes Blog

The second most common code in our data is barely a problem

P0113 is the second most-scanned code in our entire dataset, and it is almost always riding along with a MAF code rather than causing trouble on its own.

Seen in
18,219
scans in the past year
Found in
2.87%
of scans on our apps

P0113 is the second most-scanned code out of 9,298 generic codes in our data, and it is one of the least dramatic. That combination is worth explaining, because "extremely common" and "extremely minor" do not usually describe the same fault.

What the code actually means

The intake air temperature sensor is a thermistor: its resistance changes with temperature, and the engine control unit reads that resistance as a voltage. Colder air reads as higher resistance, warmer air as lower. "Circuit high" means the ECU is seeing more voltage than the range it expects — which it reads as an implausibly cold reading, or an open circuit standing in for one. Either way, the fix is electrical, not thermal.

The reason this sensor is so often the cause of a code rather than a genuine part failure is where it physically lives. On most modern engines the IAT sensor is not a separate probe screwed into the intake — it is built into the mass airflow sensor housing, sharing a connector and, on some designs, sharing a circuit board. Whatever disturbs the MAF sensor tends to disturb its neighbour.

What the telemetry says

That shared housing shows up clearly in what else is on the same scan:

P010122.85%
P010222.79%
P010311.15%
P01187.31%
P01086.88%

P0101, P0102 and P0103 are all MAF-circuit codes. Nearly a quarter of P0113 scans carry a MAF-range code, and a further chunk carry P0118 — the IAT sensor's mirror-image "circuit low" code — and P0108, a manifold pressure circuit fault often set by the same wiring loom. Looked at from the other direction, the pattern is just as strong: 44.27% of P0101 scans also carry P0113. One dirty or unplugged sensor housing is setting two codes, not two failed parts.

What it usually is

  • A MAF sensor element coated in oil or dust, common on cars with an aftermarket or reusable oiled air filter.
  • A connector at the MAF/IAT housing that is not fully seated, or has a corroded pin.
  • Aftermarket intake piping that does not seal against the housing the way the factory tube did.
  • Less often, a genuinely failed sensor element inside the housing.

None of those requires touching the engine itself. That is a large part of why this code is so common and so low-stakes at the same time: the part that sets it is exposed, cheap, and easy to disturb without anyone doing anything wrong.

Can you keep driving?

Yes. An intake air temperature reading affects fuel trim calculations at the margins — cold-start enrichment mostly — not the engine's ability to run. You will not notice a drivability difference, and you will not damage anything by driving on it for a while. It is worth fixing because a wrong air-temperature reading nudges fuel trims slightly off all the time it is present, and because — per the numbers above — it is frequently flagging a MAF problem that is worth knowing about anyway.

What to do next

Start at the housing, not the wiring diagram. Pull the MAF/IAT connector and look at the pins for corrosion or a bent contact. Check whether the sensor element is visibly dirty — a light dusting of oil from an oiled filter is enough to throw the reading off, and a MAF cleaner spray (not brake cleaner, which can damage the element) usually sorts it. If the connector and element both look clean, check the wiring for a chafe point between the housing and the ECU, since "circuit high" is exactly the signature an intermittent open connection produces.

If P0101 or P0102 showed up on the same scan — and per the numbers above, there is close to a one-in-four chance they did — treat this as one investigation, not two. Fixing the MAF side usually clears both codes at once.

Read & clear your own codes

Scan your car, see what every code means in plain English, and clear it once it's fixed — with OBD DashX on your phone.

▶ Get it on Google Play

Related codes

Figures reflect only diagnostic scans recorded through our own apps and tools. Cars are typically scanned because a symptom or warning light prompted it, so these counts describe our scan records — not the incidence of faults in any model, and not the quality, reliability, or safety of any vehicle. No comparison between manufacturers or models is implied. All trademarks belong to their respective owners; no affiliation or endorsement is implied.

← All posts