Have you got the Phantom back?
this doesn't happen very often.
My guess is that you did not have enough altitude. Likely due to launching from a lower elevation, flying to an area of higher elevation, and not correctly accounting for the trees growing in the higher elevation.
RTh and MAX altitude values are both stored in the AC, you won’t see values in a flight app without the AC connected.
It lost signal because you did not have a clear, unobstructed line of sight to your Phantom.
The height shown is the height above your launch point.
Once your Phantom has crashed into a tree it doesn't matter how many GPS satellites it has, RTH isn't going to happen.
You can check in the app when you have your Phantom powered on but it wouldn't matter what RTH was set at in this case.
It lost signal because you did not have a clear, unobstructed line of sight to your Phantom.
Treetops were blocking the signal.
The number of satellites has nothing to do with the quality of the radio signal between your controller and the Phantom.
The height shown is the height above your launch point.
At the point where the flight record ended, the terrain was about 74 feet higher than the launch point and the Phantom would have been about 39 feet above ground level (not counting tree height).
If the trees were 40 feet high, that is all the explanation you need for the incident.
Once your Phantom has crashed into a tree it doesn't matter how many GPS satellites it has, RTH isn't going to happen.
You can check in the app when you have your Phantom powered on but it wouldn't matter what RTH was set at in this case.
The Phantom never got a chance to RTH.
In a Litchi waypoint mission, the mission will continue even if signal is lost. RTH will not be initiated.
In a waypoint mission it is extra important to make sure that you have sufficient height to clear all terrain and obstacles like trees because Litchi will fly exactly where you program it to. Even into a mountain (or treetops)
I also thought about why seemingly only the downlink was compromised. Might it be that a custom channel was selected for the downlink and the operator was unlucky enough to have another service operating on that channel? I’m not sure if the custom channel setting is stored in the AC or is GO app and controller specific (would not carry across to a litchi use instance).
I don’t believe so. That is why the 32 channel hack was often helpful in increasing range. It made one extra channel available for the control signal.
It lost signal because you did not have a clear, unobstructed line of sight to your Phantom.
Treetops were blocking the signal.
The number of satellites has nothing to do with the quality of the radio signal between your controller and the Phantom.
The height shown is the height above your launch point.
At the point where the flight record ended, the terrain was about 74 feet higher than the launch point and the Phantom would have been about 39 feet above ground level (not counting tree height).
If the trees were 40 feet high, that is all the explanation you need for the incident.
Once your Phantom has crashed into a tree it doesn't matter how many GPS satellites it has, RTH isn't going to happen.
You can check in the app when you have your Phantom powered on but it wouldn't matter what RTH was set at in this case.
The Phantom never got a chance to RTH.
In a Litchi waypoint mission, the mission will continue even if signal is lost. RTH will not be initiated.
In a waypoint mission it is extra important to make sure that you have sufficient height to clear all terrain and obstacles like trees because Litchi will fly exactly where you program it to. Even into a mountain (or treetops)
