Flight Plan from the World Map do not load into Garmin GPS 430/530 on repeat flights with same Short SC-7 model/livery

:wave: 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 User Support Hub.

YES

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

SHORT SC.7 Skyvan

Which aircraft version are you experiencing this issue on? (You can find this listed in the Content Manager under the Aircraft Name)

Short Skyvan version: 1.0.9

Brief description of the issue:

When using the Short SC-7 Skyvan with Garmin 430/530, a simple Flight Plan entered from the World Map does not load into Garmin GPS 430/530 on subsequent flights with same SC-7 model/livery as the previous flight. Changing the model of the SC-7 (e.g. from Military to Surveyor) -or- changing the livery (e.g. from Camo to Grey) appears to fix the symptom. Also, I note that the issue persists across restarts of the Flight Simulator -and- cold restarts of the Windows computer.

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

Detailed steps to reproduce the issue encountered:

Steps to reproduce error condition with a sequence of 4 flights (my full test sequence and results):
— TEST START

  1. Start MSFS;

Flight 1 – First flight with “fresh” SC.7/Livery
2. From MAIN MENU, select WORLD MAP;
3. Select a different Short SC.7 aircraft model than the current aircraft shown, select “CLOSE” to return to WORLD MAP. (In my test sequence, I selected “SC.7 Surveyor” and the “Red Livery” since it was a different model that the last one I used, be sure to start with a "fresh model/livery that you used for your last flight);
4. SELECT DEPARTURE: “AYNZ Nadzab, Lae”, GATE (PARKING 4 – RAMP GA LARGE);
5. SELECT ARRIVAL: “AYXI Sim Airport, Wau”, RUNWAY (18);
6. Select “FLY”;
7. Select “READY TO FLY”;
8. In cockpit, switch PORT and STBD MAIN BATTERY switches to ON (up);
9. Switch ELECTRICAL MASTER SWITCH to ON (up);
10. Wait for the Garmin GPS’ to start up;
11. On each GPS, when prompted, press ENT to acknowledge database source screen and again to acknowledge Instrument Panel Self-Test screen;
12. Wait for Satellite Acquisition to complete and the GPS’ to show the map screen;
13. Press the “FPL” button on either of the DPS units;
14. Flight 1 result (PASS): Flight Plan (AYNZ / AYXI) successfully loaded to GPS Units;
Flight 2 – Second flight with same SC.7/Livery
15. Press “ESC” to return to the FS submenu and select “MAIN MENU” to return to the Main Menu;
16. From MAIN MENU, select WORLD MAP;
17. SELECT DEPARTURE: “AYNZ Nadzab, Lae”, GATE (PARKING 4 – RAMP GA LARGE);
18. SELECT ARRIVAL: “AYXI Sim Airport, Wau”, RUNWAY (18);
19. Select “FLY”;
20. Select “READY TO FLY”;
21. In cockpit, switch PORT and STBD MAIN BATTERY switches to ON (up);
22. Switch ELECTRICAL MASTER SWITCH to ON (up);
23. Wait for the Garmin GPS’ to start up;
24. On each GPS, when prompted, press ENT to acknowledge database source screen and again to acknowledge Instrument Panel Self-Test screen;
25. Wait for Satellite Acquisition to complete and the GPS’ to show the map screen;
26. Press the “FPL” button on either of the DPS units;
27. Flight 2 result (FAIL): No Flight Plan loaded to GPS Units;
Flight 3 – Change SC.7 Model and Livery after failure
28. Press “ESC” to return to the FS submenu and select “MAIN MENU” to return to the Main Menu;
29. From MAIN MENU, select WORLD MAP;
30. Select a different Short SC.7 aircraft model than the current aircraft shown, and select a different livery. (In my test sequence, I selected the “SC.7 Military” model and the “Green Camo” livery since they were different than the last flight);
31. Select “CLOSE” to return to WORLD MAP.;
32. SELECT DEPARTURE: “AYNZ Nadzab, Lae”, GATE (PARKING 4 – RAMP GA LARGE);
33. SELECT ARRIVAL: “AYXI Sim Airport, Wau”, RUNWAY (18);
34. Select “FLY”;
35. Select “READY TO FLY”;
36. In cockpit, switch PORT and STBD MAIN BATTERY switches to ON (up);
37. Switch ELECTRICAL MASTER SWITCH to ON (up);
38. Wait for the Garmin GPS’ to start up;
39. On each GPS, when prompted, press ENT to acknowledge database source screen and again to acknowledge Instrument Panel Self-Test screen;
40. Wait for Satellite Acquisition to complete and the GPS’ to show the map screen;
41. Press the “FPL” button on either of the DPS units;
42. Flight 3 result (PASS): Flight Plan (AYNZ / AYXI) successfully loaded to GPS Units;

Flight 4 – Second flight with same SC.7/Livery (FAIL)
43. Press “ESC” to return to the FS submenu and select “MAIN MENU” to return to the Main Menu;
44. From MAIN MENU, select WORLD MAP;
45. SELECT DEPARTURE: “AYNZ Nadzab, Lae”, GATE (PARKING 4 – RAMP GA LARGE);
46. SELECT ARRIVAL: “AYXI Sim Airport, Wau”, RUNWAY (18);
47. Select “FLY”;
48. Select “READY TO FLY”;
49. In cockpit, switch PORT and STBD MAIN BATTERY switches to ON (up);
50. Switch ELECTRICAL MASTER SWITCH to ON (up);
51. Wait for the Garmin GPS’ to start up;
52. On each GPS, when prompted, press ENT to acknowledge database source screen and again to acknowledge Instrument Panel Self-Test screen;
53. Wait for Satellite Acquisition to complete and the GPS’ to show the map screen;
54. Press the “FPL” button on either of the DPS units;
55. Flight 4 result (FAIL): No Flight Plan loaded to GPS Units;
— TEST END

PC specs and/or peripheral set up if relevant:

Windows 11 PC (non-steam)

Build Version # when you first started experiencing this issue:

Microsoft Flight Simulator: 1.37.19.0


:loudspeaker: 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:

I occasionally have that problem in Carenado’s 182RG and Blacksquare‘s 208B. My guess is it being a problem in WT‘s implementation.