Hi
So I've had my Mavic Air for about 5 days now. Due to weather and work I haven't been able to fly it in the daylight 'till this weekend. Everything was fine at the local park on Friday. But today I took it out to the cliffs above Palos Verdes and almost had a couple of heart attacks when things went a little weird. I'm sure some of it is just me getting used to things. But I wanted to check in and see if people had any comments about why I could do to make something like this not happen again.
My starting point on the cliffs was at least 300ft, maybe 500ft above the water. On my first flight everything was fine, I raised up 200ft above my starting point and headed out towards the water. Flew around for about 10 min or so, then hit the return to home button (the app said that the starting point was recorded at the beginning of the flight). I couldn't see the drone as it was too far out and the sun was low and making things difficult. Watching the screen I could see the drone descending, but not coming towards me. Then the descent started going into the negative numbers, so it was below me. Once it went 20ft below me I canceled the return to home. Using the display it took me about 5 min to orient myself and figure out where the drone was relative to me. Then I raised up about 100ft above me and flew it back manually.
Why did the drone go to an altitude below its starting point? That just seems wrong to me. A good way to loose signal contact with the remote and make it more difficult to manually fly the drone back. I had the return to home altitude set to 30m. Maybe I incorrectly assumed that that meant 30m above its starting point? Did I do something wrong? Should I have trusted the flight algorithms on the device?
My second moment of difficulty came with a new battery and I flew about 1000ft away from my starting point and almost 300ft above. Flying around and recording video I say a couple of screen freeze ups but they were short lived and didn't freak me out too much. But then the screen went black! I couldn't see the drone with my eyes and the app just crapped all over itself. A few seconds later it came back, maybe 10 - 20, but it felt much longer. I immediately hit return to home with my heart pounding. And it wanted to confirm that I wanted to land immediately right there 1000ft away. WTF! It forgot where my starting point was. I guess the app restarted and didn't record the starting point to disk (how flippin' dumb is that). Luckily the display became active again and it only took me a moment to orient myself this time and I manually returned to home. At this point I had had enough and packed everything up and went back home.
Is the screen going black like that and loosing the starting point a common occurrence? Is there something I should have done differently to prevent these kinds of mishaps????
Thanks, Derek
So I've had my Mavic Air for about 5 days now. Due to weather and work I haven't been able to fly it in the daylight 'till this weekend. Everything was fine at the local park on Friday. But today I took it out to the cliffs above Palos Verdes and almost had a couple of heart attacks when things went a little weird. I'm sure some of it is just me getting used to things. But I wanted to check in and see if people had any comments about why I could do to make something like this not happen again.
My starting point on the cliffs was at least 300ft, maybe 500ft above the water. On my first flight everything was fine, I raised up 200ft above my starting point and headed out towards the water. Flew around for about 10 min or so, then hit the return to home button (the app said that the starting point was recorded at the beginning of the flight). I couldn't see the drone as it was too far out and the sun was low and making things difficult. Watching the screen I could see the drone descending, but not coming towards me. Then the descent started going into the negative numbers, so it was below me. Once it went 20ft below me I canceled the return to home. Using the display it took me about 5 min to orient myself and figure out where the drone was relative to me. Then I raised up about 100ft above me and flew it back manually.
Why did the drone go to an altitude below its starting point? That just seems wrong to me. A good way to loose signal contact with the remote and make it more difficult to manually fly the drone back. I had the return to home altitude set to 30m. Maybe I incorrectly assumed that that meant 30m above its starting point? Did I do something wrong? Should I have trusted the flight algorithms on the device?
My second moment of difficulty came with a new battery and I flew about 1000ft away from my starting point and almost 300ft above. Flying around and recording video I say a couple of screen freeze ups but they were short lived and didn't freak me out too much. But then the screen went black! I couldn't see the drone with my eyes and the app just crapped all over itself. A few seconds later it came back, maybe 10 - 20, but it felt much longer. I immediately hit return to home with my heart pounding. And it wanted to confirm that I wanted to land immediately right there 1000ft away. WTF! It forgot where my starting point was. I guess the app restarted and didn't record the starting point to disk (how flippin' dumb is that). Luckily the display became active again and it only took me a moment to orient myself this time and I manually returned to home. At this point I had had enough and packed everything up and went back home.
Is the screen going black like that and loosing the starting point a common occurrence? Is there something I should have done differently to prevent these kinds of mishaps????
Thanks, Derek