2002 OBDII Error code PO456

[walsh28]

Check engine light came on for the first time and using the FIXD OBD tester It said PO456 evap system leak detected. I tried to find the evaporative emission control system on the dvd ford disc but could not find it ,the car is a 2002 bird 53,317 miles. Any help would be appreciated. Thanks

This page contains affiliate links for which I may be compensated. As an eBay Partner, and Amazon Associate I may be compensated if you make a purchase at no cost to you.

 

[tbird]

Leak could come from a number of places. I had a smoke test done and found my canister was cracked.

Related post- https://forums.fordthunderbirdforum...-thunderbird-small-vapor-leak-p0456-fix.7916/

P.S. please follow the directions when posting. Editing your subject now to add model year.

 

[Ronhbcc]

Check engine light came on for the first time and using the FIXD OBD tester It said PO456 evap system leak detected. I tried to find the evaporative emission control system on the dvd ford disc but could not find it ,the car is a 2002 bird 53,317 miles. Any help would be appreciated. Thanks

I had similar code on my 2003 that has 60k; Before attemptIng a repair, I first simply erased the code with my scanner and the check engine light went off; that was several months ago and the check engine light hasn’t returned; car did run great before check engine light appeared and still runs great after the erasure; I also gave the gas cap an extra turn to make sure that wasn’t the problem and throwing a code. Good luck! Ron H

 

[walsh28]

Thanks I will take that into consideration as the car runs fine before and after I have erased the code. I will do a wait and see if it reappears or if the car begins to run differently. Thanks for your input. Bill W

 

[Bruce Arrowood]

2003 8000 miles Check engine lite on. Bought a orb tester, code po442, I reset the the code,
Lite still off. As time goes by we’ll see if it comes back. 300 miles still okey.

 

[walsh28]

At This time and after lubricating the gas cap gasket I have not experienced the trouble code again.