Hi all,

Been scratching my head for a day or two regarding this issue. I know how to do the RNAV approach on the A310. Being properly configured as per the book, P.DES does not want to arm at all on the A300. Unless im doing something really wrong, this seems to be bugged. Just tried the same practice approaches on the A310 and there it works as it should. I also had some frozen V/DEV issues today. 

Pleased to hear!

Joni

3 hours ago, joni kalanderi said:

Hi all,

Been scratching my head for a day or two regarding this issue. I know how to do the RNAV approach on the A310. Being properly configured as per the book, P.DES does not want to arm at all on the A300. Unless im doing something really wrong, this seems to be bugged. Just tried the same practice approaches on the A310 and there it works as it should. I also had some frozen V/DEV issues today. 

Pleased to hear!

Joni

First you type in MDA then Final approach on the FCU (3.0) then profile button. Works flawlessly for me.  MKJS  RNAV

Well I did the same sequence except that officially the chart says its an RNP approach at LATI. In the FMC it shows up as an RNAV approach. Could it have anything to do with that? I will try to fly a specific RNAV approach airport this eve.

In any case it works with the A310 but not with the A300

Brgds

Joni 

I found the issue in my case. I was doing practice approaches with T/O flying patterns. In the A300 the FMC requires a CI otherwise it doesnt work. Funny enough it seems in the A310 there is a standard CI which does allow it to work in this type of practice run.

So if you do T/O and traffic pattern until the app, make sure in the init page to enter a CI, FL and FROM/TO (in this case same airport)

Brgds