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
| Situation | Do this instead |
|---|---|
| Visible prop chip or bend | New props — always |
| Motor grit when spun by hand | Bench or replace motor |
| Frame crack at arm root | Repair or replace arm — carbon stress |
| Loose camera / VTX mount | Tighten — jello is not PID |
| "It flies okay" but sounds different | Inspect — 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:
- Props — replace, do not straighten; compare blade length visually
- Motor bell — spin by hand; grind, click, or wobble = bench motor
- Motor base — screws tight; shaft should not pull in/out
- Frame — cracks at arm roots, loose standoffs, twisted plate
- Stack — FC still flat; soft mounts not torn
- Arms — length match left/right; not visibly bent
- Camera / vtx — mounts snug; antenna not cracked at solder
- 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
| Sign | Meaning |
|---|---|
| Gritty sound at low throttle | Bearing or shaft damage |
| Excessive heat vs other motors | Friction or imbalance |
| Visible bell gap or wobble | Shaft bent or bell loose |
| Vibration only that corner | Isolate motor before PID |
| Prop track wobbles when spun | Shaft 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 hover | Likely cause | Tune? |
|---|---|---|
| Immediate oscillation | Prop, motor, or loose mount | Fix hardware first |
| Buzz only mid-throttle | Bent shaft or ESC damage | Bench |
| Drift / wobble slow | Frame twist or cam mount | Mechanical |
| Fine hover, bad in turns only | Minor prop difference | Light filter check |
| Desync on punch | ESC hit or wire fracture | Electrical 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 offWhen 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 crash | Tune action |
|---|---|
| Cartwheel, nothing bent | Fly, maybe note only |
| New props, same family | Light — filters if buzz |
| New motor or remounted stack | Baseline reload |
| Arm/plate replaced | Partial 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.
Discussion
Comments aren't open on this post yet. Share it with your build group, or start a thread on X.