EasyManua.ls Logo

Boeing 737-800 - Page 1332

Boeing 737-800
1636 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
737 Flight Crew Operations Manual
Flight Management, Navigation -
FMC Preflight
Boeing Proprietary. Copyright © Boeing. May be subject to export restrictions under EAR. See title page for details.
11.40.20 D6-27370-866-EGP
Dashed prompts change to DIRECT if the TO waypoint is entered first.
Dash prompts appear for the first VIA beyond the end of the route.
Invalid VIA entries display the scratchpad entry INVALID ENTRY.
Invalid VIA entries are:
airways and company routes which do not contain the TO waypoint of
the previous line
airways or company routes that are not in the navigation database.
When entering airways, the beginning and ending waypoints determine if the
entry is valid. The route segment must contain the waypoint entered in the TO
position. The TO waypoint of the previous route segment must be the same as the
beginning point of the current route segment, or a route discontinuity is created
between the segments.
Entry of a SID or transition automatically enters the VIA and TO data for the route
segments of the SID. A SID automatically links to the next route segment when
the final SID waypoint is part of the route segment.
LACRE3.VAMPS is an example of a SID selection made on the DEPARTURES
page.
V2 is an example of airway entry.
2 TO
Enter the end point of the route segment specified by the VIA entry.
Entry of a waypoint in the TO column without first entering a VIA airway displays
DIRECT in the VIA column.
Box prompts indicate that an entry is required.
Valid waypoint entries for a DIRECT route segment are any valid waypoint, fix,
navaid, airport, or runway.
Valid waypoint entries for airways are waypoints or fixes on the airway.
Dash prompts appear on the first TO waypoint following the end of the route.
(SB Changes YK981 - YQ456)
3 ACTIVATE
Pushing the ACTIVATE key arms the route for execution as the active route.
When the EXEC key is pushed, the route becomes the active route and the
ACTIVATE prompt is replaced with the next required preflight page prompt.
Push – prepares the selected route for execution as the active route.
Activation of a route is required for completion of the preflight.
Displayed on inactive route pages.
September 15, 2016

Table of Contents

Related product manuals