Bogus waypoint being inserted into my flight plans between departure and WP01?

When I plan a flight in MSFS2020 and Go To Fly, the GPS always shows an additional way point before my own WP01. When I try to fly with GPS, the plane will head off in the direction of the bogus WP. If I cancel the Flight Plan from the cockpit and input a new flight plan or ‘Direct to’, then the aircraft will follow the GPS to the correct WP. If I load a new flight imported from LittleNavMap, the bogus WP is shown (always the same one). See example screen shots. There must be a fault in the software files but my experience is not enough to know where to look. Any ideas please?
E.G.
I select a simple route and go to aircraft. The Pilot Display displays a direction and distance to a WP off West coast of S Africa! Whilst the Copilot Display shows the correct track. (also does this in other aircraft). The Aircraft flies towards the bogus WP when using GPS.
If I load a flight from LittleNavMap the programme adds a bogus WP that’s way down South!
Again the GPS information on the Pilot’s screen is different from that on the Copilot’s screen.

I have uninstalled and reinstalled MSFS2020 once without any improvement.
I look forward to suggestions to try? I’m hoping that I’m making a silly error in my flight planning procedure or GPS settings.

I’m assuming that you always use LNM to prepare your flight plans then “export” them to MSFS.

First suggestion - ensure you reset LNM completely ready for a new flight plan. It probably wouldn’t hurt to reset LNM windows to default in the Windows dropdown), something I believe Alex refers to in the manual. This makes sure you start with a “clean” flightplan.

Second suggestion - can you edit out the unwanted waypoint in the route shown in the World screen in the sim? Note however that when I’ve tried this it sometimes messes up the complete flightplan but it might work.

Try deleting and re-installing LNM; I had an odd fault and a reinstall solved it.

Finally, try creating a flightplan from the World page directly.

Hope this helps.

1 Like

Thank you for your response. I had the problem when creating the flightplan from World Page but it would never show the bogus waypoint. It was only when looking at the GPS screen in Pilot’s view that you could see the distance and direction to the first waypoint didn’t correspond with the flightplan and when flying using NAV GPS, the direction would always change to the bogus waypoint. Also, when opening the Map view, it would only show the correct planned route and not the bogus waypoint. It was only when I tried to solve this by importing a route from LNM, that the bogus waypoint showed on the World page. But there is no way I’ve found of deleting this. It has no name or reference.
When I load a flight using the World page directly, and open the flightplan on the aircraft screen, it does not show any bogus waypoint, although you can see the Distance and Direction figures pointing to one. Deleting the flightplan that’s loaded into the aircraft system clears everything and if I then input a new ‘Direct to’ airport, the GPS works correctly and the aircraft flies to the correct destination.
Here is a simple route in World page, then uploaded to aircraft. The flight plan and Map show a direct flight, but the Distance and Bearing on the Pilot’s screen are completely wrong - but this is the direction the GPS will take the aircraft.


There must be a ‘fixed’ point in the coding that is not getting overwritten when a new flightplan is loaded into the aircraft?

Is this just in this one flight plan?
If so, this could be a nav data issue.
The GPS is probably picking up a waypoint of the same name in a different location, if it couldn’t find the one used in the plan.

I have this problem with any flight plan I make, either directly on the World page or if I upload one from external flight planner. I have been using airports local to me, Caernarfon, Valley, Liverpool and short simple flights whilst I try to find problem.
As I’ve been doing this, the bogus waypoint always appears to be in the same place and I have a feeling it is on the equator just off the west coast of S Africa and could be where both Longitude and Latitude are ‘0’?

See if the solution from this post helps.
https://forums.flightsimulator.com/t/problem-with-flight-plan-bug-and-autopilot/228003/19?u=thesevenflyer

Thank you Sevenflyer. I was confused why it was only happening to me!.
I’m going to have to read up about Unicodes and UFT-8 but at least I’ve got something to work on. Immediate thought is - ‘is there a way to Find and Replace in the text file to speed up the manual process’? Do you know if this is possible?
Thanks again for your help.

1 Like

Yes it is, just open the file with any source code editor and save it.
I use Notepad++ myself . (it’s freeware!)

Thanks, I’ve tried Notepad ++ and it fixes the problem as you said.
I appreciate your help.

1 Like

Your welcome, it’s nice that the cure on the original thread was found and posted about!

Sorry, but I spoke too soon. Yes, I can now take the flight plan and replace the � symbol with the correct ° (degree) symbol. But when I put this into MSFS, it still gives a broken flight plan. See the modified .PLN and the ‘broken’ flight it gives on World map. I have been trying all night to resolve this but without a glimmer of success.
I even took your ‘Fixed’ flight plan and loaded it my FS and it was ‘broken’ (see screenshot).
Do you know if I am doing something different to you? Can you actually load your fixed .PLN in MSFS and fly the route correctly with GPS?
Modified CUSTOMFLIGHT.PLN (3.0 KB)

Is your Windows10 system locale set to English (US)?

I have just checked. Windows display, keyboard and speech are English (United States); apps, websites and regional formats are English (UK).

See if changing those to English US makes a difference, particularly the App, as MSFS, unlike previous sims, runs as an App.

I’ve changed everything in Windows 10 to ‘English - USA’ and it didn’t make any difference ( I did a reset before loading MSFS). I also put everything to ‘English - UK’ but that didn’t help. I have also changed the symbols to degrees and tried different ways of saving and loading, but no improvement so far.

1 Like

Hello Sevenflyer.
If you have time in the next few days, can you do me the following favour: -
On World page, select the very simple flight EGGP Liverpool to EIDW Dublin and then click on FLY to get the plane sat on the runway ready to fly. This will have generated the 4 files, CUSTOMFLIGHT.FLT, CUSTOMFLIGHT.FLT.FSSAVE, CUSTOMFLIGHT.PLN and CUSTOMFLIGHT.SPB located here: Microsoft Flight Simulator/LocalState/Missions/Custom/Customflight.
Can you copy these to me so I can compare with mine. I am particularly interested in the GPS Engine section in CUSTOMFLIGHT.FLT as well as the CUSTOMFLIGHT.PLN.
I have copied my files here for you to see, including the initial route shown on the World and then the route as generated.

CUSTOMFLIGHT.PLN (2.0 KB)

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.