
Crash repair triage, fix now vs bench later
Every pilot eats dirt eventually. The goal after a crash isn’t heroics; it is triage: fly again safely if you can, or stop before a small problem becomes a fire. Good triage is a decision tree, not optimism.
First 30 seconds

- Disarm, and unplug the battery as soon as you reach the quad.
- Mind the props when you pick it up; bent or broken blades cut fingers.
- Sniff test: a hot, sweet electronics smell means stop. No "one more pack."
- Look it over: cracked arm, snapped VTX antenna, dangling camera, punctured battery.
If the pack is puffy, torn or getting hot, retire it; see LiPo safety.
Your quad might be fine; your finger might not be if you grab it carelessly. Disarm, unplug, then handle it. Tell spectators the same if they help retrieve it.
Field fixes (usually worth it)
| Damage | Field fix? | Notes |
|---|---|---|
| Bent prop | ✅ | Swap it; spin the motor by hand afterwards |
| Camera knocked out of angle | ✅ | Re-tighten; check the lens for cracks |
| VTX antenna bent | 🔶 | Straighten gently; replace if the core is exposed |
| Hairline arm crack | ⬜ | Tape to get home only; replace the arm |
| Motor bell wobble | ⬜ | Bent shaft or bearing; bench later |
| Stack screw pulled out | 🔶 | Swap the standoff if you carry spares |
Carry props, zip ties, hex keys, and a multimeter in your field repair kit.
Prop swap nuance
Match the prop direction when swapping a single prop. Spin the motor by hand afterwards: grinding or roughness means bearing damage or debris in the motor, not a prop problem. Also check the motor wires and connectors.
VTX antenna triage
Straighten it gently if the lead isn’t kinked. If the inner wire is exposed at the tip, replace the antenna before powering up. Running a VTX without a proper antenna can damage it.
Bench-later list
- Motors that grind, stutter, or wobble when spun by hand
- ESC that smells hot after a hover test on the bench
- FC with lifted pads or a cracked USB socket (soldering repair needs good light and time)
- Frame with delaminated carbon or several arm cracks
- Receiver or VTX with an intermittent link after an antenna hit
Carbon and structure
A hairline arm crack isn’t a field fix beyond getting home. Read carbon splinters and stress cracks; flying a cracked arm is how stacks get destroyed.
Electrical bench signs
| Symptom | Likely cause |
|---|---|
| One motor stutters | ESC, motor, or motor wire |
| All motors twitch | FC or power path |
| No image after a hit | Connector, VTX, camera cable |
| Link drops at certain angles | RX antenna or its lead |
Power path inspection
Crashes stress connectors and battery leads. Before you plug back in:
- Is the connector undamaged and seating fully?
- Are the battery-lead joints on the ESC solid?
- Is the battery strap clear of the props?
Hover test discipline
After any field repair:
1. Props off: plug in, arm briefly, check every motor spins the right way
2. Props on, quad on open ground, you well back
3. Short hover at knee height; listen for vibration
4. Land after 30 seconds and feel the motorsIf something feels wrong on the first pack, land. Tuning won’t fix a bent motor.
A clean hover confirms basic function, not that the quad is ready for bando. If there is new vibration in the hover, take it to the bench before you fly hard again.
When to retire the session
- The same arm keeps breaking (the frame may be done)
- An electrical smell comes back after cooling
- Rain or mud inside the stack: dry it fully before powering up, ideally for a day (monsoon habits)
One bent prop: swap, hover, maybe continue. Any repeated electrical smell: session over.
Triage after minor vs major hits

| Hit type | Typical safe path |
|---|---|
| Grass cartwheel | Props; inspect arms |
| Caught in a tree | Antenna, arms, motor bells |
| Concrete or metal | End the session; full inspection |
| Punctured battery | Retire the pack immediately |
Slow down
Adrenaline makes you plug in again too fast. Sit down, drink some water, and run the 30-second checklist. The quad can wait. Pilots who rush triage fly on cracked arms, then blame luck.
If the camera survived, check the DVR before the next flight; impact footage shows which arm hit first. Blackbox logs help with electrical problems that felt like a "weird desync."
Note what broke each time (arm, motor, VTX, connector). Over a season, the pattern shows your frame’s weak points and which spares to carry.
India field notes
Quads parked in hard sun after a repair run hot; let the ESC cool before the hover test. Summer heat exposes marginal ESCs. Spare arms in the car beat waiting for an import, so restock from the Bench during the week.
If you are debating whether an arm is fine, it isn’t fine enough for freestyle. Replace it or bench it. Social pressure to keep flying is how fires happen.
Decision tree (field use)
Crash → disarm, unplug, sniff test
├─ Battery damaged? → retire the pack, inspect the quad
├─ Hot electrical smell? → session over; bench the power path
├─ Bent prop only? → swap, hover test, maybe continue
├─ Visible arm crack? → get home, replace the arm
├─ Motor grinds by hand? → bench the motor; don’t fly hard
└─ All clear and a clean hover? → one easy pack, then normal flyingIf the quad feels different over the next two packs even after a clean hover, read tuning after a crash before touching PIDs.
Field kit minimum
| Carry | Why |
|---|---|
| Spare props | First swap on any hit |
| Hex keys | Motor and camera screws |
| Zip ties | Temporary antenna or arm hold |
| Multimeter | Continuity and short checks when something dies |
No spare props in the bag means triage ends with carrying the quad back to the car.
Bench
- Propellers: the first swap after any hit
- Frames: arms when hairlines show
- The Bench: whoop props, ducts, screws, VTX antennas and other consumables
See also
- Building a field repair kit, what to carry for real field days
- Soldering ESCs and pads without lifting traces, bench repairs after a bad hit
- Connector guide: XT60, XT30, PH2.0, BT2.0, power joints that fail in crashes
Discussion
Comments aren't open on this post yet. Share it with your build group, or start a thread on X.