This article outlines the possible reasons why your flight log may show incorrect takeoff or landing points.
These are the most common reasons why this can occur. Please check these to rule out the root cause:
Taking off before GPS initialised
Taking off before GPS initialised
The remote pilot may have taken-off too quickly, before the GPS unit attained a lock. You can check this by viewing the flight log file. To check:
- Click on the flight analyser button
of the log file - Download the csv file
- Open the file to view the co-ordinates
- If the co-ordinates show 'startLatitude' and 'startLongitude' is 0 then GPS was not initialised before taking off
- In this case, the pin representing the 'takeoff point' will display in the ocean, while the landing point will be correct.
Example of the flight log starting with 0,0 coordinates.
Lost connection with GPS
Losing GPS connection during flight can cause the co-ordinates for that timestamp to default to 0,0 or some other number in the log file. To check this, follow the instructions listed above.
- In this case, both takeoff and landing points may be correct, but the flight path can have erratic changes similar to the above example.
Faulty GPS
The GPS unit in the RPA may be faulty. This will most likely cause the entire flight to be recorded incorrectly, but intermittent faults are also possible. Please contact the drone provider for repair or service.
If you have checked all above possibilities and the log files appear 'normal', please reach out to support for assistance.