endotherm
First Officer
Flight distance : 503241 ft
Australia
Offline
|
This is either an incredibly funny thread or extremely tragic. alanrmx, you clearly do not read the posted replies carefully if at all, and you want to selectively choose the facts of your flight and want to make it fit in with what you think happened. This is a forum, where pilots and owners from around the world are invited to discuss problems like yours, in text and images. We offer advice and analysis for free out of the goodness of our hearts. Only a handful of people here are DJI employees.
The fact is you flew the aircraft to the limit of distance and altitude. You lost contact and you expected the RTH function to work, but it didn't come home, nor did it come back close enough to regain contact to resume control. We are with you up until that point. It is here that you fail to grasp the situation. You believe that if you lose contact or press the RTH button it will come back 100% of the time. This is not the case and it is not a fault. The button will not make up for pilot error or flying it beyond its capabilities. It has been pointed out that you were flying away with wind assistance, as seen in the flight log -- your speed is faster than the aircraft is capable of on its own. Now you want it to RTH while flying into a strong headwind. At best it will RTH automatically at around 10m/s, or if you are manually flying it in ATTI it can go a bit faster, around 15m/s. Because contact is lost you cannot take manual control, so you can not come back fighting a wind of 11m/s or more, you will never get any closer in wind of that speed. It will stay where it is, in RTH MODE, fighting the wind, then automatically land when the battery gets critical (the second level of safety after RTH was unsuccessful). Look at the last position on the map and go there, you will find the aircraft landed on the ground nearby. An experienced pilot knowing he was in trouble at that altitude and distance would have come back sooner or at least had the sense to descend to a lower altitude where the wind could be expected to be weaker, then fly closer and regain contact. If the wind was more like 20m/s or even more, which is highly possible at that altitude you will find that the wind is pushing it away further, even though it is trying to fly in the opposite direction back towards you. To you that might be a flyaway but it is being blown away. It may have flown flawlessly on other days, but on this occasion you were fighting a stronger wind than the aircraft can overcome, so you lost it due to wind. You never tried flying back to you when you did have control, so you have no idea if you could overcome the wind when it was time to return. Flying out in those conditions shows you had no regard for the conditions or even knowledge of the wind speeds and capability of the aircraft. Having a warning at 70% battery and a low-battery return home notice pop up is pretty good proof that the system knew it was carried away from you in high wind, and would need 3/4 of the battery charge to come back, ASSUMING IT HAD ENOUGH STRENGTH TO OVERCOME THE HEADWIND WINDSPEED, a fact you conveniently ignore each time. Just like driving a car, reverse gear might be able to return you to a safe part of the road if you drive into trouble, but it won't do you a lot of good if you drive off a cliff and gravity takes over. Gravity will win over your reverse gear every time, it's just physics. This is all from your flight data, we are not making anything up. We have nothing to gain or lose from independently and impartially analysing the data. You clearly have nothing new to add, or you would have offered it by now. You are just not willing to face the truth and accept it was your fault. |
|