Some planes in 2024 are still using 2020 avionics versions which are incompatible with the EFB for importing custom waypoints. I’ve confirmed this with Working Title in their Discord group. The Cessna 400 Corvalis and Cessna 408 SkyCourier for example both have older G1000 versions, and the SC7 Skyvan appears to have an older GNS530. I have tested both .pln files (created from MSFS 2020 or Little Nav Map) and flight plans created via the new planner website, and any custom waypoints from either are ignored by the older avionics versions. They will show up on the map, but they will get ignored by auto pilot and the magenta route will skip right past them. If you send them over to Simbrief (via Little Nap Map or creating them on Simbrief) and use Simbrief to import instead of the EFB, then the custom waypoints are fine. Also, using a 3rd party like PMS GTN750 to load a .pln file or from Simbrief is another workaround and works fine. The problem is that the older 2020 avionics do not support the new EFB and these native 2024 planes should not have shipped with outdated builds. There may be more affected planes, but these are three I have discovered so far.
Hi @PanoMan360 ,
Thank you for this report. We’ve moved your topic into the User Support Hub.
The Bug Reporting Hub is for posting suspected or confirmed bugs that other users are able to reproduce without duplicating an existing bug report. Using the template or providing all the relevant information about your bug and sim setup is required in order to provide valuable information, feedback, and replication steps to our test team.
If you are not sure if your issue is a bug or need further input from the community, please use the User Support Hub category. If the community can replicate your issue, first search the Bug category to see if there’s an existing topic. If it already exists, contribute to that report. Duplicate bug reports will be closed.
If you believe it is a new report and no duplicate exists, then create a new bug topic using the provided topic template.
All issues caused by or involving third-party addons/mods should be reported to the third-party developer. Assure that no addons/mods are used when reporting issues in Bug Reports.
But this IS a confirmed bug that others can reproduce, and I didn’t find it was a duplicate bug report when I searched.
Hi @PanoMan360 ,
When creating a bug report please don’t delete the template. It contains key fields for the devs in order to reproduce the issue and log it in their system. It is also used for other users that want to participate to it. Thank you !
They sent me to a helipad i was flying a C172…
@DementedCorn327 DementedCorn327 was a bug report created? If so is there a link, if not I’ll do one. I’m having the same issue.
I did not find any (so far). So feel free to create reports, 1 per aircraft, using the provided template 
.
There was, but it was moved here. I haven’t had time this weekend to go through every plane in the sim and report every affected plane as an individual report, since that is required. Post each report here though if you have time to do it and I’ll upvote it. I think the Mitsubishi MU2 is another plane I discovered, but haven’t confirmed it with Working Title yet. This is something a Microsoft/Asobo quality assurance team should be doing frankly, we should only have to bring it to their attention instead of doing their work for them. I didn’t pay to beta test 2024, but it’s most definitely a beta. It will get patched up over time no doubt and be a fantastic sim, but it wasn’t fully tested or ready for launch.