<![CDATA[FMC NEW WAYPOINT format error]]>As per the manual, I've tried entering waypoint SUXTU in format 5303.4N/01716.51E by typing it into the scratchpad like in my screenshot and hit LSK2L but I only get a Format Error.

8abf7baa-f022-43c9-8b0e-a76b843fb6cc-grafik.png

Have I found a bug or am I doing something wrong here?

]]>https://community.justflight.com/topic/10796/fmc-new-waypoint-format-errorRSS for NodeMon, 29 Jun 2026 21:08:48 GMTSun, 28 Jun 2026 19:40:54 GMT60<![CDATA[Reply to FMC NEW WAYPOINT format error on Mon, 29 Jun 2026 11:36:23 GMT]]>Thanks for the feedback. Looking into your specific example, the root cause is the extra decimal place in the longitude. I.e. "/01716.51E" will generate a FORMAT ERROR scratchpad message, but "/01716.5E" will be accepted.

We've logged this on our internal trackers for further investigation.

Mark - Just Flight

]]>https://community.justflight.com/post/51532https://community.justflight.com/post/51532Mon, 29 Jun 2026 11:36:23 GMT<![CDATA[Reply to FMC NEW WAYPOINT format error on Sun, 28 Jun 2026 19:44:43 GMT]]>Just tried via place, bearing and distance and PBD works fine, just lat/long is giving me the format error.

]]>https://community.justflight.com/post/51468https://community.justflight.com/post/51468Sun, 28 Jun 2026 19:44:43 GMT