Crz alt invalid
-
Same here, CRZ ALT INVALID flying FAEL-FAKN lightly loaded with a CRZ FL330.
The CRZ LVL INVALID appeared only once we had levelled off at an intermediate altitude due ATC, nevertheless, the aircraft then simply refused to return to PRF mode when ATC instructed me to continue my climb at which point the message appeared.
I again simply switched off as there's no point in flying this product like this.
My earlier ticket (MDPC to TUPJ or TAPA) on this exact issue remains unresolved.
-
Believe I've found a workaround to this annoying bug!!! It seems to have to do with the altimter qnh/std button. I've been flying in areas mostly with very low transition altitudes (3,000 ft or so) and have been putting this button into STD. Don't do this. If you spin the altitude window up with it in standard, it will give you the invalid cruise message, and you can't engage profile. The solution I've found is as follows:-
Just leave the button in QNH and manually set the altimeter
-
If you do switch to STD, but level off at an intermediate altitude before cruise, you must reselect QNH, then on the PROG page of the FMC, change the cruise altitude to the altitude currently selected in the autopilot (i.e. 12,000). I was able to successfully reengage PROF. I could then switch back to STD and it would stay.
Curious to hear if this helps anybody else.
-
-
Just want to follow up if it helps anybody. Haven't had this in a while. My earlier method proved to not work sometimes. I've been doing two other things consistently, and so far I've had good luck.
-
Make sure you press the STD button BEFORE you click the screw hotspot to standarize the backups. It doesn't seem to like the other way around, and causes a glitch in the STD button.
-
I was flying in the Caribbean so I had the aircraft configured for fuel in pounds but altimeters in hPa. Ever since I forced the aircraft config ini files to be in pounds AND inHG for the altimeter, no problems. Perhaps it was this "mix-match" of imperial and metric units confusing the FMC.
-
-
We do have all of the feedback in this thread, as well as all of the feedback provided through Just Flight Support, logged on our internal trackers, and improvements will be coming in future updates.
The INVALID CRZ ALT message indicates that the T/C is being calculated after the T/D (i.e. the FMS is calculating that the aircraft doesn't have the performance to reach the entered CRZ FL). I suspect (but I'll need to check with the rest of our team) that the message is generating correctly, but the MAX/OPT FL may be a little too optimistic on shorter flights. The solution for this message generation would be to replan the flight at a lower cruise altitude.
Mark - Just Flight
-
We do have all of the feedback in this thread, as well as all of the feedback provided through Just Flight Support, logged on our internal trackers, and improvements will be coming in future updates.
The INVALID CRZ ALT message indicates that the T/C is being calculated after the T/D (i.e. the FMS is calculating that the aircraft doesn't have the performance to reach the entered CRZ FL). I suspect (but I'll need to check with the rest of our team) that the message is generating correctly, but the MAX/OPT FL may be a little too optimistic on shorter flights. The solution for this message generation would be to replan the flight at a lower cruise altitude.
Mark - Just Flight
I don't think the message is generating correctly because you can easily reach the cruise altitude programmed with hundreds of miles to spare before descent. This issue is not exclusively on short flights. Had it happen just last week on a 400nm leg, cruising at FL280 with very mid/low weight.
Another workaround I've found to this is programming a hardware dial to control the altitude knob instead of using the mouse wheel scroll. Using the mouse wheel scroll to spin up the altitude up quickly seems to aggravate this problem.
-
If you haven't already, could I kindly ask you to raise a ticket with any information like that via the following link: https://www.justflight.com/support
Then our support team will be able to properly log that feedback on our internal trackers.
If you've already created a ticket for this, we'll already have the info logged, and our development team will be investigating it further.
Mark - Just Flight
-
If you haven't already, could I kindly ask you to raise a ticket with any information like that via the following link: https://www.justflight.com/support
Then our support team will be able to properly log that feedback on our internal trackers.
If you've already created a ticket for this, we'll already have the info logged, and our development team will be investigating it further.
Mark - Just Flight
