MSFS Creates IFR Flightplan that can't be flown. Must Manually enter into G3000 NAV. Why?

[DrizzlyPrism745]

Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

2 tags are required: One for platform, and one for aircraft.

Are you using Developer Mode or made changes in it?

NO

Have you disabled/removed all your mods and addons? If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the Community Support section.

YES

Which aircraft are you reporting an issue about? (Please also add the proper tag for it)

Daher TBM930

Brief description of the issue:

IFR Flight from CYLK Runway 28 to CYZF Yellowknife RW10, with RNAV10-Z Approach

Provide Screenshot(s)/video(s) of the issue encountered:

YES

Detailed steps to reproduce the issue encountered:

1. Use the MSFS MAP to enter the flight normally (Screenshot 1)

2. Screenshot 2. The flight should be direct to the WEST. Notice there is no FMS from takeoff/ CYLK. In fact FMS says I should take off and fly EAST to the APPROACH. I tried flying this, there is no flight path to connect to.
3. Screenshot 3. Manually enter the G3000 and manually add this flight. It now shows up. However, after Load it again appeared erroneous (again back to trying to connect to ADRIS faf waypoint.
4. Screenshot 4. All good after selecting the DAXAX iaf waypoint. Load and Go.

What is wrong with this load? Is this airport or approaches out of date? First time seeing this type of error where I cannot fly a flight entered directly into the MSFS MAP.

PC specs and/or peripheral set up if relevant:

PC Windows 11.

Build Version # when you first started experiencing this issue:

1.34.16.0

---

For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

[CasualClick]

Hello!

Your topic has been moved into the Aviate, Navigate, Communicate Community Support category.

The Bug Reporting category is for posting suspected or confirmed bugs that other users are able to reproduce. Using the template 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 Community Support category. If the community can replicate your issue, first search the Bug Reporting 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, 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.

[CasualClick]

Personal Comments and Observations

Cannot Reproduce.

Note my flight plan built in the MSFS World Map below. And then screenshots in-cockpit after a Cold & Dark startup. MFD show flight plan path and GTC shows Flight Plan details.

Also note proper EFB Flight Planning Tools like Little Nav Map cannot generate a valid route using either mix of Low Altitude Airways or even Direct Path under IFR Rules.

So I think this is a combination of a route that cannot generate a valid IFR plan and something else in your configuration.

[Habu2u2]

Hi @DrizzlyPrism745
You said in your description you were going to fly RNAV10Z, but in the WM you’ve set up for RNAV 10Y. However, that approach doesn’t show up at all in my completely unmodded 930, because (as shown in your screenshot) it’s shown as an RNP approach. To my understanding, The 930 isn’t certified for RNP approaches, and that approach shouldn’t even be listed as an option for an approach (and it’s correctly not shown in my 930 FMS).

So there appears to be some issue there… not sure what’s causing your FMS to show the RNP approach unless you’ve got some add-on or outside program (navdata???) buried in the sim or just a temporary glitch.

The next issue probably is that the procedure as it’s set up in your second set of screens where you’re set for 10Z, is that the transition is probably set for “vectors” rather than a specific transition point. For a valid RNAV approach to that airport, You should use RNAV gps 10Z LPV, and set DAXAX as the transition point (or you can use the other transition that will be offered when you set up the approach), and then you should get a correct initial flight path to your transition point and it should fly the whole thing correctly.
The reason I think your approach is currently set to “vectors” is that the sim currently does not react well to “vectors”. If the sim has “vectors” set, The G3000 is correctly not displaying the initial leg because it assumes you will hand fly (or do a "direct to) a waypoint ATC assigns you. Unfortunately, the sim ATC isn’t generally doing that. So the G3000 doesn’t know where you’re going to be vectored to, so it doesn’t activate that leg.

You might double check your procedure in the MFD, and make sure it’s set to a valid transition point and not “vectors”. You can use the preview option on the procedures page to see which transition works best for you, or just use the one I used and it should be fine.
I hope I said it well enough that you get what I think you need to do to get it to work right.
Regards
P.S. your “direct to” is working because it’s replacing the “vector” leg with a leg the FMS understands. If you “direct to” the IAF it’s the same as selecting the transition when setting up the approach.
If it’s working correctly after you set the approach, it should look like:

[DrizzlyPrism745]

Thank you AJ for moving this to the forum. My error. However, I use LNM regularly and chose to post this without using it to show the lack when simply selecting the IFR route within MSFS Map function, not with LNM. If I may say, I see you selecting from the Gate to AUTOMATIC arrivals. This is not reproducing my selection of runways and the only IFR RNAV Approach for RW 10 at Yellowknife. Winds in this northern area are intense and I didnt wish to accept whatever RW it selects. I guess I would have expected that any legit selection of arrivals / approaches from MSFS would be valid, especially if strong existing winds strongly prefer a certain RW. Thus, my request for RW 10. If you select as I stated, I would be interested if you also see an incomplete path. Another suggestion from @Habu2u2 is my next try. Thank you.

[DrizzlyPrism745]

Thank you SO much for your much deeper understanding of the G3000 operation under IFR conditions. You hit it spot on. My error on RNAV Y vs Z. I have installed the Working Title G3000. I can try to uninstall to eval. if that is an issue. However, note the following sequence: (SS1) for my entered plan. SS2: The starting RW 26 was dropped from the FP, but the RNAVgps Z 10 LPV is correct… HOWEVER (SS3) it does suppose VECTORS, and upon manually changing to DAXAX manually, all is good (SS4).

This begs the question – is this a bug? The upside to this is it is forcing me to understand more deeply how to program the G3K. However, I’m not sure this is MS’ intent, no?
Thank you. I’ll be more aware of the VECTORS implications on my FP and may insert a manual WP, if there is no other Approach available than vectors.
Most sincerely, Mark

[Habu2u2]

Glad it worked for you. IMHO, this isn’t a bug in the Garmin, but a major issue with the flight planning logic in the sim. The sim sometimes seems to have issues assigning a transition if you set up a flight (direct IFR) to an airport if there’s no intermediate waypoint. Other times it has an issue transitioning from a SID to your first enroute waypoint. I’m sure The MS and WT folks are fully aware of the sims issues with making consistently good flight plans, and how thats impacting the use of the outstanding Garmin units they’ve given us. As they say, you can’t get to step 500 without doing steps 1, 2, 3……
Anyway, glad you see what the sim’s doing and understand the logic to get it to do what you intended it to do.
Regards
P.S. just FYI here’s a link to some comments by Bishop398 from WT concerning this issue and some other issues

Garmin G3000/5000 Issues and Support

For those of you having autopilot and/or suspected flight plan import issues, we will need a good deal more information in order to diagnose a cause (as these types of issues were not reported during the beta, and the new systems are much more complex to operate): Full flight plan and screenshots of the flight plan pages Screenshots of the PFD showing the autopilot mode annunciations at the top of the PFD during the time the problem is occurring Screenshots of the MFD map showing the plotted f…

[CasualClick]

@DrizzlyPrism745

I have installed the Working Title G3000. I can try to uninstall to eval.

The Working Title G3000 is built into the sim since AAU1. If you are still using a Working Title Community Mod, your sim configuration is incorrect and unsupportable.