Jump to content

Changing STAR breaks everything


Recommended Posts

I was flying into KDEN on the ZPLYN3.ZIGEE arrival earlier and when I was inbout ASYLM I decided I wanted to take the equivalent landing north RNAV arrival, BOSSS2. I loaded in the new arrival and the route was not loaded on the ND or MCDU. Then both MCDU and ND were completely unresponsive.

 

Here's a video of what happened:

 

 

 

I was able to solve it by loading in a previous autosave before I made the change, going DIRECT back to ZIGEE, loading in a different arrival like the PURRL2, then reloading the BOSSS2 arrival and going DIRECT back to ASYLM.

Link to comment
Share on other sites

4 hours ago, Emanuel Hagen said:

Could you try the same thing with the NavDataPro database please? Does the same happen there?

Yup, selected the Navdata pro in the configurator. Loaded up at a nearby airport, took off, then between ZIGEE and ASLYM, tried to change the arrival to ILS35L and BOSSS2 and it froze the MCDU and ND again. This time it drew out the arrival on the ND though.
Recorded this as well:

 

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use