Filter
Top Products
NOTE: No database altitude constraints will be displayed at the MAP
if the MAP is abeam or beyond the runway threshold . No altitude
constraints are displayed on an approach if a PT is part of the
approach procedure.
The following may appear in the waypoint altitude field:
• FL: Flight Level
• A: at or above
• B: at or below
• G: glide path (programmed Flight Path Angle)
NOTE: If an approach is programmed at the destination airport, and
the MAP is the end of the runway, the altitude value displayed next to
the MAP is approximately 50 feet above the runway threshold eleva-
tion. If the MAP is prior to the end of the runway and the approach is
straight-in, the altitude displayed at the MAP is computed based on a
line drawn from the FAF through the MAP to a point 50 feet above
the runway threshold. The altitude may not be the MDA (Figure 2-
16). If no approach is programmed, the altitude value will be the air-
port elevation regardless of runway selection. The MAP altitude is
shown in yellow.
The Waypoint VNAV offset is given in nautical miles where a nega-
tive (-)offset is prior to the waypoint (Figure 2-16, interpreted as
"cross ten miles before RYMES at 3000 feet") and a positive offset is
after the waypoint. If dashes appear in the altitude constraint field,
NO altitude is programmed at that waypoint.
ERASE:
Same as for Stored Flight Plans except the current FROM/TO leg
cannot be erased. The Active Flight Plan is automatically erased
upon system shut-down.
Page Display Definitions
2-12
GNS-XL Flight Management System
Rev. 1
Jul/98