A321 Help sought with changing arrival runway/star in-flight

[ocndvr 0]

Hi,

I have a situation with the Aerosoft Airbus A321 (Prepar3d v4.5) which I am really hoping somebody can help me with. I am unable to change the arrival runway (and STAR) during a flight. So, if I am assigned a different runway by ATC from the one I was expecting, I cannot complete the flight since there is no way I can make the change.

I've thoroughly checked the existing threads on this topic, and tried the suggestions, including the following...

https://forum.aerosoft.com/index.php?/topic/121426-how-can-i-edit-the-arrival-runway-while-in-flight/
and
https://forum.aerosoft.com/index.php?/topic/108737-changing-star-in-flight/

The advice given in these threads suggests that it should be possible to change the runway and star via a sequence of selections. This does not work for me. I've tried many times. I wish it was that easy.

https://forum.aerosoft.com/index.php?/topic/144595-changing-star-in-flight/

Here, more detailed steps are given, as follows...

1. Sec FPLN
2. Copy active (KMSP, MUSCL3, via GREAK, RNAV Y 12R)
3. lat. rev. page
4. select new dest - KMSP ( by this way you delete previous star and rwy) 
5. insert rwy: RNAV Y 12L
6 insert star: MUSCL3, via CMMOE 
7 In approach page: enter destination data
8. activate: Sec FPLN

For these steps, I am uncertain which waypoint I should go into the "lat rev page" on. I've tried several, including the destination airport, with no success. If I try to re-add the airport as a new destination, I get a "not found in database" message. When I click on "Data" - "A/C Status" and examine the active databases, I see that there is a "0" for primary database and the correct Navigraph database for the secondary. Any attempt I make to change things here results in losing both flight plans. Perhaps this is the root of the problem?

I've been playing around with this for quite a while, trying all manner of combinations, with no success whatsoever.

Does anybody have any advice regarding this? Anybody else experience this issue before?

Any help at all appreciated. Thanks!

- Bob

[DaveCT2003 2553]

As I posted in the thread you referenced, it's a bug with that airport. I filed a bug report back when I was part of the team but apparently it was never resolved before the project development ended.  I would forget about using the secondary flightplan and delete the waypoints as I referred to in your referenced thread.

 

FYI:  The real aircraft has a different page for doing this which is not modeled in the Aerosoft version.

 

Sorry I could not be of more help, if I ever get P3D booted back up I'll do my best to look at this, but I'm heavily engaged in another flight sim project for the US Navy/Lockheed Martin and another flight sim developer and along with a heavily possibility of going on a transplant list I simply don't have much time these days.

 

Best wishes.

 

 

 

[ocndvr 0]

Dave, thank you so much for your very speedy reply!

 

I appreciate the info. It turns out that in this case the airport is ok. After I submitted my original post, I kept reading various threads related to this issue and to navigational database issues. This combined with your procedure confirmation made me revisit everything again and to finally get on the right track. It turns out that my issue was caused by the way I had my navigational database installed.

 

I originally thought that the "ACTIVE NAV DATA BASE and SECOND NAV DATA BASE" on the MCDU DATA - A/C STATUS page had something to do with the active/secondary flight plans, but of course that was completely wrong. Once I found out it had to do with which database system (Navigraph or NavPro) was installed, I dug further and discovered that my Navigraph installation was not quite right. I ended up re-installing the Navigraph database into the "<documents>/Aerosoft/General/A3XX Navigraph" directory and deleting the "<documents>/Aerosoft/General/A3XX NavData" directory. Now when I check the database via DATA - A/C STATUS, the active database is set to the Navigraph database, as it should be.

 

This means that I can successfully change the approach data - finally! The procedure I use is as follows - please let me know if there is a better way...

 

(1) copy the active flight plan to the secondary flight plan

(2) in the secondary flight plan, select the last waypoint of the current STAR, prior to the arrival runway

(3) on the LAT REV page, re-enter the destination airport into NEW DEST

(4) now I can change the arrival runway and STAR in the usual way

(5) activate the secondary flight plan

 

So glad to finally have this solved. It's been a problem for a while. Thanks again for the reply and best of luck with everything! Cheers!

 

- Bob