Positive vs Negative Fuel Trim: Read the Correction Before Naming a Cause

A technician sees a positive fuel-trim number and writes vacuum leak on the repair order. The number may justify further investigation, but that note skips a step: it turns a correction into a component diagnosis. A useful record says what changed, under which conditions, and what test will separate the possible explanations.

This guide is for interpreting conventional percentage fuel-trim displays on gasoline applications. Use the actual vehicle's service information for PID definitions, test conditions and limits. The worksheet below is an original way to organize observations; it does not replace that procedure.

What positive and negative mean

On the usual percentage display, positive fuel trim represents added fuel relative to the base calculation; negative represents removed fuel. Zero represents no correction in that displayed term. A positive correction does not prove a leaking intake, and a negative correction does not prove a leaking injector.

Short-term fuel trim, or STFT, shows the current feedback correction. Long-term fuel trim, or LTFT, represents learned correction. An STFT reading near zero can coexist with a substantial learned correction, so one number alone is an incomplete description.

Ford's 2013 gasoline OBD operation summary, pages 51-54, provides a manufacturer example: it distinguishes calculated short-term and learned long-term terms, explains that the displayed learned value relates to the current operating condition, and distinguishes percentage displays from internal multipliers. This historical explanation supports the terminology, not a universal specification for today's vehicles.

Make two captures comparable

Before comparing numbers, give each capture a short identity block. Without it, the next technician cannot tell whether a difference follows the complaint, the operating point or a change in how the data was collected.

• Record the vehicle, engine and fuel type, plus the current service-information reference.
• Save the tool, software, scan mode, exact PID label, units and bank identification.
• Record fuel-system status, temperature, RPM and load alongside the values.
• Mark whether the customer's symptom was present during that capture.
• Record recent repairs, code clearing or adaptation resets; use unknown when the history is unavailable.
• Save a trace or observed range over a stated interval instead of presenting a selected instant as the whole event.

Keep unsupported data distinct from a displayed zero. If a bank or PID is unavailable, write that down. Do not create an apparently complete comparison by filling a blank with zero. The freeze-frame guide explains how a stored event snapshot can be documented separately from a live capture.

A fictional example: same sign, different question

Consider an invented training record, not a real vehicle or an acceptance range. Capture A records Bank 1 STFT moving between +2% and +4%, with LTFT at +12%, while the reported idle symptom is present. Capture B records STFT between -1% and +1%, with LTFT at +3%, at a different documented operating point where the symptom is absent. Both captures include their fuel-system status and the rest of the identity block.

The useful handoff is: the recorded correction and symptom differ between these two conditions; reproduce and compare under the applicable procedure. The record does not establish which part caused that pattern. It also does not support calling Capture B a successful repair when no repair and verification have occurred.

If a second supported bank is available, add its observations under matching conditions. Treat a difference as a question to investigate, and preserve the original values rather than collapsing both banks into a single average.

Choose a test that can change the decision

Write the hypothesis on a separate line from the observation. Then identify the next test in the current vehicle-specific diagnostic procedure and state which possible result would support or weaken the hypothesis. That makes the next action reviewable without pretending that the fuel-trim display has already identified the cause.

For example, the observation might be a repeatable change during the documented complaint. The hypothesis names a possible explanation. The next-test field identifies the prescribed check and required conditions. Leave the result blank until the check is performed; do not substitute a likely answer.

Avoid assigning every vehicle the same percentage cutoff or adding STFT and LTFT into an exact universal verdict. Preserve both reported values and apply the manufacturer's interpretation. After work, record a comparable verification capture and follow the applicable adaptation instructions. Keep an unresolved difference visible in the handoff.

Use the observation worksheet

The downloadable worksheet keeps the capture reference, conditions, values, hypothesis and next test in separate fields. Attach the original export or image so someone can audit the note. Use the diagnostic report template to explain the confirmed findings and remaining work to the customer.

To discuss your shop's diagnostic records and technician handoffs, request STEP early access.