Ford P0455 — Evaporative Emission System Leak Detected — Large Leak
P0455 means the EVAP monitor could not build or hold vacuum or pressure in the fuel-vapour system, and the shortfall was large. Large leaks have a short list of causes and the first one is genuinely the fuel cap — not because techs are lazy, but because a missing or unsealed cap is a large open path by definition. Once the cap is verified, this becomes a straightforward find-the-leak job: smoke-test the system and follow the smoke.
Read this as diagnostic guidance, not a repair order. Procedures, torque values, thresholds and pinpoint tests vary by platform and model year — always work from the Ford Workshop Manual entry for the exact vehicle in front of you. Work safely: relieve fuel pressure before opening a fuel system, let exhaust components cool, and follow the manufacturer's procedures for high-voltage and airbag systems.
What has to happen for this code to store
- The EVAP monitor seals the vapour system and either pulls it into vacuum or pressurises it, then watches whether the pressure holds.
- A leak large enough that the system cannot reach or hold the target sets the gross-leak code. A smaller shortfall sets the small-leak code instead.
- The monitor has enable criteria — fuel level within a range, ambient temperature, soak time, steady conditions. That is why the code often appears the morning after a fill-up and why it can take a drive cycle before a repair is confirmed.
- A stuck-open purge or vent valve prevents the system from sealing at all, which the monitor reports as a leak even though nothing is physically torn.
Platforms we work on
- Ranger 2.3L EcoBoost
- F-150 3.5L EcoBoost
- Escape 1.5L EcoBoost
- Edge 2.0L EcoBoost
These are the Ford platforms this code is covered on in our own diagnostic scenario corpus. It is a statement about our coverage, not a claim that the code is limited to these vehicles.
Causes, in the order worth testing them
This is a test sequence, not a frequency ranking — cheapest and most discriminating first. We do not publish invented percentages. What each branch gives you is the observation that separates it from the others.
- 1
Fuel cap missing, loose, or not sealing
The cap is part of the sealed system. Missing, cross-threaded, or with a hardened seal, it is a large opening — the definition of a gross leak.
How you tellCheck that the cap is present, correct for the vehicle, clicks properly, and has an intact seal. Ask the customer directly whether it was ever left off. On capless filler systems, inspect the filler flapper and seal instead — there is no cap to blame.
- 2
Disconnected, cracked or rodent-damaged vapour hose
The EVAP plumbing runs along the underbody where it is exposed to heat, road debris and rodents. A single disconnected line is a large leak.
How you tellSmoke-test the system and inspect the run from the tank to the canister to the engine. Physical damage is usually visible once smoke shows you where to look — this is what the smoke test is for.
- 3
Vent or purge valve stuck open
If the vent valve does not close, the monitor can never seal the system, and it reports a leak because from its point of view there is one.
How you tellCommand the valves and verify they actuate and seal. A system that will not build any vacuum at all, with no visible damage, points at a valve rather than a hole.
- 4
Canister or filler-neck damage
A cracked charcoal canister or a corroded filler neck is a large opening in the sealed volume, and both are common on older or high-mileage vehicles.
How you tellSmoke will find these. Inspect the canister body and mounting and the filler neck where it meets the tank, particularly on a vehicle from a corrosive climate.
- 5
Fuel tank pressure sensor misreporting
The monitor judges by what the pressure sensor tells it. A failed sensor can report a leak that does not exist.
How you tellThis branch is reached after the smoke test finds nothing. Read the tank pressure signal and see whether it responds sensibly to a commanded vent or purge event; a signal that never moves is not measuring the tank.
What to measure, and how to read it
| Signal | What it tells you | How to read it |
|---|---|---|
| Fuel tank pressure (FTP) | The pressure signal the EVAP monitor judges by. | Watch it respond as the vent and purge valves are commanded. A signal that does not move when the system state clearly changes is the sensor branch. Exact PID labelling varies by platform — confirm against the WSM for the vehicle in front of you. |
| Fuel level | Tank level at the time of the test. | The EVAP monitor only runs inside a fuel-level window. Testing outside it wastes a drive cycle and produces an inconclusive result that looks like a fixed vehicle. |
| Purge and vent valve command / state | Whether the valves are actually doing what they are told. | Command each valve and verify actuation. A valve that does not seal makes every leak test meaningless until it is addressed. |
| Vehicle service history | Prior EVAP work and prior repeat visits. | A repeat EVAP complaint after a cap replacement usually means the cap was never the leak. History prevents repeating a repair that already failed once. |
PID labels follow the naming used by FDRS and by Olympus. Exact labels and threshold values vary by platform and model year — confirm against the Workshop Manual entry for the vehicle you are working on. We deliberately do not reprint Ford specification values here.
Codes that change how you read this one
Small leak. Normally the system reports the most severe leak it finds, so P0442 and P0455 together is anomalous — that combination points at a purge/vent valve or sensor fault rather than at two separate holes.
Very small leak. All three leak codes stored together is the strongest form of the anomalous-cluster signal: suspect a valve, the tank-pressure sensor, or the filler/cap interface rather than three independent leaks.
EVAP leak detected — fuel cap loose or off. When present it names the branch directly; verify the cap and seal and re-run the monitor.
Mistakes that cost parts and repeat visits
- Replacing the fuel cap and returning the vehicle without confirming the repair. The monitor needs its enable criteria met before "no code" means anything — the customer driving 60 miles with the light still on does not mean the cap was innocent, and it does not mean it was guilty either.
- Skipping the smoke test because the cap "looked fine". A hardened seal looks fine and does not seal.
- Diagnosing the tank-pressure sensor before smoke-testing. The sensor is the last branch, not the first.
- Not checking whether the vent valve seals. If it does not, every leak test after that is measuring nothing.
- Forgetting that many current Fords are capless — on those, the filler flapper and seal replace the cap in this differential entirely.
What Olympus does with P0455
- 01Pulls vehicle history first, which catches a previous cap or EVAP repair that already failed once.
- 02Runs a self-test and reads stored DTCs from the PCM so the full leak-code picture, including any small-leak codes, is visible at once.
- 03Recognises the anomalous multi-leak cluster: when large, small, and very-small leak codes are all stored, it ranks purge/vent valve and sensor causes ahead of "find three holes".
- 04Asks the questions that actually discriminate here — whether the light appeared right after refuelling, whether the cap was ever left off, whether there is a fuel smell.
- 05Searches the Ford WSM and pinpoint tests for the EVAP topology on that platform and cites what it used.
- 06Tells the tech what confirming the repair requires, rather than declaring the job done because the code cleared.
Olympus is Ford/Lincoln-only today, runs on Windows, and drives the dealership’s own licensed FDRS session on the dealership’s own hardware — it needs FDRS installed, a VCM/J2534 interface on the vehicle, and a licensed Ford account. It does not replace FDRS and it does not ship Ford software. Verified-outcome tracking is early: the repair-outcome corpus is still being built, so nothing here is presented as an accuracy claim.
Run this diagnosis with the truck in front of you
Olympus reads the modules through FDRS itself — no retyping codes off a screen — pulls the live data named above, searches the Ford WSM, TSBs and pinpoint tests for the exact platform, and cites what it used. When the data does not separate the causes, it says so and names the test that would.
Clicking the download button starts a Windows installer download. Olympus needs FDRS and a licensed Ford account on the same machine — it drives your dealership's own FDRS session, it does not replace it. First 10 diagnostics are free.
FAQ
- Can a loose gas cap cause P0455?
- Yes — it is the textbook cause of a gross EVAP leak, because a missing or unsealed cap is a large opening in a system that is supposed to be sealed. That is why it is the first check. It is not the only cause: disconnected or damaged vapour hoses, a stuck-open vent valve, and canister or filler-neck damage all produce the same code.
- I tightened the gas cap but P0455 is still on. Why?
- Two possibilities. Either the cap was not the leak, or it was and the monitor has not re-run yet. The EVAP monitor only runs when its enable criteria are met — fuel level in range, appropriate temperature and soak time — so the light can stay on for a drive cycle or more after a genuine repair. If it persists past that, smoke-test the system.
- Is it safe to drive with P0455?
- It is generally safe and there is usually no drivability effect. You are venting fuel vapour, so it will fail an emissions test and you may smell fuel. If there is a strong fuel odour or any sign of liquid fuel, treat that as urgent — that is beyond an EVAP monitor code.
- What is the difference between P0455 and P0442?
- Both are EVAP leaks; the difference is size. P0455 is a gross leak — large enough that the system cannot hold pressure at all, which points at caps, disconnected hoses, and open valves. P0442 is a small leak, which usually means a hairline crack, a marginal seal, or a slightly leaking valve, and generally needs a smoke test rather than a visual inspection.
Related codes
- Code definition: SAE J2012 standard definition, cross-checked against Ford’s FDRS DTC translation catalog (36,032 entries) as loaded by backend/src/services/olympus/ford-dtc-catalog.ts.
- PID labels: the labels used by the Olympus Ford scenario corpus and FDRS emulator profiles (backend/eval/golden/profiles, backend/scripts/bench-harness/fixtures).
- Co-occurrence readings: the curated DTC cluster patterns in backend/src/services/olympus/constitution/v1/well-known-dtcs.ts.
- Diagnostic sequence: standard OBD-II/Ford drivability method. Thresholds, connector IDs, and pinpoint steps are deliberately not reproduced here — use the WSM / pinpoint test for the exact platform and model year.
FutureAI is an independent software company. We are not affiliated with, endorsed by, or sponsored by Ford Motor Company. Ford, Lincoln, F-150, Ranger, Bronco, Explorer, Escape, Edge, Transit, Mustang, EcoBoost, Power Stroke, FDRS and PTS are trademarks of Ford Motor Company, used here only to identify the vehicles and tools these pages describe.