Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About ba747heavy

  • Rank
    Ramp Agent
  1. Thank you for your input, but no, that response is not helpful at all. If you re-read what I posted, you will see all I did was scroll the altitude in the FCU window. I did not click or right-click on the altitude knob. It reset the cruise altitude in the MCDU but did not change altitude (it remained, as I said in the original post, at level flight at the original cruise altitude), which it should have done had I pushed or pulled on the knob.
  2. I've had a scenario come up a few times now where I have had to change the arrival runway, which required a new routing on the STAR already in the MCDU. The easiest way to follow what I am talking about is look at KPHX and the EAGUL6 arrival. If, for instance you originally put in runway 8, the MCDU correctly adds in the way points/altitudes all the way to OBASE and adds in a discontinuity after OBASE for the expected vectors from air traffic. However, lets say the expected runway is changed to 26, there is now a new routing after HOMRR to JAGAL, with new altitudes and such. The MCDU will remove and replace the ILS way points for runway 8 with the 26 waypoints, but will not replace the STAR way points with the new routing required due to the runway change. The only way I've found to work around this is to completely change the STAR (runway doesn't seem to matter, and the best of my recollection changing the transition fix didn't fix it), insert the change, go back and reselect the original transition and STAR with the new runway. The best I've been able to figure, this STAR/runway change is not specific to KPHX, but that was the easiest example I could come up with.
  3. I'd like to add in that I too have this problem and am hoping for an official fix from aerosoft that does not include "fixing" my driver settings.
  4. Last night I was flying and the VATSIM controller gave me a pilot's discretion descent approximately 60 miles from the TOD point the MCDU was giving me. I scrolled the FCU altitude to FL240 and the MCDU popped up with a message "NEW CRUISE ALTITUDE" and the TOD way point was gone. The FMA indicated "ALT" and I believe "SPD" (my memory isn't great, I apologize). I did not push or pull the altitude knob, and the plane stayed in level flight. I fixed this my moving the FCU altitude back to my cruise altitude and pushing the altitude knob, which "reset" my cruise back up to where I was.
  • Create New...