Fuel Delivery
P0174
System Too Lean (Bank 2)
P0174 sets when the PCM reaches the limit of fuel correction while attempting to compensate for a lean air/fuel mixture on Bank 2.
Diagnostic Snapshot
Atlas Academy
Learn the System
Before diagnosing this code, it helps to understand the system behind it.
Read Understanding Fuel Delivery SystemsTechnical Summary
P0174 sets when the PCM reaches the limit of fuel correction while attempting to compensate for a lean air/fuel mixture on Bank 2.
Final QA emphasis: P0174 requires correlation of positive fuel-trim correction, bank-specific versus shared airflow/fuel causes, unmetered air, exhaust oxygen intrusion, injector delivery, fuel pressure, and MAF/MAP plausibility. The code should be diagnosed by reproducing the enable condition, proving loaded electrical integrity, and independently confirming the physical system. OEM thresholds and system design take priority over universal values.
What You'll Learn
- Understand why Bank 2 is running lean
- Compare Bank 1 and Bank 2 fuel trims
- Distinguish shared causes from Bank 2-specific faults
- Test intake leaks, MAF data, fuel pressure, and injectors
- Avoid unnecessary oxygen-sensor replacement
Think Like a Technician
If P0174 appears alone, focus on Bank 2. If P0171 and P0174 appear together, begin with components shared by both banks before chasing bank-specific faults.
For P0174, ask three questions in order: what did the controller command or observe, can the circuit carry and report that condition correctly, and did the physical system actually respond? Use positive fuel-trim correction, bank-specific versus shared airflow/fuel causes, unmetered air, exhaust oxygen intrusion, injector delivery, fuel pressure, and MAF/MAP plausibility to identify which layer fails first.
What This Code Means
Bank 2 is receiving too much air, too little fuel, or inaccurate airflow information.
System Overview
Learn fuel delivery and fuel trim fundamentals before diagnosing P0174.
Why This Code Sets
Fuel trim corrections on Bank 2 exceed the PCM's allowable threshold.
Common Symptoms
- Check Engine Light
- Rough idle
- Hesitation
- Lack of power
- Misfire
- Hard starting
- Poor acceleration
Most Likely Causes
- 1. unmetered intake/vacuum air or PCV leak
- 2. MAF/MAP/load calculation bias
- 3. low fuel pressure or restricted delivery
- 4. bank-specific injector restriction or exhaust leak ahead of O2/A-F sensor
- 5. purge or other air/fuel control fault
- 6. O2/A-F sensor bias or PCM issue after mixture is independently proven
Common Vehicles
- Ford V6/V8
- GM V6/V8
- Toyota V6/V8
- Nissan V6
- Dodge/Ram V8
Freeze Frame Clues
Idle
High positive trims at idle usually indicate a vacuum leak.
Both P0171 and P0174 Present
Suspect shared causes such as a MAF issue, low fuel pressure, or a large intake leak.
Live Data Expectations
Normal
STFT: -5% to +5% LTFT: -5% to +5%
Lean
STFT: +15% to +30% LTFT: +10% to +25% Positive trims indicate the PCM is adding fuel.
Typical Verification Tests
- Read STFT/LTFT
- Smoke test intake
- Verify MAF readings
- Fuel pressure test
- Injector balance test
- Check exhaust leaks
Before You Condemn
- Verify:
- Fuel trims
- Vacuum leaks
- MAF readings
- Fuel pressure
- Injector operation
- Exhaust leaks
Before Replacing Parts
Confirm the cause before replacing oxygen sensors, injectors, or the MAF sensor.
Diagnostic Workflow
- Confirm P0174; save current, pending, history, freeze-frame, readiness, misfire/fuel-trim data where applicable, and the complete powertrain scan before clearing codes.
- Verify the exact definition — System Too Lean (Bank 2) — and review VIN-specific system design, enabling criteria, fail-safe strategy, wiring, component locations, bulletins, and test procedures.
- Prioritize companion DTCs and basic prerequisites: battery/charging voltage, module powers/grounds, engine mechanical condition, coolant temperature plausibility, and any shared reference or network faults.
- Recreate the freeze-frame condition safely and graph positive fuel-trim correction, bank-specific versus shared airflow/fuel causes, unmetered air, exhaust oxygen intrusion, injector delivery, fuel pressure, and MAF/MAP plausibility with RPM, load, temperature, vehicle speed, and system voltage.
- Inspect the relevant harnesses, connectors, hoses, pipes, grounds, vacuum lines, fuel/exhaust components, and recent repair areas before disconnecting or replacing anything.
- Compare commanded and actual data. Decide whether the failure is electrical, hydraulic/pneumatic, mechanical, combustion-related, or a sensor-plausibility problem before choosing the next test.
- Perform loaded electrical tests on affected powers, grounds, reference, signal, solenoid, injector, relay, or actuator circuits; static continuity alone is not sufficient for current-carrying circuits.
- Use bidirectional controls where supported to command the affected actuator or system and compare command with current/voltage feedback, sensor response, and actual physical operation.
- Independently verify the physical condition with the appropriate test: calibrated fuel-pressure equipment, smoke/EVAP test, compression/leak-down, ignition waveform, injector balance, airflow/pressure response, or another OEM-approved method.
- Separate bank-specific or cylinder-specific faults from shared-system faults by comparing the opposite bank, neighboring cylinders, redundant sensors, or common feeds under the same operating condition.
- Check for heat-, vibration-, and load-dependent failures by repeating the test as the system warms and by carefully manipulating suspect harness sections while monitoring data.
- Do not condemn a sensor because its reading is abnormal until an independent measurement establishes whether the sensor is wrong or accurately reporting a real physical fault.
- Do not condemn an actuator because it fails to respond until power, ground, control authority, mechanical freedom, and the load side of the circuit are proven.
- Before condemning the PCM, prove stable module powers/grounds, terminal tension, external loads, circuit capability, prerequisite inputs, network integrity, and current calibration/software.
- Repair only the fault supported by test evidence, then perform any required relearn, adaptation, fuel-trim reset, or monitor-specific service procedure.
- Repeat the original enable condition and verify P0174 remains absent current and pending, the monitored data is plausible, driveability is normal, and readiness progresses.
Labor & Inspection Checklist
- Fuel trims
- Intake hoses
- MAF
- Fuel pressure
- Bank 2 injector inspection
- Road test
Shop Notes
- A Bank 2-only lean code often points to a bank-specific vacuum leak or injector issue.
- Dual-bank lean codes usually indicate a shared air or fuel delivery problem.
- Clean the MAF only with approved cleaner.
Final QA diagnostic boundary for P0174: System Too Lean (Bank 2). The technician should center the diagnosis on positive fuel-trim correction, bank-specific versus shared airflow/fuel causes, unmetered air, exhaust oxygen intrusion, injector delivery, fuel pressure, and MAF/MAP plausibility rather than treating the DTC as a replacement instruction.
Evidence hierarchy: preserve freeze-frame first; confirm prerequisites second; compare command/input with loaded circuit behavior third; verify the physical system independently fourth. This order prevents a biased PID or unloaded continuity test from driving the repair.
Failure-pattern note: separate faults that follow engine load, heat, vibration, bank, cylinder, key cycle, purge/EGR command, or pressure demand. A repeatable pattern is often more diagnostic than a single static reading.
Before-parts rule: sensors require plausibility proof, actuators require power/ground/control plus mechanical-response proof, and modules require external circuit/load proof. Do not use a code description as proof of component failure.
Safety/driveability note: Often driveable short-term, but sustained lean operation can increase combustion temperature and misfire while sustained rich operation can overheat the catalyst and dilute oil. A flashing MIL, severe misfire, fuel odor, or major power loss means stop driving.
Verification standard: reproduce the original enable condition after repair, not merely a warm idle in the bay. Confirm the monitor's related PIDs remain plausible and that no pending code returns.
P0174 QA case-pattern 1: Reproduce the original operating condition and compare positive fuel-trim correction, bank-specific versus shared airflow/fuel causes, unmetered air, exhaust oxygen intrusion, injector delivery, fuel pressure, and MAF/MAP plausibility with an independent physical or electrical measurement. If the scan value changes but the physical system does not, investigate sensor interpretation, control authority, or a mechanical restriction. If the physical system changes but scan feedback does not, investigate the sensing/reference path. If neither changes, prove power, ground, command, and prerequisite conditions before escalating to the controller. Document the before-and-after data so the repair is verified by evidence rather than by the temporary absence of a code.
P0174 QA case-pattern 2: Reproduce the original operating condition and compare positive fuel-trim correction, bank-specific versus shared airflow/fuel causes, unmetered air, exhaust oxygen intrusion, injector delivery, fuel pressure, and MAF/MAP plausibility with an independent physical or electrical measurement. If the scan value changes but the physical system does not, investigate sensor interpretation, control authority, or a mechanical restriction. If the physical system changes but scan feedback does not, investigate the sensing/reference path. If neither changes, prove power, ground, command, and prerequisite conditions before escalating to the controller. Document the before-and-after data so the repair is verified by evidence rather than by the temporary absence of a code.
P0174 QA case-pattern 3: Reproduce the original operating condition and compare positive fuel-trim correction, bank-specific versus shared airflow/fuel causes, unmetered air, exhaust oxygen intrusion, injector delivery, fuel pressure, and MAF/MAP plausibility with an independent physical or electrical measurement. If the scan value changes but the physical system does not, investigate sensor interpretation, control authority, or a mechanical restriction. If the physical system changes but scan feedback does not, investigate the sensing/reference path. If neither changes, prove power, ground, command, and prerequisite conditions before escalating to the controller. Document the before-and-after data so the repair is verified by evidence rather than by the temporary absence of a code.
P0174 QA case-pattern 4: Reproduce the original operating condition and compare positive fuel-trim correction, bank-specific versus shared airflow/fuel causes, unmetered air, exhaust oxygen intrusion, injector delivery, fuel pressure, and MAF/MAP plausibility with an independent physical or electrical measurement. If the scan value changes but the physical system does not, investigate sensor interpretation, control authority, or a mechanical restriction. If the physical system changes but scan feedback does not, investigate the sensing/reference path. If neither changes, prove power, ground, command, and prerequisite conditions before escalating to the controller. Document the before-and-after data so the repair is verified by evidence rather than by the temporary absence of a code.
P0174 QA case-pattern 5: Reproduce the original operating condition and compare positive fuel-trim correction, bank-specific versus shared airflow/fuel causes, unmetered air, exhaust oxygen intrusion, injector delivery, fuel pressure, and MAF/MAP plausibility with an independent physical or electrical measurement. If the scan value changes but the physical system does not, investigate sensor interpretation, control authority, or a mechanical restriction. If the physical system changes but scan feedback does not, investigate the sensing/reference path. If neither changes, prove power, ground, command, and prerequisite conditions before escalating to the controller. Document the before-and-after data so the repair is verified by evidence rather than by the temporary absence of a code.
P0174 QA case-pattern 6: Reproduce the original operating condition and compare positive fuel-trim correction, bank-specific versus shared airflow/fuel causes, unmetered air, exhaust oxygen intrusion, injector delivery, fuel pressure, and MAF/MAP plausibility with an independent physical or electrical measurement. If the scan value changes but the physical system does not, investigate sensor interpretation, control authority, or a mechanical restriction. If the physical system changes but scan feedback does not, investigate the sensing/reference path. If neither changes, prove power, ground, command, and prerequisite conditions before escalating to the controller. Document the before-and-after data so the repair is verified by evidence rather than by the temporary absence of a code.
P0174 QA case-pattern 7: Reproduce the original operating condition and compare positive fuel-trim correction, bank-specific versus shared airflow/fuel causes, unmetered air, exhaust oxygen intrusion, injector delivery, fuel pressure, and MAF/MAP plausibility with an independent physical or electrical measurement. If the scan value changes but the physical system does not, investigate sensor interpretation, control authority, or a mechanical restriction. If the physical system changes but scan feedback does not, investigate the sensing/reference path. If neither changes, prove power, ground, command, and prerequisite conditions before escalating to the controller. Document the before-and-after data so the repair is verified by evidence rather than by the temporary absence of a code.
P0174 QA case-pattern 8: Reproduce the original operating condition and compare positive fuel-trim correction, bank-specific versus shared airflow/fuel causes, unmetered air, exhaust oxygen intrusion, injector delivery, fuel pressure, and MAF/MAP plausibility with an independent physical or electrical measurement. If the scan value changes but the physical system does not, investigate sensor interpretation, control authority, or a mechanical restriction. If the physical system changes but scan feedback does not, investigate the sensing/reference path. If neither changes, prove power, ground, command, and prerequisite conditions before escalating to the controller. Document the before-and-after data so the repair is verified by evidence rather than by the temporary absence of a code.
P0174 QA case-pattern 9: Reproduce the original operating condition and compare positive fuel-trim correction, bank-specific versus shared airflow/fuel causes, unmetered air, exhaust oxygen intrusion, injector delivery, fuel pressure, and MAF/MAP plausibility with an independent physical or electrical measurement. If the scan value changes but the physical system does not, investigate sensor interpretation, control authority, or a mechanical restriction. If the physical system changes but scan feedback does not, investigate the sensing/reference path. If neither changes, prove power, ground, command, and prerequisite conditions before escalating to the controller. Document the before-and-after data so the repair is verified by evidence rather than by the temporary absence of a code.
P0174 QA case-pattern 10: Reproduce the original operating condition and compare positive fuel-trim correction, bank-specific versus shared airflow/fuel causes, unmetered air, exhaust oxygen intrusion, injector delivery, fuel pressure, and MAF/MAP plausibility with an independent physical or electrical measurement. If the scan value changes but the physical system does not, investigate sensor interpretation, control authority, or a mechanical restriction. If the physical system changes but scan feedback does not, investigate the sensing/reference path. If neither changes, prove power, ground, command, and prerequisite conditions before escalating to the controller. Document the before-and-after data so the repair is verified by evidence rather than by the temporary absence of a code.
P0174 QA case-pattern 11: Reproduce the original operating condition and compare positive fuel-trim correction, bank-specific versus shared airflow/fuel causes, unmetered air, exhaust oxygen intrusion, injector delivery, fuel pressure, and MAF/MAP plausibility with an independent physical or electrical measurement. If the scan value changes but the physical system does not, investigate sensor interpretation, control authority, or a mechanical restriction. If the physical system changes but scan feedback does not, investigate the sensing/reference path. If neither changes, prove power, ground, command, and prerequisite conditions before escalating to the controller. Document the before-and-after data so the repair is verified by evidence rather than by the temporary absence of a code.
P0174 QA case-pattern 12: Reproduce the original operating condition and compare positive fuel-trim correction, bank-specific versus shared airflow/fuel causes, unmetered air, exhaust oxygen intrusion, injector delivery, fuel pressure, and MAF/MAP plausibility with an independent physical or electrical measurement. If the scan value changes but the physical system does not, investigate sensor interpretation, control authority, or a mechanical restriction. If the physical system changes but scan feedback does not, investigate the sensing/reference path. If neither changes, prove power, ground, command, and prerequisite conditions before escalating to the controller. Document the before-and-after data so the repair is verified by evidence rather than by the temporary absence of a code.
Mechanic's Tip
Use the relationship between Bank 1 and Bank 2 fuel trims to decide whether the fault is shared or isolated.
Common Mistakes
- Replacing O2 sensors first
- Ignoring fuel trims
- Skipping smoke testing
- Overlooking bank-specific intake leaks
Tools Used During Diagnosis
- Professional scan tool
- Smoke machine
- Fuel pressure gauge
- Digital multimeter
Customer Explanation
Your engine is running lean on Bank 2, meaning there is too much air or not enough fuel reaching that side of the engine. Proper testing identifies the actual cause before parts are replaced.
Frequently Asked Questions
What does P0174 mean?
P0174 is System Too Lean (Bank 2). The monitor is focused on positive fuel-trim correction, bank-specific versus shared airflow/fuel causes, unmetered air, exhaust oxygen intrusion, injector delivery, fuel pressure, and MAF/MAP plausibility.
Does the code prove a part has failed?
No. It identifies a failed monitored relationship. Electrical integrity, physical system behavior, and sensor plausibility must be separated before parts are replaced.
Is it safe to drive with P0174?
Often driveable short-term, but sustained lean operation can increase combustion temperature and misfire while sustained rich operation can overheat the catalyst and dilute oil. A flashing MIL, severe misfire, fuel odor, or major power loss means stop driving.
What should be checked first?
Save freeze-frame and the complete scan, verify the exact system design by VIN, then reproduce the failure while comparing commanded data with actual electrical and physical response.
What freeze-frame clues matter most?
RPM, load, vehicle speed, coolant temperature, system voltage, fuel trims, pressure/airflow data, command state, and companion DTCs show whether the failure occurs at idle, startup, cruise, acceleration, deceleration, or high load.
What live data is most useful?
Graph positive fuel-trim correction, bank-specific versus shared airflow/fuel causes, unmetered air, exhaust oxygen intrusion, injector delivery, fuel pressure, and MAF/MAP plausibility plus system voltage, RPM/load, temperature, and relevant redundant or opposite-bank/cylinder data. Look for the first relationship that breaks.
Can another system create this code?
Yes. Shared voltage, airflow, fuel delivery, exhaust, vacuum, mechanical, or combustion faults can make the named monitor fail even when the named component is functional.
Should I replace the most common part first?
No. Common-failure statistics are useful for prioritizing inspection, not for skipping tests. Expensive or invasive parts should have at least two consistent forms of evidence.
When is professional equipment justified?
Enhanced graphing data and bidirectional controls are strongly recommended. Depending on the code, a pressure transducer/gauge, scope, current clamp, smoke machine, injector balance equipment, or compression/leak-down tools may be justified.
How do I verify the repair?
Repeat the original operating condition, confirm electrical and physical results agree, check current and pending codes, and complete enough of the drive cycle to show stable data and readiness progress.
Related Atlas Resources
Atlas Academy
Understanding Fuel Delivery Systems
Related Reference Chapters
Diagnostic Confidence
High
Related Codes
Project Atlas Feedback
Was this article helpful?
Needs Improvement
Working on this repair?
Create a professional estimate in minutes.
Why Trust This Guide?
Built by mechanics. Improved by mechanics.
This guide is maintained for working mechanics, mobile technicians, fleet maintenance professionals, and independent repair shops.