--- PLEASE READ ALL INFO BELOW BEFORE POSTING! ---
I planned to perform a short GPS controlled high altitude flight, going straight up, and then straight down again.
When initating the descent, something did not work out as expected, and less than ten minutes later the hexacopter crashed because the failed descent attempts had drained the battery.
Technical explanation to what actually happened:
The GPS mode prioritized staying in place over descending. The winds were so strong that the engines had to work hard to keep the multirotor in place. When I told the multirotor to descend it basically said "I'm afraid I can't do that, because you told me to stay in this position, and if I slow down the motors to descend, I would also start moving sideways with the wind". The solution was to disengage the GPS mode.
Important background information:
This video depicts a very dangerous situation that could have ended up much worse than it actually did.
I was very lucky not to cause any damage on the ground to either living beings or property.
I am not proud of this particular flight, and my main reason for putting the video on YouTube is to inform others and hopefully help them avoid making the same mistake(s) I did.
My arguments for performing a high altitude flight at all were as follows: - No airplanes in this area ever fly as low as I did in the video - There is generally not much air traffic in this area at all - I checked with flightradar24.com before flying - Military, police, and emergency flights are virtually non-existant in this area - The multirotor was supposed to go straight up and straight down again
Knowing all of this, I still realize it was a mistake flying that high, especially on this particular occasion. The wind on the ground was not very strong, but higher up, the wind was so strong that the hexacopter had to struggle to stay in position. When I started descending, the hexacopter did not seem to respond to my command, and the only way to make it respond was to disconnect the GPS mode. It then started descending, but it also started moving away with the wind.
Facts to be noted before commenting on the video:
I DO NOT PERFORM HIGH ALTITUDE FLIGHTS ANYMORE, NOR DO I FLY OVER POPULATED AREAS. Hence, it is unnecessary to ask me to stop flying like I did in the video, since it definitely won't happen again anyway. The crash was a harsh wakeup call that totally made me rethink my attitude towards multirotor flying, and I realize now that high altitude flights and flights over populated areas are way too risky and dangerous.
THE MULTIROTOR DID NOT CAUSE ANY DAMAGE ON THE GROUND, TO EITHER PEOPLE, ANIMALS, OR PROPERTY. Having said this, I am fully aware that something disastrous could have happened, and there is no need to keep reminding me about that fact.
I WAS CONFIDENT THAT THE MULTIROTOR WOULD AUTOMATICALLY PERFORM A CONTROLLED LANDING IF THE BATTERY LEVEL REACHED ITS SPECIFIED MINIMUM. After reading the documentation, I felt reassured knowing that I had specified two battery level limits, where the second (lowest) limit, if reached, would initiate a forced automatic landing. Apparently this never happened, so this was either a misunderstanding on my behalf, or unclear documentation, or a combination of both.
Also, I do not live in the US, so the FAA will probably not be too interested in this flight.
My advice to any and all multirotor flyers out there: Never ever take any unnecessary risks. It is never worth it. I got away with it this time, but I could as well have ended up hurting or even killing someone on the ground.
00:00 - Ascent 01:09 - Through the clouds 02:20 - Above the clouds 03:10 - Problems start 04:07 - GPS disconnect 04:16 - Slow descent 05:18 - Return To Home activated 06:20 - Manual descent 07:47 - Below the clouds 08:05 - Batteries almost depleted 08:44 - Batteries die 09:12 - Aftermath 09:41 - Crash in slowmotion
