That check engine light came on, you plugged in your scanner, and now you're staring at a P0442 code small evap leak detected. You've cleared it once, maybe twice, but it keeps coming back. If you're trying to pin down the source without throwing parts at the problem, testing the fuel tank pressure sensor (FTP sensor) is one of the smartest diagnostic moves you can make. This sensor is the primary way your car's computer monitors the evaporative emission system for leaks, and when it's not reading correctly, it can either miss a real leak or flag one that doesn't exist.

What does the fuel tank pressure sensor actually do?

The fuel tank pressure sensor sits on or near the fuel tank and measures the pressure and vacuum inside the tank and the evap system. Your powertrain control module (PCM) uses this sensor's signal to run a leak test, usually after you shut off the engine and the fuel tank cools down. The PCM looks for a specific rate of pressure change. If pressure drops too quickly or doesn't hold steady, it sets a leak code.

For a small evap leak typically a hole or gap smaller than 0.020 inches the pressure changes are tiny. That means the sensor needs to be accurate down to fractions of an inch of water column. Even a slightly out-of-spec sensor can mislead the PCM into thinking there's a leak when there isn't, or worse, let a real small leak go undetected.

Why should I test the FTP sensor before chasing other leak sources?

Small evap leaks are frustrating to diagnose. There are dozens of potential leak points hoses, fittings, the gas cap, purge valve, and canister and the leak is often too small to see or hear. If the FTP sensor is giving bad data, you could spend hours smoke testing and swapping parts without ever finding the problem.

Testing the sensor first takes about 10 minutes and costs nothing if you already have a scan tool and a multimeter. It either confirms the sensor is working so you can focus your efforts elsewhere, or it identifies a faulty sensor that's been the root cause all along.

What tools do I need to test the fuel tank pressure sensor?

You don't need expensive equipment for a solid baseline test:

  • OBD2 scan tool with live data to read the FTP sensor voltage or pressure reading in real time
  • Multimeter to check voltage output and ground at the sensor connector
  • Hand vacuum pump to apply known pressure or vacuum to the sensor
  • Basic hand tools to access the sensor (usually located on top of the fuel tank or near the fuel filler area)

How do I check the FTP sensor signal with a scan tool?

With the engine off and the ignition key in the "on" position, go to your scan tool's live data screen and find the FTP sensor PID. Here's what to look for:

  1. Key on, engine off, gas cap loose: The reading should be close to atmospheric pressure, typically showing around 1.3 to 1.7 volts on a 5-volt reference sensor, or a pressure reading near 0 inches of water column (inH₂O).
  2. Gas cap tightened: The reading should stay relatively stable. Any wild swings or a reading stuck at a high voltage (like 4.5V or above) suggests a problem with the sensor or its wiring.
  3. With engine running: The purge valve will create vacuum in the tank during normal operation. Watch the pressure reading change as the purge valve cycles. You should see a smooth, gradual change not erratic jumping.

If the sensor reads a constant value regardless of what's happening, or if it shows obviously wrong numbers, you likely have a bad sensor or a wiring issue.

How do I test the sensor with a hand vacuum pump?

This is the most reliable way to check sensor accuracy without replacing it:

  1. Disconnect the pressure hose from the FTP sensor.
  2. Connect your hand vacuum pump to the sensor port using the correct adapter.
  3. Apply 5 inHg of vacuum and watch the scan tool live data. The voltage should drop smoothly and proportionally. On most GM and Chrysler sensors, 5 inHg of vacuum corresponds to roughly 1.0 to 1.2 volts.
  4. Release the vacuum and apply slight pressure (1-2 psi). The voltage should rise above the baseline reading.
  5. Hold the vacuum for 30 seconds. If the voltage drifts while you hold steady vacuum, the sensor is leaking internally or has an electrical fault.

The key thing: the voltage should move smoothly and hold steady under constant input. If it jumps around, sticks, or doesn't respond at all, the sensor is bad.

What voltage specs should the FTP sensor read?

Specs vary by vehicle manufacturer, but here are common ranges:

  • GM vehicles (most common for FTP-related P0442 codes): ~1.3V at rest (atmospheric), drops with vacuum, rises with pressure. Reference voltage is 5V.
  • Chrysler/Dodge/Ram: Similar 5V reference, ~1.5V at atmospheric, 5V max at full pressure.
  • Ford: Some use a different sensor style. Check your specific service manual.

Always verify specs for your exact year, make, and model. A Mitchell or AllData subscription gives you pin-for-pin testing procedures and voltage charts for your vehicle.

Can a bad FTP sensor cause a P0442 small evap leak code without an actual leak?

Absolutely. This is one of the most overlooked causes of a recurring P0442 code. If the sensor reads pressure as slightly lower than it actually is, the PCM may interpret normal system behavior as a small leak. Some technicians have reported replacing the purge valve, gas cap, and canister before realizing the FTP sensor was the real problem.

On the flip side, a sensor that reads too high can mask a real small leak. The PCM thinks the system is sealed when it's not, and the code only sets when conditions are just right like cold weather or a specific fuel level.

What are common mistakes when testing the FTP sensor?

  • Only reading codes, not live data. A code tells you there's a problem; live data shows you whether the sensor is reading correctly.
  • Skipping the wiring check. A damaged wire or corroded connector can cause the same symptoms as a bad sensor. Always check for 5V reference at the connector and a good ground before condemning the sensor.
  • Not checking hose connections to the sensor. A cracked or disconnected hose between the sensor and the tank can give false readings. Inspect the hose connections carefully before testing.
  • Assuming the sensor is fine because it "looks" okay. These sensors fail internally all the time. Corrosion from fuel vapor exposure is a common failure mode, especially on vehicles over 8 years old.
  • Not running the evap monitor after replacement. If you replace the sensor, you need to clear codes and complete a drive cycle so the PCM can re-run the leak test and verify the fix.

How do I know if it's the sensor or an actual small leak?

Here's a practical approach that saves time:

  1. Test the sensor first using the vacuum pump method described above.
  2. If the sensor tests good, move on to a smoke test. Introduce smoke into the evap system and watch for leaks at every fitting, hose, and component.
  3. If the sensor tests bad, replace it, clear the codes, and run a drive cycle. If the code doesn't come back, you're done. If it does come back, there's likely a real leak too.

This order matters. Testing the sensor takes minutes and costs nothing. A smoke test takes more time and often requires equipment that costs $100-$400.

Practical checklist for FTP sensor testing

  • Connect your scan tool and pull any stored evap codes (P0440, P0441, P0442, P0455, P0456)
  • Check live data with key on, engine off note the baseline voltage or pressure reading
  • Open and close the gas cap while watching the reading for any change
  • Inspect the wiring harness and connector at the sensor for damage or corrosion
  • Verify 5V reference voltage and ground at the sensor connector with a multimeter
  • Connect a hand vacuum pump to the sensor and apply 5 inHg of vacuum
  • Watch for smooth, proportional voltage change on the scan tool
  • Hold vacuum for 30 seconds and confirm the reading stays stable
  • If the sensor passes, proceed to a smoke test of the entire evap system
  • If the sensor fails, replace it, clear codes, and run a complete drive cycle to verify

Start with the sensor. It's the fastest way to eliminate a major variable and get closer to the real fix without wasting time or money on parts you don't need.

Get Started