AutoLogicTools

OBD-II trouble code

P0919: Gear Shift Position Control Error

The module commanded a gear and the shift rail did not arrive. On the fore-and-aft axis that means the dog teeth failed to mesh — and tooth-on-tooth block-out is a normal transient event, so the diagnosis here starts with how often it happens, not with which part to buy.

High severityPowertrainTransmission / Shift ControlDo not drive

Quick facts

System
Powertrain
Category
Transmission / Shift Control
Severity
High severity
Drivable
No — stop driving until repaired
Repair cost range
$90$5,200
DIY difficulty
Shop recommended

What does P0919 mean?

P0919 is not a circuit code. It is the transmission control module reporting an outcome: it asked the shift mechanism to move to a particular gear position, it watched the position feedback, and the mechanism did not get there within the time and tolerance the strategy allows. Nothing in that description says which component failed, and that is the point — the module has detected a result, not a cause.

On the fore-and-aft shift axis the physical meaning of that result is specific and worth understanding, because it changes how seriously a single occurrence should be taken. This axis engages by pushing a sliding sleeve's dog teeth into the corresponding teeth on the gear. Those teeth have to line up in the gaps between each other. When they arrive face to face instead — tooth on tooth — the sleeve cannot advance, and the mechanism is blocked until relative rotation moves the teeth a few degrees and a gap opens. Every driver who has ever pushed a manual gearlever into second, felt it refuse, and had it slide home a moment later has experienced exactly this. It is a normal transient event, not a failure. The module, however, has no way to distinguish one from the other: all it knows is that the gear it commanded did not arrive in the time allowed. A single P0919 stored after a hard cold shift can therefore be a non-event, and diagnosis should begin by establishing frequency and circumstances rather than by ordering parts.

When the code is genuinely recurring, the most valuable piece of evidence is which other codes are stored with it. If P0919 sits alongside gear shift position circuit codes, the module's information about where the rail is was unreliable, and the electrical side deserves attention first — the mechanism may have arrived perfectly well and simply not been seen to. If P0919 is stored alone, with clean position circuits and clean actuator circuits, the position sensor is reporting truthfully that engagement genuinely did not complete. That moves the job squarely into mechanical territory: a worn or bent selector fork, a tired synchroniser, a rail binding in its bushings, or a clutch that is not releasing fully and is leaving the gearset loaded so the teeth cannot align. Reading the code list before touching anything is what separates those two very different jobs.

One no-parts cause is worth ruling out early because it is common and cheap. The engagement end positions on these transmissions are learned values, not fixed ones, and they are stored per gear. After a clutch replacement, a gearbox repair, a mechatronic swap or a battery disconnection on some designs, those learned values can be stale or absent, and the module will judge a perfectly correct engagement as a failure to arrive. Running the shift adaptation procedure and retesting costs an hour and resolves a genuine share of these cases outright.

Common causes

  • Tooth-on-tooth block-out preventing the sleeve from advancing
  • Worn or bent selector fork failing to push the sleeve fully home
  • Worn synchroniser cone unable to match speeds before engagement
  • Clutch not releasing fully, leaving the gearset loaded
  • Shift adaptation values stale or missing after previous work
  • Shift rail binding in worn or contaminated bushings
  • Weak or slow shift actuator failing to complete travel in time
  • Incorrect or degraded transmission fluid altering synchroniser behaviour
  • Gear shift position sensor misreporting an engagement that did occur
  • Internal mechanical damage to the sleeve or gear dog teeth

Symptoms

  • Occasional refused gear engagement followed by a successful retry
  • Crunch or knock during engagement
  • Transmission dropping to neutral instead of taking the requested gear
  • Warning lamp with a transmission fault message
  • Longer than normal pause between gear request and drive
  • Complaint worse on cold starts and improving with temperature
  • Repeated engagement attempts audible from the transmission
  • Fault recorded once with no driver complaint at all
  • Additional shift position or actuator codes stored alongside
  • Progressive worsening from occasional to frequent over time

Diagnostic steps

  1. 1.Establish frequency and circumstances first, because an isolated occurrence after a hard cold shift can be a normal tooth-on-tooth block-out rather than a fault.
  2. 2.Scan every module and list all stored codes before clearing anything, since what accompanies P0919 determines whether this is an electrical or a mechanical job.
  3. 3.If shift position circuit codes are present, diagnose those first — the mechanism may have engaged correctly and simply not been observed to.
  4. 4.If P0919 stands alone with clean circuit codes, treat the position feedback as truthful and plan a mechanical investigation.
  5. 5.Confirm the shift adaptation values are current and run the adaptation procedure, particularly if the fault followed clutch, gearbox or mechatronic work.
  6. 6.Verify clutch release is complete, because a dragging clutch keeps the gearset loaded and prevents the dog teeth from aligning.
  7. 7.Check transmission fluid level and specification, since the wrong fluid changes synchroniser behaviour directly.
  8. 8.Record which gears are affected — one gear implicates that gear's fork, sleeve or synchroniser, while all gears implicate the actuator, the clutch or the adaptation.
  9. 9.Log commanded versus reported shift position through several engagement attempts to see how far short the mechanism stops.
  10. 10.Only after adaptation, clutch and fluid have been ruled out, plan internal inspection of the fork, sleeve and synchroniser for the affected gear.

Repair cost

$90$5,200

A shift adaptation reset where stale learned values are the cause is $90 to $250, and it is worth attempting first because it resolves a real share of these cases outright. Diagnosis otherwise is $150 to $450. Correcting fluid level or specification is $150 to $450. Clutch replacement on an automated manual or dual-clutch, where incomplete release is the cause, is $1,200 to $3,400. Selector fork, sleeve or synchroniser repair requires the transmission to come out and runs $1,800 to $5,200 depending on how many gears are involved and whether the unit is repaired or exchanged. The wide range is honest rather than evasive: this code names an outcome, and the outcome has causes at both ends of the price scale.

Estimate your repair

Run the numbers for your vehicle

Open the Repair Cost Estimator with automatic transmission rebuild or replacement preselected. Adjust labor rate and vehicle category to fit your situation.

DIY vs shop

Leave this one to a qualified shop. It typically involves emissions-critical components, refrigerant handling, or other work that requires manufacturer-grade tooling, training, or certification. DIY attempts often produce a more expensive problem than the original code.

Related codes

Frequently asked questions

Can a single P0919 be nothing at all?

Yes, and it is one of the few transmission codes where that is a reasonable first hypothesis. The shift axis engages by pushing dog teeth into the gaps between the matching teeth on the gear. When those teeth arrive face to face instead, the sleeve cannot advance until a few degrees of relative rotation opens a gap — the same event a manual driver feels when a gearlever refuses second and then slides in a moment later. It is normal mechanics. The module cannot tell that transient apart from a real failure; all it sees is a commanded gear that did not arrive in the time allowed. So one occurrence after a hard cold shift means considerably less than a pattern of them, and establishing frequency is the correct first step.

What do the codes stored alongside P0919 tell me?

They tell you which half of the problem you are in, and it is the most valuable free information available on this code. If gear shift position circuit codes are stored with it, the module's picture of where the rail was sitting was unreliable — the mechanism may have engaged perfectly well and simply not been seen to do it — so the electrical side comes first. If P0919 is stored on its own with clean circuit and actuator codes, the position sensor is reporting truthfully that engagement really did not complete, and the job is mechanical: fork, sleeve, synchroniser, rail or a clutch that is not fully releasing. Scanning everything before clearing anything is what makes that distinction possible.

Why would adaptation fix this?

Because the engagement end positions on these transmissions are learned rather than fixed, and they are stored gear by gear. The module knows where a properly engaged third gear puts the rail because it learned it, not because a number was cast into the housing. After a clutch replacement, gearbox repair, mechatronic swap or in some cases a battery disconnection, those learned values can be stale or missing, and the module will then judge a completely correct engagement as a failure to arrive. Running the shift adaptation procedure and retesting takes about an hour, costs a fraction of any mechanical repair, and resolves a genuine proportion of these cases without a single part being fitted.

Can I keep driving with P0919?

Not once it is recurring. An automated manual or dual-clutch transmission has no torque converter and no hydraulic limp-home gear, so a failed engagement leaves it in neutral rather than in a reduced drive mode, and that can happen while pulling out or mid-overtake. There is a mechanical cost argument too: every failed engagement attempt hammers dog teeth that may already be worn, and letting that continue converts a synchroniser and fork repair into a gearset replacement. If a single occurrence was recorded, the fault cleared and it has not returned, monitoring is reasonable — a pattern of them is not.

Editorial context

About This Diagnostic Information

AutoLogicTools diagnostic guides explain OBD-II trouble codes using recognized code definitions, standard automotive diagnostic principles, and practical automotive context. A trouble code records a condition detected by a control module. It does not automatically identify a failed part, and the right diagnostic procedure can vary by vehicle.

Manufacturer service information, technical service bulletins, wiring diagrams, and vehicle-specific procedures should take precedence when available.

AutoLogicTools was founded by Vincent Fisk, an automotive locksmith and shop owner in San Diego with hands-on experience in vehicle keys, immobilizer systems, electrical issues, modules, programming, and diagnostics.