Archived

This topic is now archived and is closed to further replies.

namida

FMC cannot calculate cruise altitude.

Recommended Posts

Some wired thing happens whlie planning routes from EDDF - LFPG. Route(Airac 1108) - EDDF SOBRA Y180 DIK UN857 RAPOR UZ157 VEDUS LFPG EDDF SID : RWY18 - SOBR3SLFPG STAR : RWY27L - VEDU4J.VELLER 8kD0.jpeg SID set, and right after STAR selection, CRZ ALT CHANGED msg appears on scratchpad and cruise alt has actually changed. 8kDG.jpeg After this, all the altitude values in LEGS page has gone.I found there're 2 discontinuity and a (VECTOR) leg, so removed all discons and vector legs.Even with this modification It doesn't calculate routes for a long time. 8kE6.jpeg FL280 is embeded with STAR procedure.PERF info was not set because I do it after Departure has entered.. Is this a bug or Am I miss something?

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

It's only about a 300 mile trip, that's about right. What Flight Level are you attempting??

Share this post


Link to post
Share on other sites

I'm not sure but manipulating this route several times, it has work one time with 4 or more FL280 in LEGS page.Anyway I'll check if this is inevitable by too high altitude problem. Thanks!

Share this post


Link to post
Share on other sites

See FCOM Volume 2, Section 11.60.2 The message appears when a selected STAR or approach contains a crossing restriction that conflicts with the selected cruise altitude.

Share this post


Link to post
Share on other sites

I still wonder why new altitudes are not set automatically as it has changed automatically,but at least I can bypass this result for futher flights. Thank you guys!! I read 2 FCOMS through a week but everytime I encountered problem I found a new line. Idea.gif

Share this post


Link to post
Share on other sites