QYS-ELEC-01 Crank-to-Run Feed Handoff Is Not Proven by Crank Fire

Why an engine that fires during crank can still lose the RUN-state power path the moment the key is released.

QYS IDQYS-ELEC-01
Build LaneElectrical Diagnostics / State-Change Feed Testing
System AreaELEC / Power Distribution / Ignition Feed / Relay Feed
What It Seems To Prove

The engine fired during crank, so power, fuel, ignition, and module feeds must already be present.

What It Actually Proves

The crank-state path worked long enough for combustion to begin. The run-state handoff may still be missing, weak, dropping out, or unable to carry current.

Purpose

This QYS exists to stop one of the nastier start-and-die assumptions: treating crank fire as proof that the electrical feed system is good.

Crank fire proves the engine received enough power, fuel, spark, and control permission during the START event to light off briefly. It does not prove the RUN feed survived the handoff after the key returned.

Core Idea

A vehicle can have one power path during crank and a different feed path during run. That split can hide a failure because the engine gives the technician a little reward before it quits.

What the symptom seems to prove: The system must have usable voltage because the engine fired.

What it actually proves: The START-state circuit carried the load briefly. RUN-state delivery still has to be proven at the exact transition point.

The diagnostic mistake is treating one state as proof for another. START power and RUN power are related, but they are not the same test.

Why This Matters In The Real World

In the bay, this failure wastes time because it feels like a fuel problem, an ignition problem, a theft problem, or a bad module depending on which symptom the tech grabs first.

The engine firing is real evidence, but it is limited evidence. The job is to catch what drops out when the system stops being cranked and has to live on the RUN feed.

What Is Actually Failing

The failure is usually in the handoff path that should keep the system powered after the crank request ends. That may be an ignition switch RUN contact, main relay contact, relay socket, fuse contact, module power feed, shared splice, coil feed, injector feed, PCM power feed, or ground return.

The part may not be fully open. It may carry enough current during a static check, pass a quick meter reading, or wake the module, then fold when load, heat, vibration, or contact resistance shows up during transition.

The Big Diagnostic Trap

The trap is checking key-on voltage or looking at crank fire and calling the feed proven. That is lazy evidence. It proves presence at one moment, not delivery through the handoff.

A meter can show voltage on an unloaded circuit while the circuit cannot feed a coil, injector bank, relay output, or PCM power leg when the load lands on it. Voltage seen is not voltage delivered.

The System Chain You Have To Think Through

You have to think through the full state-change chain, not just the component that looks guilty after the stall.

  • Battery and main distribution must stay stable during crank and release.
  • Ignition switch START and RUN outputs must both be identified, not blended into one assumed feed.
  • Main relay, ASD relay, EFI relay, or ignition relay output must remain alive after the crank request ends.
  • PCM power, module wake-up, coil feed, injector feed, and fuel pump run-enable must be checked during the actual transition.
  • Ground paths must be watched for rise or dropout while the loads are active, not just checked for continuity with the system asleep.

The handoff is the diagnostic event. Miss the event and the evidence turns into guesses.

Why This Gets Worse Under Real Conditions

This failure gets worse under real conditions because marginal contacts and weak feeds do not fail on command. Heat raises resistance. Vibration moves terminals. Relay contacts arc. Ignition-switch contacts wear. Fuse sockets loosen. Grounds shift when current demand changes.

A cold parked vehicle may fire clean. A hot restart, steering load, fan load, fuel pump load, or normal key-release movement may be enough to knock the RUN feed out. That is why a static test is too soft for this problem.

What This Failure Looks Like On The Vehicle

On the vehicle, crank-to-run feed handoff faults usually look like a clean start that refuses to stay alive.

  • Engine fires while the key is held in START, then dies as soon as the key returns to RUN.
  • Engine catches for one or two seconds, then loses spark, injector pulse, pump command, or PCM activity.
  • Fuel pressure, spark, or injector power appears during crank but disappears immediately after key release.
  • Modules wake up during crank but reset, drop communication, or lose enable state after the transition.
  • The failure may repeat hot, after vibration, after a key-cycle, or only when several loads are active.

That pattern does not automatically convict the fuel pump, ignition module, PCM, security system, or throttle body. It points to a state-change proof problem.

What A Good Tech Should Prove Instead

A good tech proves the power path in the state where the failure happens. For this asset, that means testing through crank, release, and RUN with the circuit loaded.

  • Measure START-state voltage at the affected feed while the system is cranking.
  • Measure RUN-state voltage at the same point after the key returns, without letting the load disappear from the test.
  • Check relay command and relay output separately so a clicked relay is not mistaken for delivered current.
  • Verify PCM power, coil feed, injector feed, fuel pump run-enable, and module grounds during the exact dropout window.
  • Load the suspect feed or ground path so hidden resistance cannot hide behind an open-circuit voltage reading.

The proof standard is not whether the circuit has voltage. The proof standard is whether the circuit can carry the required load through the START-to-RUN handoff.

The Field Rule

Crank fire proves crank-state delivery. It does not prove RUN-state feed integrity.

When the symptom happens at key release, the test has to happen at key release. Anything else is testing around the problem instead of through it.

Things Learned From This Asset To Stop Doing

  • Stop treating a brief engine fire as proof that power distribution is good.
  • Stop using static key-on voltage as proof of loaded RUN feed integrity.
  • Stop calling a relay good because it clicks during crank.
  • Stop replacing pumps, coils, modules, or throttle bodies before proving which feed disappeared.
  • Stop assuming START and RUN use the same electrical path without checking the diagram or the circuit behavior.

Things Learned From This Asset To Start Doing

  • Start separating START-state evidence from RUN-state evidence.
  • Start logging or watching voltage during the exact crank-to-run transition.
  • Start proving relay output, not just relay command.
  • Start testing coil, injector, PCM, module, and pump feeds under load after key release.
  • Start treating state-change failures as timing problems first and parts problems second.

Summary

Crank-to-run feed handoff faults fool techs because they give the engine just enough to fire. That short fire feels like proof, but it is only proof of the crank-state path.

The real question is what survives after the key releases and the system shifts to RUN. If the feed, relay output, module power, coil feed, injector feed, pump command, or ground path drops out there, the engine can start and still have no usable run path.

Do not let crank fire close the case. Catch the handoff under load and prove what the circuit can actually deliver when the vehicle asks it to stay running.