Hello,

I am flying with the Wilco Airbusses 319-321 in FSX while using Radar Contact and have the following issue:

The FMCG automatically activates the final approach phase at a certain point in the flight plan (deceleration point) before the arival airport (it is reducing speed, it locks in the programmed approach runway and sets the ILS).

Unfortunately, Radar Contact usually requests to contact Approach only after this point.

So, when I receive the runway to use for the approach, the Final Phase including runway and ILS etc. is already set which cannot be changed w/o starting a GO Around procedure which actually resets the Final Approach phase.

 

Does anyone know a way 1.) that Radar Contact requests to contact approach earlier to give me the chance to programme the right runway before the Airbus is activating the final approach phase or 2.) A way how to reset the final approach phase in the Airbus or 3.) any other way to avoid this issue?

 

Any advice would be highly appreciated!

 

Thanks in advance!

 

Tilo

RC approach contacts you just after 40 nm out from destination and assigns the runway. That can not be changed. After your first ack of a vector you can request an IAP to the assigned or other runway which will let you navigate using the FMCG. If you want RC vectors for you to fly using your MCP you can just request another runway. It is best to use the RC assigned runway as RC's first priority is observing ai patterns which may not follow necessarily expected behavior due to winds. FS has a complicated runway scoring system that chooses the best runway for ai based on aircraft type, runway navaids, visibility, and other factors.

 

If you wish to preassign your arrival runway prior to starting RC you can do that in your RC controller page for the arrival airport based on expected weather but you take your chances with ai conflicts.

 

It is important that all waypoints you use from the FMCG be synced with the .pln sent to RC. I use FSBuild 2.4 for a flight planner with my PMDG 737NG aircraft since that and FSBuild are supported by Navigraph updates for terminal database procedures.

 

I don't know about Airbus operations but in the Boeings I assign the departure and arrival runways in the FMC after getting the information from RC ground and and approach. In the Boeings I always enter the arrival runway so even if I am taking vectors it shows up on the navigation display with an extended center line that gives me situational awareness.

 

In RC you can listen to ATIS about fifty nm out for the "expected" arrival runway but that can change. It is also dependent on what weather application you use.

 

If you are an area that uses runway specific SIDs and STARs I only program the common waypoints for all runways into the .pln sent to RC.

 

To gain flexibility in RC refer to the NOTAMS option in the manual.

 

If using UT2 for a traffic application be sure to set the ai spawning distance to maximum so RC can see the ai as far out as possible.

 

Remember that ATC takes priority over any direction from nav equipment, not the other way around.

 

While based on FSBuild you might get some ideas from this tip sheet I am attaching:

 

 

Hmm, this is what I was afraid of. There seems to be no simple workaround.

However, I just got an idea that I will try: I am going to test whether the automatic activation of the final approach mode does not happen if I am changing from the managed to the selected mode before reaching the Deceleration point. I will try that tomorrow and let you know. For now, I would already thank you very much for your detailed advice. Maybe a move to FS Build could also be a good idea in general.

 

Best regards,

Tilo

There is something OT but related that you should be aware of:

 

Often the FMC/FMCG indicated top of descent is an idle descent to the airport surface. RC's TOD is based on the 3 in 1 rule between your current cruise altitude and the MSL altitude of the crossing restriction and tends to show up earlier than the aircraft suggested TOD.

 

Depending on your arrival direction RC issues a crossing restriction of 11,000 feet (FL110) or 12,000 feet (FL120) about 40 nm out from the destination airport reference center. I don't know how you indicate a 40 nm radius range ring on the Airbus navigation display but on the Boeoing Smith's FMC you put in the ICAO airport code as the fix on the FIX page and then /40 for the place/bearing/distance entry and EXE it. I have also seen in Boeing cockpit videos a 30 nm range ring placed because I believe that's where airport pattern speed restrictions may come into play.

I just tried to change from managed to select mode just before the Deceleration point and it works. The final approach mode does not switch on automatically. So, I am just waiting for the runway assignment by RC4 and then activate the final approach mode manually.