P279B: Transfer Case Gear Low Incorrect Ratio
When the transfer case is in Low range the measured input/output speed ratio does not match the expected value.
What P279B means
P279B is a generic OBD-II powertrain code in the transmission group.
- Check engine light
- Usually on
- Emissions-related
- No
- Limp mode possible
- Not typical
- Drive cycle to clear
- Not required
Get it fixed
Post this code once and get quotes from local mechanics. Free to post.
Makes the repair and parts links below specific to your car. Kept in this browser only.
Common causes
- 01Stretched transfer case chainMost likely
- 02Worn planetary gear setPossible
Can I drive with P279B?
Usually yes, for a short time.
The car will often drive normally, but get it diagnosed soon. If you notice rough running, warning lights flashing, overheating or a burning smell, stop driving.
Why we rate it moderate
- Turns on the check engine light
Severity is our rule-based rating from the code’s flags in OBDex and the system it affects, not an inspection of your car. If the check engine light is flashing, or you notice overheating, low oil pressure, or brake or steering problems, stop driving and get help.
How to diagnose P279B
- 1
Confirm the code and save freeze-frame data
Read the codes with an OBD-II scan tool and note every code, not just P279B. Save the freeze-frame data (speed, load, temperature when the fault set) before clearing anything; it tells you when the fault happens.
- 2
Fix other faults first
If other codes are stored, start with power-supply, sensor-circuit and communication codes. They can cause this code as a side effect.
- 3
Test the circuit
Inspect the wiring and connector at the transfer case and planetary gear set for damage, corrosion or chafing. With a multimeter, check supply voltage, ground and signal against the specifications in the service manual for your vehicle.
- 4
Test the likely causes in order
Start with the most likely cause and work down: Stretched transfer case chain; worn planetary gear set. Test before replacing parts.
- 5
Check for recalls and service bulletins
Look up recalls for your exact vehicle with its VIN, and ask a dealer about technical service bulletins (TSBs). Manufacturers sometimes issue software updates or extended warranties for known faults.
- 6
Clear the code and verify the repair
After the repair, clear the code and drive the car under the conditions in the freeze-frame data to confirm it does not return.
P279B repair cost estimate
Estimate, not a quote. Labor times are typical ranges for this code from OBDex, and $125/hr is an assumed rate. Shop rates and labor times vary by vehicle and region. Diagnosis time may be billed separately.
- DIY difficulty
- Hard
- Good DIY job?
- Usually a shop job
Involved testing or major parts. Most owners use a shop.
Parts and systems involved
- Transfer case
- Planetary gear set
P279B FAQ
What does P279B mean?
P279B means “Transfer Case Gear Low Incorrect Ratio”. When the transfer case is in Low range the measured input/output speed ratio does not match the expected value.
Is P279B serious? Can I keep driving?
We rate P279B as moderate severity. Usually yes, for a short time. The car will often drive normally, but get it diagnosed soon. If you notice rough running, warning lights flashing, overheating or a burning smell, stop driving.
What causes P279B?
The most common causes, from most to least likely: Stretched transfer case chain; Worn planetary gear set. Test before replacing parts, because several causes can set the same code.
How much does it cost to fix P279B?
Typical labor is about $375–$1,000 at an assumed $125/hour shop rate, plus parts. That is an estimate, not a quote: labor times and rates vary by vehicle and region, and diagnosis may be billed separately.
Can I fix P279B myself?
DIY difficulty is hard. Most owners leave this to a shop because it needs involved testing or specialist tools. Always confirm the cause before buying parts.
Will P279B clear itself?
If the fault was intermittent, the warning may go off once the computer stops seeing it, but the code stays in memory. Fix the cause; clearing the code alone doesn’t repair anything.