Ford P0442 — Evaporative Emission System Leak Detected — Small Leak
P0442 means the EVAP monitor sealed the vapour system, watched the pressure, and found a leak too small to be a gross failure but too large to pass. The practical difference from a large leak is that you will not find it by looking. A small leak is a hairline crack, a marginal seal, or a valve that leaks slightly — the smoke test is the diagnosis, not an optional extra step, and the monitor enable criteria decide whether your repair can even be confirmed today.
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 monitor seals the vapour system and evaluates how well it holds vacuum or pressure. A shortfall in the small-leak band sets this code rather than the gross-leak code.
- Enable criteria — fuel level within a window, ambient temperature range, sufficient soak time, steady driving — must all be met before the monitor runs at all.
- Because the leak is small, it can be intermittent with temperature: a seal that holds cold can leak warm, and vice versa.
- A valve that leaks slightly rather than a physical hole produces the same result, since the monitor only sees that the system did not hold.
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 seal marginal, or capless filler seal worn
A cap that clicks and looks correct can still have a hardened or nicked seal that leaks slightly. On capless systems the filler flapper seal does the same job and wears the same way.
How you tellInspect the seal itself rather than the cap’s action, and include it in the smoke test rather than exempting it because it "looks fine". This is the cheapest branch and the easiest to wave past.
- 2
Hairline crack or porous vapour line
Age, heat cycling and road debris produce small cracks in vapour lines that are invisible without smoke, especially where lines pass near heat or chafe against structure.
How you tellSmoke-test the whole system and follow the smoke. This is what separates P0442 from a gross leak in practice — there is nothing to see until you introduce smoke.
- 3
Purge or vent valve leaking slightly
A valve that does not seal completely bleeds the system down during the test. The monitor reports a leak because functionally there is one.
How you tellCommand each valve and verify it seals, not merely that it actuates. A valve that moves but leaks is a common cause of a small-leak code with an otherwise intact system.
- 4
Canister, filler neck or tank seal degradation
Seals and grommets at the canister, the filler neck and the tank sending unit harden over time and leak slightly.
How you tellSmoke will find these too. Pay particular attention to grommets and gasket interfaces on higher-mileage vehicles and in corrosive climates.
- 5
Fuel tank pressure sensor drift
The monitor judges by the pressure signal. A drifting sensor can report a small leak that does not exist.
How you tellReached only after a clean smoke test. Check whether the pressure signal responds sensibly to commanded valve events; a sensor that barely moves is not measuring the tank properly.
What to measure, and how to read it
| Signal | What it tells you | How to read it |
|---|---|---|
| Fuel tank pressure (FTP) | The signal the monitor judges by. | Watch it respond as the vent and purge valves are commanded. No sensible response means the sensor branch. Exact PID labelling varies by platform — confirm in the WSM for that vehicle. |
| Fuel level | Tank level at test time. | Outside the monitor’s fuel-level window the test simply does not run. Confirming a small-leak repair with the tank at the wrong level produces a "no code" result that means nothing. |
| Purge and vent valve state | Whether the valves seal, not just whether they move. | A valve that actuates but leaks is indistinguishable from a hole as far as the monitor is concerned, and it is easy to miss if you only confirm movement. |
| Vehicle service history | Prior EVAP work on this VIN. | A repeat small-leak code after a cap replacement is a strong hint that the cap was never the leak. History stops a repair from being repeated. |
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
Large leak. The system normally reports the most severe leak it finds, so small and large leak codes stored together is anomalous — that pattern points at a purge/vent valve or the tank-pressure sensor rather than at two separate holes.
Very small leak. Small, large and very-small codes all stored at once is the strongest form of the anomalous cluster and is a curated pattern in the Olympus test corpus: suspect the purge valve, the tank-pressure sensor, or the cap/filler interface.
Leak detected with the fuel cap named directly. When present, verify the cap and its seal and re-run the monitor before doing anything more involved.
Mistakes that cost parts and repeat visits
- Visual inspection instead of a smoke test. A small leak is by definition too small to see — this is the branch where skipping the smoke test guarantees a comeback.
- Replacing the cap and returning the vehicle without understanding the monitor enable criteria. "No code today" is not a confirmed repair.
- Treating small and large leak codes together as two separate holes instead of recognising the valve/sensor pattern.
- Verifying that a valve actuates but not that it seals.
- Chasing the tank-pressure sensor first. It is the last branch, after a clean smoke test.
What Olympus does with P0442
- 01Pulls vehicle history first, so a previous EVAP repair that already failed is on the table before testing starts.
- 02Runs a self-test and reads stored DTCs from the PCM so the whole leak-code picture, including any large or very-small leak codes, is visible at once.
- 03Applies the anomalous-cluster reading: multiple leak codes stored together get ranked as a valve or sensor fault, not as multiple holes.
- 04Searches the Ford WSM and pinpoint tests for the EVAP topology on that specific platform — the plumbing layout is what makes a smoke test efficient.
- 05States the monitor enable criteria as part of the verification plan, so the tech knows what actually confirms the repair.
- 06Keeps confidence at "could-be" until a smoke test has been performed, because on this code the data alone cannot localise the leak.
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
- What is a small EVAP leak on a Ford?
- It is a leak in the sealed fuel-vapour system that is large enough to fail the monitor but small enough that the system still mostly holds — a hairline crack in a vapour line, a hardened cap or filler seal, a slightly leaking purge or vent valve, or a tired grommet. The size is exactly why it cannot be found by looking.
- Do I need a smoke test for P0442?
- In practice, yes. A small leak is below the threshold of visual inspection, so smoke is what makes it findable. Skipping it and replacing the fuel cap on the assumption that the cap is the cause is the single most common reason this code comes back.
- Will P0442 clear itself after I fix the leak?
- It will clear once the EVAP monitor runs again and passes — but the monitor only runs when its enable criteria are met, which typically include fuel level in a certain range, an ambient temperature window, and enough soak and steady driving. That is why the light can stay on for a drive cycle or more after a correct repair, and why "the code did not come back this afternoon" is not proof of anything.
- Is P0442 worth fixing?
- It will fail an emissions test, and it means fuel vapour is escaping to atmosphere rather than being captured. There is usually no drivability effect, so it is a schedule-it repair rather than an emergency — but it will not fix itself, and the underlying cracked line or hardened seal only gets worse.
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.