Skip to checklist
SpeedNeeds Diagnostics • Guide / Checklist

Start-to-Run Observation Checklist

Use this when the engine catches, fires, starts, stumbles, dies, or only stays running with help. Capture what happens from key release to run-loss before you choose the diagnostic branch.

Source QTS QTS-SYM-116

Core Truth

A start-and-die complaint is not the same as a crank-no-start complaint. The split happens in the first few seconds after catch, key release, throttle input, and module enable state. Guess that wrong and the whole test path gets crooked.

When To Use This

1 Starts Then Dies

The engine catches and runs briefly, then stalls immediately or shortly after key release.

2 Runs With Help

The engine will only stay alive with throttle assist, repeated attempts, added air, or careful pedal control.

3 Classification Is Fuzzy

The complaint is being called no-start, stall, security, idle, fuel, or ignition without clean first-observation proof.

The Rule

Do not jump straight to parts, fuel pressure, or idle components until the start-to-run event is named cleanly. First capture what the engine does at catch, what changes when the key leaves START, how long it runs, and whether throttle assist changes the outcome.

  • Observe the same start attempt from crank, catch, key release, and stall.
  • Record run duration in seconds, not vague words.
  • Separate “never caught” from “caught and lost run enable.”
  • Do not hold the throttle open blindly around unsafe evidence.
  • Stop the test if fuel leak, backfire, smoke, high RPM, or mechanical noise shows up.

Observation Checklist

Mark what you can prove from the start attempt. The point is to lock down the real question: did the engine fail to start, or did it start and then lose the ability to keep running?

  • Park/neutral confirmed, parking brake set, wheels clear, no one near belts, fans, tires, or exhaust.
  • Fuel leak, raw fuel odor, smoke, fire risk, or severe mechanical noise checked before cranking.
  • Scan tool, camera, helper, or notes ready before the attempt begins.
  • No catch, partial catch, single hit, normal catch, delayed catch, rough catch, or flare-up.
  • Starter sound is not engine run. Confirm the engine actually fired and carried itself.
  • Note whether catch happens every attempt or only after repeated cranking.
  • Dies exactly when key is released, stumbles after release, runs briefly, or keeps running until another condition changes.
  • Watch for dash/warning lamp behavior, relay click, power drop, or module reset at the same moment.
  • A stall at key release can point toward run-enable, ignition/run feed, security, or module state. Do not skip this split.
  • Instant die, less than 1 second, 1–3 seconds, 5–30 seconds, or longer than 30 seconds.
  • Duration matters because immediate run-loss and short-run stall are not the same diagnostic branch.
  • Use video if needed. Memory lies fast when the engine fires and quits.
  • No change, runs only with throttle, improves but still dies, flares too high, backfires, bogs, or stalls faster.
  • Throttle assist can separate idle air / airflow control from deeper run-enable, fuel, ignition, or security loss.
  • Do not force throttle assist if there is fuel spray, backfire, runaway RPM, severe knock, or unsafe movement risk.
  • Security lamp on, flashing, off, proves-out normally, or changes during crank/run/stall.
  • Battery, oil, MIL, theft, immobilizer, throttle, traction, or message-center warnings noted.
  • Indicator behavior is evidence. Do not erase it with a code clear before recording it.
  • Fuel leak, raw fuel flooding, backfire, smoke, fire risk, overheating, oil pressure concern, belt/fan hazard, runaway RPM.
  • Hard mechanical knock, grinding, starter hang-up, wiring smoke, arcing, hot cable, or battery distress.
  • Unsafe evidence changes the job from classification to containment.
  • No catch / crank-no-start.
  • Catches then dies at key release.
  • Starts then dies in 1–3 seconds.
  • Starts then dies after short run time.
  • Runs only with throttle assist.

STOP Lock The First Observation

Before you continue, write the start-to-run event in plain language. If you cannot write it, you have not classified the symptom yet.

Decision Gate

Pick the next move based on observed behavior, not the label someone gave the complaint.

No Catch

Route as crank-no-start. Do not call it starts-then-dies if the engine never carried itself.

Dies At Key Release

Focus on RUN-state power, run-enable, security, ignition feed, and module state splits.

Runs With Throttle

Check idle air, airflow path, throttle control, base air, vacuum leak behavior, and fuel response under controlled input.

Unsafe Evidence

Stop repeated attempts. Contain the hazard before more testing.

Safety Note

Do not keep cranking a vehicle that is leaking fuel, backfiring hard, smoking wiring, racing uncontrolled, or making severe mechanical noise. Use a helper, recorded data, safe stationary setup, and proper containment. Keep hands, clothing, tools, and leads away from belts, fans, exhaust, high current, fuel spray, and moving parts.

Final Call

The first few seconds tell you which road you are on. Catch it clean. Time it. Watch key release. Test throttle assist only when safe. Then pick the branch.

Better decisions start with better proof.

Get new drops in your inbox

Read the Privacy Policy.