Flightplans don't load with their according flight

[PacificSet90456]

@SpurSchnalle678

When I create a flightplan in the Garmin1000, on the runway (tested with the Baron 58), save the flight and load it again, the flightplan is not loaded additionally. It is not even displayed in the Garmin1000 to choose.

I don’t think flight plan upload or flight plan updates from the Garmin is enabled. I’m not sure why you are saving the flight and then (immediately?) loading it again.

The same when I save a flight enroute with an active flightplan and load the flight again: the plane will appear in the correct location and under correct conditions, but with no flightplan - although the flightplan is listed in the according *.FLT file in the LocalState folder.

The use of a flight file *.flt is not well documented or supported. In addition, each .flt file is customized by the aircraft choice.

It is logical to think that saving and loading a flight file .flt should work any time and and any where. But unfortunately that isn’t how flight files work. The ONLY time they work correctly is when a restart is done at the end of a flight. This is because there are three different sections of the .flt file that contain flight plan information. One of the sections contains a pointer to a flight plan file .pln which is incorrect. When you try re-using a .flt file, the flight plan is not displayed BUT the flight plan information is in the NAVLOG top menu item and may or may not be displayed on the VFR Map.

I also cannot create a flightpaln in MSFS and save it under the *.PLN extension - it is not offered in the SAVE dialog.

Where are you creating and then attempting to save a flight plan? On the World Map?

To make it short: I can load a *.PLN file once, but cannot reload an active flightplan with a *.FLT file.

An active flight plan is not a .flt file. As I mentioned the .flt file contains an incorrect pointer to the .pln file.

Even though many tickets have been submitted through ZenDesk, Asobo seems to be reluctant to fix this issue. It is sort of working as it was initially designed.