Newbie question: if a STAR has multiple arrivals for multiple runways, how do I select which “branch” to program in the MCDU? For instance, the BRUSR1 arrival into KPHX. I originally wanted to land on runway 26, but the MCDU would only give me the arrival path into runway 7 L/R despite me selecting runway 26 in the MCDU.
Chart for reference:
@FSEINDHOVEN Not necessarily. I still want to use the BRUSR1 arrival since I am coming in from the west (this was on a flight from Sacramento, CA). Looking at the tail end of the STAR, I wanted to enter the Rwy 26 ILS via BRUSR.ANNTI.ZILUB.BRIEZ.KUCOO.JURAZ. However, no matter what I did, the MCDU would only give me BRUSR.BDWIL.ENSEA.FBALL.PGSKN.TLMAN.FOWLE (the arrival into 7L) then have me awkwardly loop around to Rwy 26.
I should fly selected heading from JURAZ and ILS 26 via ZERLO-CERUN-TODRE
Other is not foreseen in the charts nor in the airac
Moin,
The BRUSR1 is an RNAV arrival. You cannot select it for an ILS approach.
But you can do it the other way around. In the MCDU select the 26 RNAV with BRUSR1 approach and fly with ILS. Don’t forget to check the ILS Frequence …
Gruß
Dieter
You’re not doing anything wrong. It’s a problem with the airbus mod and default airbus and the default planes. The WT CJ4 and Aerosoft CRJ do not have this issue. You can see the same issue with the HYDRR1 arrival into ILS25L KPHX. Hopefully when FBW implements their new navigation code it fixes the issue.
@dflight8685 It seemed to work fine with the 7L ILS 
@StewartLapp Ok, that makes sense. Thanks for letting me know!
For some arrivals, if you select the runway, then the STAR, then the transition and execute it, then go immediately back to that same arrivals selection page and select the runway and STAR again but NOT the transition this time, it should insert the transition you selected the first time. It doesn’t always work, but most of the time it does. Def seems to be a bug with the FBW and default versions. As state above, the CRJ and CJ4 don’t have this issue.
@autopylit88 Yeah, I’ve encountered that bug too with the initial transitions, but it’s the subsequent transitions (not sure if that’s the correct term) that I have issues with. Looking forward to what the FBW team can do with their custom nav code.
