Bahamas244
4th Jan 2014, 16:57
At my airline, everyone is new to the 737 Classic. Still a bit of growing going on with the FMS and CDU entry. The use of the altitude data entry for waypoint crossing is not clearly spelled out in the FCOM with only one page speaking to it. I personally believe that is because the A or B suffix should be self explanatory when applied to waypoint altitude constraints, however, I am seeing a lot of crews wrongly applying the suffix to EVERY waypoint they are cleared to descend and level off at.
The logic employed, which I think is incorrect application of the FMC feature, is that it will recalculate all the altitudes behind the waypoint, aiding in descent. This may be correct IF there is continued descent, but not when one is leveling off at the fix specified.
Example:
"Boeing 123 cross LUCKY at FL130 at 250knots" I am thinking the entry should simply be LUCKY 250/130 and not 250/130B because there is no constant descent to increase the descent gradient since there is a level flight segment.
Looking at the computed numbers for the waypoints after doesn't show any change to backup the B suffix entry logic.
Trying to substantiate my logic against the inappropriate use of the at or below entry.
The logic employed, which I think is incorrect application of the FMC feature, is that it will recalculate all the altitudes behind the waypoint, aiding in descent. This may be correct IF there is continued descent, but not when one is leveling off at the fix specified.
Example:
"Boeing 123 cross LUCKY at FL130 at 250knots" I am thinking the entry should simply be LUCKY 250/130 and not 250/130B because there is no constant descent to increase the descent gradient since there is a level flight segment.
Looking at the computed numbers for the waypoints after doesn't show any change to backup the B suffix entry logic.
Trying to substantiate my logic against the inappropriate use of the at or below entry.