When I were flying one day I saw something strange when I took a look at the home point before flying.
It was 4,700 miles off ( 7500 Kilometers) from where I was flying.
This Is the first and only time it heppend to me and a good reminder to check before taking off.

Better not initiate RTH.  That's quite a trip.!

Are you sure it has been recorded?
That location is 0 latitude + 0 longitude. It's shown if no GPS Data is available.

Eric13 Posted at 2018-6-18 07:43
Are you sure it has been recorded?
That location is 0 latitude + 0 longitude. It's shown if no GPS Data is available.

Yes It was recorded, this is from my flight records and it was recorded as the home point.

GPS failure maybe?

Anokadrone Posted at 2018-6-18 08:48
GPS failure maybe?

Maybe. It only happen this one time and I always check home point so...

JoiCam Posted at 2018-6-18 08:53
Maybe. It only happen this one time and I always check home point so...

Some things I can chock up to a glitch but good catch!  I will be checking for sure.  Thanks

I think you're going to need a bigger BATTERY  

rwynant V1 Posted at 2018-6-18 09:15
I think you're going to need a bigger BATTERY

And many of them I think

JoiCam Posted at 2018-6-18 09:20
And many of them I think

You definitely want to set the action in case of signal loss to "Hover", not RTH!  

Eric13 Posted at 2018-6-18 11:30
You definitely want to set the action in case of signal loss to "Hover", not RTH!

Now that is something to think sbout

I like Eric's post above.  I'd love to see the log.  

http://www.phantomhelp.com/LogViewer/Upload/

That is as a result of the GPS system returning a set of zero value co-ordinates. That point, just south of Burkina Faso, has the global co-ordinates of 0.00, 0.00

This error was hapenning for a number of people a couple of years ago, caused by faulty firmware.

Geebax Posted at 2018-6-18 17:34
That is as a result of the GPS system returning a set of zero value co-ordinates. That point, just south of Burkina Faso, has the global co-ordinates of 0.00, 0.00

This error was hapenning for a number of people a couple of years ago, caused by faulty firmware.

Thanks for that info. It is good to know.