FPV motors hot after a flight: what's normal and the three settings that cause it
Short answer: FPV motors should come down warm, not hot. Unplug the battery and touch each motor bell. If you can hold a finger on it for a few seconds, it's normal. If you flinch, find the cause before the next pack: first the props and motors themselves, then three settings, D-term gain, filtering and ESC motor timing.
Heat is wasted power. A motor that runs hot is either working against something mechanical or being told to make thousands of tiny corrections that don't move the quad but do warm the windings.
The touch test, done safely
1. Land and disarm
2. Unplug the battery (always, before your fingers go near props)
3. Touch each motor bell within about 30 seconds of landing
4. Compare: all four the same? One hotter than the rest?| What you feel | What it means |
|---|---|
| Warm, about like a cup of tea you can hold | Normal |
| Hot, but you can keep a finger on it for a few seconds | Fine on a hot day or after a hard pack; keep an eye on it |
| Too hot to touch | Stop flying and find the cause |
| One motor much hotter than the others | Mechanical problem on that corner |
| All four too hot | Settings, prop load, or heat soak from back-to-back packs |
Too much heat for too long can weaken the motor's magnets and burn through the thin enamel on the windings, which ends in a shorted, dead motor. On Indian summer afternoons, start cooler: rest packs and quad in the shade between flights (see filter tuning for hot climates).
Mechanical first: one hot motor
If only one motor is hot, don't touch your tune. Settings act on all four motors at once, so a single hot one points at hardware.
- Swap the prop on that corner for a new one. A slightly bent or chipped blade shakes the motor all flight.
- Spin the motor by hand. It should turn smoothly and freely. Gritty or notchy means a worn or dirty bearing.
- Check the shaft. Look along it while you spin it; a wobble means a bent shaft after a crash.
- Check the screws. A motor screw that's too long can touch the windings; a loose one lets the motor rock.
- Check the phase wires and solder joints for nicks or a cold joint, especially near the arm.
Our vibration guide covers each of these in more detail. New motors on their first packs? See breaking in new motors.
All four hot: the three settings
When every motor comes down hot and the hardware checks out, the cause is usually one of these. Change one thing at a time, fly a pack, and touch the motors again.
1. D-term gain too high
D-term damps fast movement, which is why it fights propwash and bounce-back. But it reacts to rate of change, so it also amplifies gyro noise, and the motors turn that noise into heat. High D is the most common software cause of hot motors.
| Sign | Try |
|---|---|
| Motors hot, quad flies fine | Lower D (or the D-term slider in Betaflight) one step and re-test |
| Motors hot and you hear a fine buzz or grind | Lower D and check filtering (below) |
| You raised D to fix propwash | Undo it and work through propwash tuning properly |
2. Filtering too light (or RPM filter off)
Filters remove noise before the PID loop sees it. Push the gyro or D-term filter sliders too far towards "less filtering" and the noise reaches the motors.
- RPM filtering is the best single tool against motor noise, and it needs bidirectional DShot on ESC firmware that supports it. If it's off, turn it on: RPM filter and bidirectional DShot.
- If you moved the filter sliders for a "locked in" feel, bring them back one step at a time towards the defaults.
- Not sure where the noise is? A Blackbox log shows it plainly: reading Blackbox without drowning.
3. ESC motor timing set too high
ESC firmware (BLHeli_S, Bluejay, BLHeli_32, AM32) lets you set motor timing. Higher timing can give a little more top end, but it also makes motors run hotter. If someone bumped it up, or a preset did, put it back to the firmware's default or a middle setting and compare. More on ESC firmware: BLHeli_32 vs AM32.
Not a setting: too much load
Motors also run hot when they simply work too hard:
- Props too big or too aggressive for the motor's KV and battery. See motor KV and prop size.
- A heavy quad that hovers at high throttle: a big battery or a GoPro on a small build.
- Back-to-back packs with no cool-down: motors never return to air temperature, so each pack starts hotter.
Quick map
| You notice | Check first | Then |
|---|---|---|
| One motor hot | Prop on that corner | Bearing, shaft, screws, wires |
| All hot, flies well | D-term gain | Filter sliders, RPM filter |
| All hot, buzzing sound | Filtering, RPM filter | D-term gain |
| Hot only on summer afternoons | Cool-down between packs | Slightly more filtering |
| Hot after changing props | Prop size and pitch vs KV | ESC motor timing |
| Hot after loading a preset | Compare the preset's D and filter values to your old ones | ESC motor timing |
Before you fly again
- Fix the mechanical issue, or change one setting.
- Fly one calm pack.
- Unplug and do the touch test.
- Repeat until all four motors come down just warm.
New to tuning? Start with Betaflight tuning basics, and practise the moves free in the FPV Grind sim while your motors cool.
FAQ
- How hot is too hot for FPV motors?
- Warm after a pack is normal. Unplug the battery, then touch each motor bell: if you can keep a finger on it for a few seconds, you are fine. If you have to pull away straight away, something is wrong, and flying on can weaken the magnets and burn the enamel on the windings.
- Why is only one motor hot?
- One hot motor is almost always mechanical: a bent prop, a bent shaft, a worn bearing, a loose motor screw or a damaged phase wire on that corner. Swap the prop first, then spin the motor by hand and feel for roughness. Settings affect all four motors together.
- Does too much D-term make motors hot?
- Yes. D-term reacts to fast changes, so it amplifies gyro noise and sends it to the motors as tiny rapid corrections you can't see but the motors turn into heat. High D with light filtering is the most common software cause of hot motors.
Discussion
Comments aren't open on this post yet. Share it with your build group, or start a thread on X.