KlooGee
First Officer
Flight distance : 16783757 ft
United States
Offline
|
Jurza,
I don't have an explanation for what caused the Yaw Errors that eventually forced it into ATTI mode. This is something I think you should open a ticket with DJI on. Maybe (or maybe not) they will conclude it is a warranty case and will provide a replacement for you. That part is hard to predict.
In regards to the footage, if you were recording and you have the cache turned on in DJI Go 4, then you may have the footage on your phone. I would check there. I think I can speak for most of us here that we would also be interested in seeing the footage from your phone.
In regards to recovering your aircraft, I think that is going to be difficult to predict where it ended up. The last recorded altitude was approximately 27m (88ft) high and moving at approximately 3.6m/s (8mph) and didn't show any signs of descending or slowing down. It was also at 73% battery, so it could have continued on this trajectory and altitude for quite some time. Not saying not to go look for it, just saying I won't even try to guess a projected search location.
In regards to the statements about the aircraft not responding once it was in ATTI mode, I agree with JJB. Looking at your logs, there is a very clear correlation to stick inputs and resulting aircraft movements. I think if you had some experience and knew to use the sticks to fly it home instead of trying to use RTH or the pause button while the aircraft was in ATTI mode, there is a much better likelihood of a positive outcome. In ATTI mode the aircraft was likely floating with the wind, but I think with positive stick inputs, the aircraft likely could have been directed to a more predictable landing zone.
As I mentioned before, I would suggest you open a ticket with DJI (if you haven't already) and supply them with the FlightRecord log so they can try to interpret the cause of the Yaw Errors that lead to this scenario.
Good luck!
|
|