Device: Samsung Galaxy A36
Operating system: Android OS
Yesterday, while flying to Los Angeles, I encountered an issue with LNAV. While I was asleep over the Pacific Ocean, A/P-LNAV automatically deviated from the planned route, as shown in the attached image. Please investigate this issue.
I would also like to thank all the developers for the ongoing improvements to the LNAV feature. I’m very impressed with the work you’ve done.
Sometimes that occurs when you have 2 of the same fix in your flight plan, usually when copying and pasting flight plans online and mixing them with SIDs and STARs
Simply delete one of the 2 fixes if that’s the case
The flight plan was imported using .fpl file created using SkyVector. So, I don’t think I had duplicate waypoints.
No, this incident happened when I was flying over the ocean, and there were no duplicate waypoints.
I experienced this problem too
From my experience so far, it seems this is an intermittent issue when passing over a waypoint that’s placed at exactly 180*E/W longitude.
Solution: delete said waypoint.
Oh yes, you’re right. This deviation started from 47N80. I’ll make a note of it. Thanks.
This isn’t a FPL issue it is a bug with LNAV.
I came to make a post and found this so thought I’d add.
I’ve had this happen ‘TWICE’ since update on FPLs I’ve used and been over many times - in fact the first time it happened whilst flying on a STRAIGHT part of the FPL.
Appears for a moment it loses LNAV(even on a straight line) then way overcorrects to try and recapture - you end up going in wild S patterns until you correct it. For a heavy it tries to recapture at almost 90 degs meaning it is soon unable to do it.
Today I was on a track and had gone around that section many times before it decided to lose LNAV momentarily and it started wildly trying to overcorrect to recapture - had I not been there it would have ruined the exercise.
I’d say quite a big issue & I expect more will report it when they lose their fpl AFK 
I’d add that I feel this may be related to what’s been put in place to improve way point capturing as a suggestion, since I’ve never experienced this ever before the update in 4 years of IF.
