Garmin Flight Deck 100 User Manual

190-00728-04  Rev. A

232

Flight planning consists of building a flight plan by entering waypoints one at a time, adding waypoints along 

airways, and inserting departures, airways, arrivals, or approaches as needed.  The system allows flight planning 
information to be entered from either the MFD or PFD. The flight plan is displayed on maps using different 
line widths, colors, and types, based on the type of leg and the segment of the flight plan currently being flown 
(departure, enroute, arrival, approach, or missed approach).

Active non-heading Leg 

Active heading Leg

Non-heading Leg in the current flight segment

Heading Leg not in the current flight segment

Non-heading Leg not in the active flight segment

Turn Anticipation Arc

Up to 99 flight plans with up to 99 waypoints each can be created and stored in memory. One flight plan can be 

activated at a time and becomes the active flight plan.  The active flight plan is erased when the system is turned 
off and overwritten when another flight plan is activated.  When storing flight plans with an approach, departure, 
or arrival, the system uses the waypoint information from the current database to define the waypoints.  If the 
database is changed or updated, the system automatically updates the information if the procedure has not been 
modified. If an approach, departure, or arrival procedure is no longer available, the procedure is deleted from the 
affected stored flight plan(s), and an alert is displayed (see Miscellaneous Messages in Appendix A) advising that 
one or more stored flight plans need to be edited.

Whenever an approach, departure, or arrival procedure is loaded into the active flight plan, a set of approach, 

departure, or arrival waypoints is inserted into the flight plan along with a header line describing the instrument 
procedure the pilot selected.  The original enroute portion of the flight plan remains active (unless an instrument 
procedure is activated) when the procedure is loaded.

When the database is updated, the airways need to be reloaded also.  Each airway segment is reloaded from 

the database given the entry waypoint, the airway identifier and the exit waypoint. This reloads the sequence of
waypoints between the entry and exit waypoints (the sequence may change when the database is updated). The
update of an airway can fail during this process.  If that happens, the airway waypoints are changed to regular 
(non-airway) flight plan waypoints, and an alert is displayed (see Miscellaneous Messages in Appendix A).