How to check FPV motor direction
TUNING // FIELD_REPORT

How to check FPV motor direction

Published
Updated
Read time4 min read

Checking FPV motor direction before the first hover: props off, Betaflight Motors tab, one motor at a time, compare with the diagram. A wrong direction is the classic "arms, then flips into the ground" failure on take-off.

FPV Grind's rule: never spin props on the bench to "see if it feels right". Direction is a configuration check, not a feeling.

Why direction matters

How to check FPV motor direction: Why direction matters

Each corner needs a specific spin direction so the motors' torque cancels out and the flight controller can steer. One reversed motor makes the quad tip, yaw wildly or flip the instant you add throttle.

Symptom on take-offOften means
Immediate flip into the floorA motor reversed, motor order wrong, or props on the wrong corners
Strong unwanted yawProps on the wrong corners
"Almost flies" but leans hardMixed-up directions or CW/CCW props

Check prop orientation (CW/CCW) once the motors are right: how to change props.

Safe check (Betaflight)

1. Props OFF - non-negotiable
2. Connect USB AND plug in a battery (motors won't spin on USB power alone)
3. Open Betaflight Configurator → Motors tab
4. Read the warning; enable motor test only when ready
5. Spin ONE motor at a low test value
6. Check it's in the right position AND spinning the right way per the on-screen diagram
7. Repeat for all four corners
8. Fix any problems, then re-test before the props go on

The diagram depends on Betaflight's Motor direction is reversed setting (Configuration tab), which switches between "props in" and "props out". Make sure it matches how your quad is meant to run.

Whoop-focused setup context: Betaflight setup tiny whoop first flight · Betaflight for beginners.

How to reverse a wrong motor

You typically have two tools:

MethodWhen to useNotes
Reverse in softwarePreferred: the Motors tab's motor direction tool (BLHeli_S / Bluejay ESCs with DShot), or an ESC configuratorClean; no soldering
Swap any two of the three motor wiresWhen software reverse isn't availableNeeds careful soldering

A motor that spins correctly but sits in the wrong position (e.g. M1 where M2 should be) is a motor order problem, not a direction problem. Fix it with Betaflight's motor remapping, or by moving the wires.

Soldering help: how to solder FPV motors · soldering pads without lifting traces. Mounting after swaps: how to mount whoop motors.

Props-on checklist (only after directions are correct)

How to check FPV motor direction: Props-on checklist (only after directions are correct)

□ All four directions match the diagram
□ Correct CW/CCW props on the correct corners
□ Motor screws tight; bells don't rub ducts or frame
□ No tools or loose screws on the bench under the props
□ First hover gentle, in open space, no spectators leaning in

Power-on habits: how to power on safely. On a bigger quad, follow first 10 flights after a new build.

Failure modes

MistakeOutcome
Props on during the motor testInjury risk; everything nearby gets shredded
Testing all motors at onceHard to see which corner is wrong
Reversing the wrong motor numberStill flips; now you're confused
Ignoring motor order (M1–M4)Directions look right but the quad still flips
Skipping the re-test after a fixAssumed fixed, still wrong

Vibration after a motor job is a separate issue: fix vibration. New motors: break-in guide.

India / whoop notes

Whoop AIO pads are small and tear easily, so use software reverse whenever your ESC supports it. Keep spare motors; crashes will use them: replace whoop motor · 0802 vs 1102.

Check motor and frame combinations in Grind Lab before you rebuild a corner with the wrong KV. Parts on the Bench. Practise recoveries on /sim so a bad take-off doesn't become a panic habit.

Bottom line

Props off → Motors tab → one at a time → match the diagram → reverse in software or swap wires → re-test → then props on. Direction checks take five minutes and save frames, fingers and ego.

See also

Discussion

Comments aren't open on this post yet. Share it with your build group, or start a thread on X.