February 14, 201214 yr HiToday I flew from Billund (Denmark) to Kastrup (Denmark)On my way up to cruising altitude, I got a order to fly direct to TNO ( A waypoint) But the FMC had set an altitude restriction (FL120B) and therefore would the aircraft not climb anymore. I deleted the restriction but it just got worse. And I had to fly the rest of the flight without VNAV.What should I have done to avoid the problem? Patrick - Denmark i7 10900k - GTX1060 (To be upgraded to RTX3080-ti) - 32 GB of RAM - Nvme SSD - 100 mbps internet
February 14, 201214 yr You should have have ALT INT to continue the climb. That would have been the easiest way. Matt Cee
February 14, 201214 yr Afaik ALT INV in fact deletes the restriction and Patrcik (not Patrcik I presume :( ) said he already did that. I wonder how exactly things got worse...?
February 14, 201214 yr Afaik ALT INV in fact deletes the restriction and Patrcik (not Patrcik I presume :( ) said he already did that. I wonder how exactly things got worse...?It's been a while since I've flown a plane with the ALT INT, but I believe if he had stopped at 12,000 in VNAV, he would've been in VNAV ALT and would have needed to hit the ALT INT to get it back into VNAV PATH and start the climb. Matt Cee
February 14, 201214 yr Author So I should have pressed the ALT INT and that would have solved the problem. Easy.Yeah my name is Patrick not patrcik. I have to edit that. Patrick - Denmark i7 10900k - GTX1060 (To be upgraded to RTX3080-ti) - 32 GB of RAM - Nvme SSD - 100 mbps internet
Create an account or sign in to comment