Jump to content

Bazz

Member
  • Posts

    6
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Bazz's Achievements

1

Reputation

  1. Bazz

    MSFS A320 V2 AIRAC

    Again you are amazing, thankyou
  2. Hello Wondering if you can please advise which Navigation database the A320 V2 is using. It seems different to the standard A320 and B787 however it may just be the implementation of the A320 which is more detailed and accurate. I believe we are still on AIRAC 2406. Specifically on a flight from NZDN to NZQN I cant plan direct to ATKIL without also selecting the ELRUV Star, whereas I can on the other two aircraft
  3. You and your product, and your support are amazing thank you
  4. Hello and thank you sincerely for your help I tried again and got the same erroneuos result, just to check what I had done. So then I managed to get it right by playing around with the arrival page. Previously I had not entered a SID or a STAR and only entered RNAV 14 W, nothing else. This time I went into arrival and selected RNAV 14W then selected VAPMU as a via and it then it chose and displayed the correct constraints. However it also dropped IRPOD of the FPLAN page, interesting, it seems it should be where "LIM" is So wondering if you can let me know what you entered on the arrival page, because that changed a lot which makes sense. It also wanted to change the cruise altitude to FL10 so I went in and changed it back to FL4 Really appreciate your help, thank you again
  5. Hello Not sure whether I am missing something however I do have the TCA Side stick for the A320 ahd the red button configured to toggle AP, however it will only toggle the AP on and will not toggle OFF. I have to use the Mouse button, then the alarms go off as it seems the AP needs to stay on until after landing
  6. Hello, Great product and really enjoying thank you VNAV seems to work well for the most part however I am not sure about a couple of things Firstly in the example in the manual it says to enter the FAF altitude in the FCU at the top of descent. When I do this it does not recognise the waypoint altitude constraints in between TOD and FAF. Secondly I found this when I did a small flight from YBBN to YBCG RNAV 13W where the constraints are as follows and the MCDU Flight Plan calculated altitudes VAPMU Constraint 2500 A320 MCDU Flight Plan page calculated 1828 CG017 Constraint 2500 A320 MCDU Flight Plan page calculated 1678 I am wondering if you can comment on this please Kind regards Barry C
×
×
  • Create New...