My F150 check engine light came on and I was able to use a code key to find out the problem codes. P0171 & P0174. There are articles online that show the number of things to check to try to find the cause and fix.

Q. I am a novice and have never worked under the hood of a car before. Is this something that is relatively easy to fix and can be done by me or should I take it to a mechanic. How much should a mechanic charge in CA?

Thank You Very Much.

 

Year, engine size and mileage should also be posted when asking for help. If you say 5.4 odds are it's the pcv and tube assembly, more specifically the 90% rubber boot where it attachés to the back of the intake. Ford base number 6C324 IIRC, about 30 or 40 bucks from Ford.

 

Your right, if you have no experience it's over your head.
First is to know what the codes are indicating.
Next what might be the causes.
Your codes are indicating the computer has shifted the fuel tables ( in computer software) to the rich end as far as they can go, so sets the codes to tell you that fact..
What could be the problem is usually excessive air leak into the intake tract.
The codes are the results of the OXYGEN sensors detecting excessive air and signal the computer to richen up the tables to correct the fault which "can't" be corrected hence the codes are set for both banks. (171/174)
Simple! no this is a computer system you are dealing with.
Good luck.

 

I have a 2003 4.2 xlt that had this same problem. Tried cleaning mass air sensor, intake, and several other things. The codes would go away for a week or two and come back. the following link shows how to fix the problem.
since this was done I have had no problems at all.


https://sites.google.com/site/fordf1...P0171P0174-Fix

 

Hey there, I have a 1997 4.6L V8 and have the P0174 Code only (system to lean in bank 2). I have yet to troubleshoot it, probably this coming weekend, but I was wondering if anyone has performed this fix on the 4.6L V8.

Obviously I will check for any other noticeable problems before i attempt a fix like this. But If anyone has any pointers, or has experienced this error code before feel free to let me know what you did!