- Joined
- Dec 28, 2016
- Messages
- 113
- Reaction score
- 24
From the information you've shared so far, it sound like the remote controller disconnected and the Phantom crashed into a tree when it tried to return home. If you upload your TXT flight log here and post a link back here, I'd be happy to review it and confirm/deny that.
I had uploaded to HealthyDrones, but it didn't have all the details that this does, so thanks for the link. The log for the flight in question is here. I was really referring to the file stored on the drone itself, which should contain more information about what happened after it disconnected until it lost power. As far as I know, it won't be possible to retrieve that file without power on the drone.
For comparison, the log of the flight immediately prior (just minutes before) is here. On that flight, Go to Home was activated at 2m 29s, and it shows the craft stopping forward motion, ascending to 246 ft., then continuing flight toward home. That altitude is consistent with what my son had programmed - 70 meters (even though the units on the app are set in Imperial, the selection for RTH altitude is in Metric). He disengaged Go to Home and flew it in Sport and P-GPS most of the way back, but that brief period of flight in Go Home mode indicates to me that the RTH altitude was set correctly.
On the flight he lost the drone, it shows the drone essentially hovering and decreasing in altitude after the return to home mode was activated. The drone was on the ground only a few minutes between those flights, and my son says he didn't change the RTH altitude. Is there a way to find the actual setting of that in the flight log? When I open the app and look at that setting currently, would it be accurate when not connected to the drone?
Appreciate the help!