zetato
18th Dec 2016, 09:25
Hi all, my question is for a 737NG pilot, and is related to the planning phase on ground.
I'm using a 737NG simulator model, usually a 738 but I think it should be the same for the other models, and what I need to know, is if after the insertion of the route in the CDU, is possible to insert some constraint on some waypoints for the climb and for the descent phase, in such a way the plane would reach a certain altitude passing a point during the VNAV climb (and continue to climb), and, after the cruise phase, it would start the descent, passing another waypoint at predefined altitude constraint, during the descent (and continue the descent).
At the moment, the model i'm using cause a mess if I try to insert a constraint in the LEGS page on a point of the climb, for example, if I have a CRZ ALT of FL370, TIDKA fixpoint is computed at FL350 and I try to insert /FL335 in the LEGS page on the corresponding RSK, It computes a descent starting some miles prior to TIDKA and an End Of Descent over the point, confusing the rest of the vertical profile.
Something similar happens if I insert a constraint in a point of the descent.
I think it should be normal and easy to adapt a vertical profile during the flight plan insertion phase, but I need a confirmation from you.
I'm using a 737NG simulator model, usually a 738 but I think it should be the same for the other models, and what I need to know, is if after the insertion of the route in the CDU, is possible to insert some constraint on some waypoints for the climb and for the descent phase, in such a way the plane would reach a certain altitude passing a point during the VNAV climb (and continue to climb), and, after the cruise phase, it would start the descent, passing another waypoint at predefined altitude constraint, during the descent (and continue the descent).
At the moment, the model i'm using cause a mess if I try to insert a constraint in the LEGS page on a point of the climb, for example, if I have a CRZ ALT of FL370, TIDKA fixpoint is computed at FL350 and I try to insert /FL335 in the LEGS page on the corresponding RSK, It computes a descent starting some miles prior to TIDKA and an End Of Descent over the point, confusing the rest of the vertical profile.
Something similar happens if I insert a constraint in a point of the descent.
I think it should be normal and easy to adapt a vertical profile during the flight plan insertion phase, but I need a confirmation from you.