Garmin G1000 Pilot's Manual page 251

Integrated flight deck for the piper pa-32 saratoga series
Hide thumbs Also See for G1000:
Table of Contents

Advertisement

When a procedure is loaded, the system will auto-designate (automatically enter and enable) altitude
constraints to be used for vertical guidance. An altitude constraint which has been auto-designated by the
system will be displayed as cyan text.
An altitude constraint may be manually designated for procedure waypoints and enroute waypoints by
activating and moving the cursor to the desired altitude in the active flight plan, turning the small FMS Knob
and pressing the ENT Key. An altitude constraint may be manually designated only if it is available for vertical
guidance. Altitudes that are not available for vertical guidance are shown in white text and cannot be selected
by the cursor.
For all designated altitudes, the system will automatically calculate advisory altitudes prior to the designated
altitude constraint. These advisory altitudes are not auto-designated and are displayed as white text.
Altitudes that have been designated for use in vertical guidance can be "un-designated". Pressing the CLR
Key with the altitude constraint highlighted in the active flight plan removes the altitude constraint designation.
The altitude will not be used for vertical guidance and the text displayed will be shown in white. The system
will recalculate advisory altitudes (white text) once any altitude constraint is designated, modified, or un-
designated.
An altitude constraint may be entered as a flight level (FL), height above mean sea level (MSL), or height
above ground level (AGL). AGL format is only available for airport waypoints.
An altitude constraint is invalid if:
- Meeting the constraint requires the aircraft to climb
- Meeting the constraint requires the maximum flight path angle or maximum vertical speed to be exceeded
- The altitude constraint results in a TOD behind the aircraft present position
- The constraint is within a leg type for which altitude constraints are not supported
- The altitude constraint is added to the FAF of an approach that provides vertical guidance (i.e., ILS or GPS
SBAS approach)
- The altitude constraint is added to a waypoint past the FAF.
Altitude constraints can be modified or removed after having been added to the flight plan. If an altitude
constraint is removed and the navigation database contains an altitude restriction for the lateral waypoint,
the system will display that altitude restriction in white text. The system also provides a way to reinstate a
published altitude constraint that has been modified.
Entering/designating or modifying an altitude constraint:
1) Press the FPL Key on the MFD to display the FPL – ACTIVE FLIGHT PLAN Page.
2) Push the FMS Knob, and turn to highlight the desired waypoint altitude constraint.
3) Enter an altitude constraint value using the FMS Knobs. To enter altitudes as a flight level, turn the small
FMS Knob counter-clockwise past zero or clockwise past 9 on the first character, and the system automatically
changes to show units of Flight Level. Turn the large FMS Knob clockwise to highlight the first zero and enter
the three digit flight level.
4) Press the ENT Key to accept the altitude constraint; if the selected waypoint is an aerodrome without a runway
selected, an additional choice is displayed. Turn the small FMS Knob to choose MSL or AGL, and press the ENT
Key to accept the altitude.
190-02692-00 Rev. A
Garmin G1000 Pilot's Guide for the Piper PA-32 Saratoga
FLIGHT MANAGEMENT
231

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents