Kloo Gee
Captain
Flight distance : 16641309 ft
United States
Offline
|
I have looked into quite a few log files in the recent weeks and most of them that have all Yaw Errors in them have 1 thing in common. Very strong winds recorded for the flight times.
This log is a little tougher to analyze because the log doesn't contain any values for the RC stick inputs at all. Because of this, it isn't possible to determine what pilot inputs had on the flight path, so some guesstimating needs to be taken into account.
Having said that, I really think the wind played a very big factor in this flight. Firstly, the regional weather report is showing the wind speed at around a steady 20mph (maybe slightly under).
.
That is a very stiff wind. Looking at the area of the flight via Google Maps & Earth, it appears to be a hilly area with valleys running through it. Wind speeds in these type of geographic elements can be greatly affected by the terrain with localized wind speeds that can be both far greater and far lower than the overall regional wind speeds due to the way the wind is funneled around and over the terrain.
Like I said, without the RC input values in the log files, it is impossible to tell what inputs the pilot made during the flight and what influence those inputs had on the flight path. However, we can see in the flight path, that it appears that even after the aircraft went into ATTI mode, it *appears* that the pilot had enough control of the flight to circle it around into the wind and bring it from about 80 ft away to about 19 feet away. This happened from 0:22.2 to 0:34.8 into the flight.
Only a couple seconds later (at 0:36.5), the controlling device lost connection with the aircraft at only a distance of 42ft away and 52ft up. When the connection was restored 6 seconds later, the aircraft was already 195ft way and increasing its speed away from the home point until the connection was permanently lost 2 seconds later at a distance of 242 feet away moving at a rate of about 17mph.
My guess is that a wind gust was likely responsible for putting the aircraft into a situation it wasn't able to cope with (could be exceeding design limitations or could be a bug, impossible for me to say) and as such caused the Yaw Errors which eventually put it into ATTI mode.
My recommendations:
- Open a case with DJI support to see if they can figure out why the Yaw Error occurred in the first place.
- don't fly in high winds where you could be potentially putting the aircraft near its limitations
- if you do fly in windy conditions, fly INTO the wind so that if something happens, the wind will blow it back to you (instead of away from you) and give you more time to react.
- If it goes in ATTI mode, start losing elevation fast if there aren't obstacles (such as trees or buildings) to crash into. Also crashing into those objects may be preferable to keeping it at current elevation and watching it fly away.
Maybe I missed it, but were you using the Spark's RC or just controlling via your phone?
I wish you the best of luck in a positive resolution to your case.
|
-
|