The drone and pilot that collided with an Army Helo back on Sep 21st have been identified. Full story at https://arstechnica.com/tech-pol ... -1-5-dent-in-rotor/

Takeaways:
- Pilot relied solely on Go 4 app for fly/no fly instead of using additional apps that include TFRs. A TFR was active for the area the pilot flew in. The app "B4UFLY" includes TFRs.
- Pilot did not maintain visual contact while flying the drone, thus did not know a collision was imminent.
- Drone identified by serial number on one of the quad motors lodged in Army helo's oil cooler fan. NTSB new the motor was from DJI, DJI was then able to track down the owner of the drone.
- Surprising amount of damged caused by a drone made out of mostly plastic.

And we wonder why our range is now so limited.

https://forum.dji.com/thread-124054-1-1.html

This is very strange for Go 4 app. I read that you can utilize voice prompts for signal control and you additionally have the alternative for setting the flight course on the helix or camera mode. There are other extra modes like the true to life mode where your video backs off for a more sensational impact.

____________________________________________________________________________________________
optimizing app blog