A few days ago I had a crashed of my Octa Quad setup due to a failed motor. Post crash investigation showed that the motor failed during the previous flight and some combination of battery voltage, wind, and magic fairies kept the thing flying long enough to hover for about a minute in the subsequent flight before falling.
![](https://lh3.googleusercontent.com/-8ava1qHWC0g/VUO-YMd7mZI/AAAAAAAAANQ/Q_2fdZu-Ooc/s400/motor%2Bfailure%2Bduring%2Bdescent.png)
The RCOU log of the previous flight shows exactly where the motor failed on landing:
The bloom during descent is the Pixhawk maintaining stability after losing >50% lift on the right rear arm. The prop windmilled enough that I didn't notice it and some sort of intermittent connection made the spin check before the next flight look ok.
I'm considering adding a monitor to the RCOU in the pixhawk firmware that will send a motor failure warning over mavlink when the motor PWM shows that sort of split. Clearly the warning will also get triggered during hard yawing etc but the pilot will know about those events enough to ignore the warning. Can anyone think of an easier way to implement this?
Thanks,
--Caleb