Code guide
P0102 — MAF circuit low input
This is an electrical complaint, not a performance one: the airflow signal reaching the computer sat far below anything a running engine could produce. Dead signals are usually connections — which is why the connector outranks the cleaner here.
MAF circuit · Air metering · Often paired with P0113 — see below
The short version
P0102 means the signal from the mass air flow sensor read far lower than a running engine could honestly produce — near zero, or missing outright. The computer isn't saying the airflow is suspicious; it's saying the wire went quiet.
In rough order of likelihood:
- The connector — unplugged after other work, not fully latched, a corroded or backed-out pin, oil wicked into the terminals.
- The wiring between sensor and computer — chafed insulation where the harness bends, a broken conductor, a bad ground.
- The sensor itself electrically dead — it happens, but it's third on the list for a reason.
- Severe contamination can drag the reading low in slower ways — but a sudden, hard low-input code is a circuit story, not a cleaning story.
Reading codes and watching the live airflow signal are free in Fixiom — always, no credits and no subscription.
Circuit code vs dirty sensor
The MAF family splits into two kinds of complaint, and the split decides the repair aisle. Range/performance complaints (P0101, or a lean code like P0171) say the sensor is talking, but its story doesn't add up — that's where contamination and cleaning live. Circuit complaints — P0102 low, P0103 high — say the electrical signal itself went out of bounds.
That's why spraying cleaner at a P0102 usually accomplishes nothing: the element being clean doesn't help if its signal never reaches the computer.
The ten-second live test
Park on level ground, transmission in park or neutral, parking brake set. Never run an engine in an enclosed garage.
- Put the MAF reading on screen — it's in grams per second — and idle the engine.
- Read the number. A warm idle on most passenger engines sits somewhere in the low single digits of g/s, loosely tracking engine size. Precision doesn't matter here; life does.
- Blip the throttle. A live sensor jumps immediately with the air rushing in, then settles.
Reading the result: a reading pinned at or near zero that ignores the blip entirely is a dead signal — connector, wiring, or sensor, exactly as the code claims. A plausible idle number that responds crisply to the blip means the circuit is alive right now; suspect an intermittent connection (wiggle-prone, sets the code sometimes) and check the freeze frame for when it actually tripped.
The connector check
Engine off and cool. The MAF sits in the intake tube between the air box and the throttle body, with one obvious connector.
- Unlatch it and look — at both halves. Bent or backed-out pins, green or white corrosion, oil film on the terminals (over-oiled aftermarket air filters wick oil down the intake and into this exact connector).
- Check the harness where it flexes — the few inches of loom near the connector take the engine's movement, and chafe hides there.
- Reseat it to the click, firmly. A connector that was the fault often announces it by the code staying gone afterwards — cheap fixes count double when they're also diagnostic.
- If other work was done recently — air filter, battery, anything in that corner — assume the disturbance is related until proven otherwise. "It started after the air filter" is evidence, not coincidence.
When P0113 rides along
On most modern engines the intake air temperature sensor lives inside the MAF assembly and shares its connector. So when P0102 arrives together with P0113 — intake air temperature circuit high — the odds collapse onto one answer: a single connector or harness problem took both signals out at once. Two sensors dying independently at the same moment is not how probability works.
That pairing is one of the most useful two-code patterns in OBD2: it points a finger at one specific plug before anything is bought.
Why it still runs (badly)
Lose the airflow signal and the computer falls back to estimating airflow from throttle position, engine speed, and its maps. The engine runs — that's the point of the fallback — but on a guess: expect rough idle, hesitation, sometimes rich running and a fuel smell, and worse economy. Drivable to a driveway or a shop; not a state to commute in for a month.
What a phone adapter can't see
What it genuinely gives you: the live g/s reading and its response to a throttle blip — which is the aliveness test — the freeze frame from when the signal dropped, and any companions like P0113 that reframe the whole diagnosis.
What it cannot do:
- Measure the sensor's signal at the connector. Separating a dead sensor from dead wiring takes a meter, the pinout, and a wiring diagram.
- Find a chafe inside the loom. Eyes and fingers on the harness.
- Verify power and ground to the sensor — same meter, same diagram.
- Reseat the connector for you — though it will happily confirm the signal came back to life when you have.
Common questions
What does P0102 mean?+
The mass air flow sensor's signal read far below anything a running engine could produce — effectively missing. It's an electrical circuit code: the prime suspects are the connector, the wiring between sensor and computer, and only then the sensor itself.
Will cleaning the MAF sensor fix P0102?+
Usually not. Cleaning addresses contamination, which distorts a living signal — that's P0101 or lean-code territory. P0102 says the signal itself went dead or near zero, which is a connector, wiring, or failed-sensor problem. Check the plug before buying the spray.
Can I drive with P0102?+
Short distances, yes — the computer estimates airflow from throttle and RPM as a fallback, so the engine runs, just poorly: rough idle, hesitation, often rich. It's a get-it-sorted state, not a live-with-it state.
Why do I have P0102 and P0113 together?+
Because on most modern engines the intake air temperature sensor is built into the MAF assembly and shares its connector. Both codes at once almost always means one connector or harness fault silenced both signals — not two sensors failing simultaneously.
How do I tell if the MAF sensor is dead or unplugged?+
Watch the live airflow reading at idle. Near zero with no response to a throttle blip means the signal isn't arriving — then check the connector: latch, bent or corroded pins, oil in the terminals, chafe where the harness flexes. If the circuit checks out clean with a meter, the sensor earns the blame.
What is a normal MAF reading at idle?+
Low single digits of grams per second on most passenger engines at a warm idle, loosely scaling with engine size. For this code the exact number matters less than signs of life: a plausible reading that jumps when you blip the throttle is a living circuit; a zero that ignores the blip is a dead one.
Related guides
- P0113 — Intake air temp circuit high — and the -40° reading that gives it away instantly.
- Cleaning a MAF sensor — How to clean it properly — and how to tell first whether it's actually the problem.
- P0171 — System too lean — where fuel trims tell you the answer in about two minutes.
The signal went quiet. Quiet signals are usually connections.
Codes, freeze frames, and the live airflow reading are free in Fixiom — always. Ten seconds of g/s beats an afternoon of guessing.