Tuning after a crash
TUNING // FIELD_REPORT

Tuning after a crash

Published
Read time6 min read

A hard hit changes mechanics first — software second. Tuning over a bent motor is how pilots burn afternoons, cook ESCs, and convince themselves Betaflight "broke." The quad does not know it crashed; it only reads gyro noise and stick input. If the noise floor jumped because a bell is wobbling, every PID slider move is theater until something physical is fixed.

When NOT to tune after a crash

SituationDo this instead
Visible prop chip or bendNew props — always
Motor grit when spun by handBench or replace motor
Frame crack at arm rootRepair or replace arm — carbon stress
Loose camera / VTX mountTighten — jello is not PID
"It flies okay" but sounds differentInspect — okay is subjective

If inspection fails, do not arm for a tune session. Field crash repair triage first.

Inspect before sliders

Structured pass — five minutes saves an hour:

  1. Props — replace, do not straighten; compare blade length visually
  2. Motor bell — spin by hand; grind, click, or wobble = bench motor
  3. Motor base — screws tight; shaft should not pull in/out
  4. Frame — cracks at arm roots, loose standoffs, twisted plate
  5. Stack — FC still flat; soft mounts not torn
  6. Arms — length match left/right; not visibly bent
  7. Camera / vtx — mounts snug; antenna not cracked at solder
  8. Battery — no puff, connector strain, damaged wrap

See crash repair triage for field vs bench depth.

Smoke test: after motor swap or stack work, use smoke stopper habits — not full punch on first arm.

Bent shaft tell

SignMeaning
Gritty sound at low throttleBearing or shaft damage
Excessive heat vs other motorsFriction or imbalance
Visible bell gap or wobbleShaft bent or bell loose
Vibration only that cornerIsolate motor before PID
Prop track wobbles when spunShaft or prop seat

Do not "fix" with D-term — replace or rewind. Prop balancing does not fix bent steel.

Bench motor test (props off): spin each motor in configurator; swap suspect motor to another ESC output — problem follows motor = motor fault; stays on channel = ESC/solder. Five minutes beats PID roulette.

Symptom → action after crash

Symptom on first hoverLikely causeTune?
Immediate oscillationProp, motor, or loose mountFix hardware first
Buzz only mid-throttleBent shaft or ESC damageBench
Drift / wobble slowFrame twist or cam mountMechanical
Fine hover, bad in turns onlyMinor prop differenceLight filter check
Desync on punchESC hit or wire fractureElectrical inspect

Log in Blackbox only after mechanical pass — otherwise you tune noise.

When to re-tune lightly

Small changes — same airframe identity:

  • Same hardware, new props of similar load (same size/pitch family)
  • Minor arm replacement, stack untouched, same mount
  • Vibe slightly worse — check filters before PID
  • Camera angle changed slightly — may need rates tweak, not full PID

Workflow:

1. New props, tight bolts
2. Hover 1 pack — no aggressive tricks
3. If 90% same feel → fly session, note only
4. If buzz or heat → filters first, small steps
5. Log one maneuver if still off

When to reset or retune hard

Major changes — treat as partial new build:

  • New motor or ESC channel
  • FC replacement
  • Stack remounted with different soft mount — soft vs rigid
  • Mystery oscillation after multiple prop swaps
  • Frame plate or core replaced — resonance changed
  • Significant weight change (new VTX, GoPro mount)

Load a known baseline tune for your frame class, fly one pack, then Blackbox if still off. See Betaflight tuning basics order: mechanical → filters → P → I → D → FF.

Save profiles: export tune before crash day so you can compare to pre-crash baseline.

Props and load changes

Swapping from one 5" prop family to another changes amp draw and noise — not always "re-tune everything," but expect to revisit filters if:

  • Pitch jumped 2+ inches equivalent feel
  • Tri-blade → quad-blade
  • Heavier prop material

See motor KV and headroom if new props pin throttle.

ESC and electrical after impact

Crash impulse can crack FET legs or loosen battery pads. If one motor desyncs:

  • Inspect ESC channel solder
  • Swap motor to another output to isolate
  • Check ESC firmware only after hardware ruled out

Do not enable RPM filter to mask a damaged ESC channel.

Rates and feel after crash

Sometimes PID is fine but rates feel wrong after camera or radio bump. Check rates and expo before PID reset — especially if only "feel" changed, not oscillation.

India field note

Hard landings on concrete and dust infiltration are common — bearings fail faster when grit enters bell gaps. Carry spare props in field kit; motor spare if you fly remote spots.

Summer crashes on hot asphalt heat-soak motors before the next arm — cool before tuning or you chase heat noise.

Common mistakes

  • Straightening props with pliers
  • Adding D on a bent motor until ESC smokes
  • Full PID reset without fixing known crack
  • Skipping smoke stopper after stack knock
  • Tuning in front of spectators instead of inspecting

When to stop and bench

If two prop swaps and bolt check do not fix oscillation, stop flying that quad. Bench test motors individually, check FC gyro with props off (vibration on bench), swap known-good motor.

Returning to fly before structural fix risks LiPo damage in a tumbling crash — not worth the clip.

After crashTune action
Cartwheel, nothing bentFly, maybe note only
New props, same familyLight — filters if buzz
New motor or remounted stackBaseline reload
Arm/plate replacedPartial new build

Export tune before crash-heavy weekends — compare logs to saved profile before slider heroics.

Props-off bench spin: compare each motor sound in the configurator; swap suspect motor to another ESC output to isolate motor vs channel. Bent shafts often pass visual inspection but grind under load — trust hand-spin and hover vibe over optimism.


After a crash, the question is not "what PID?" — it is "what broke?" Fix that, hover gently, then tune only what the logs prove. Your pre-crash profile is the goal; random slider heroics are the detour.

See also

Discussion

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