曝光台 注意防骗
网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者
approach routing. The waypoints may be conveniently defined by using
names of waypoints or navaids in the database, bearing/distance from
such fixes, intersections of radials or latitude/longitude information.
Procedure turns and DME arcs cannot usually be manually entered
(unless they can be defined by a series of waypoints). Deviation from the
defined route may require use of “DIRECT TO” or “INTERCEPT LEG
TO/INTERCEPT COURSE TO” when intercepting the inbound course.
Constant monitoring of raw data during the approach is required.
Note: Procedure turns and DME arcs may require use of HDG SEL.
October 31, 2004
767 Flight Crew Training Manual
Approach and Missed Approach
Copyright © The Boeing Company. See title page for details.
FCT 767 (TM) 5.35
LNAV cannot be used to track fix or radial data displayed on the map. A
navaid/waypoint and the appropriate radial may be inserted on the FIX page to
create a “course” line on the map that helps to improve situational awareness. A
similar display may be created by manually tuning an appropriate VOR and
selecting the desired course. These methods provide reference information on the
map display only. They are not reflected on the LEGS page and cannot be tracked
with LNAV. These methods should only be used when there is no opportunity to
use an approach selected from the navigation database and should therefore be
considered only when normal means of displaying approaches are not available.
Pilots should be aware that the displayed course is an FMC calculated course and
is not raw data information.
Note: HDG SEL should be used to fly the approach ground track.
767-200, 767-300
Note: VNAV PTH operation using speed intervention is not available with
manually entered waypoints.
767-400
Note: Automatic procedure tuning and VNAV PTH operation using speed
intervention are not available with manually entered waypoints.
If the approach is not available in the NAV database, select the landing runway
from the FMC ARRIVALS page. The runway and associated extended centerline
then displays on the map to aid in maintaining position awareness.
Pilots should not become involved in excessive “heads down” FMC manipulation
to build map displays while at low altitude. Raw data VOR, ILS, and ADF
displays should be used to avoid distractions during higher workload phases of
flight. Map building should be avoided below 10,000 feet AGL.
Use of VNAV
Approaches using VNAV may be accomplished using any of the recommended
roll modes provided in the applicable Operations Manual procedure.
October 31, 2004
767 Flight Crew Training Manual
Approach and Missed Approach
Copyright © The Boeing Company. See title page for details.
5.36 FCT 767 (TM)
A vertical path suitable for use of VNAV is one that approximates 3° and crosses
the runway threshold at approximately 50 feet. To obtain such a VNAV path,
maximum use of the navigation database is recommended. For approaches where
an RNP is specified, or approaches where a DA(H) is used, the waypoints in the
navigation database from the FAF onward may not be modified except to add a
cold temperature correction, when appropriate, to the waypoint altitude
constraints. With respect to the construction of a suitable final approach path,
there are two types of approaches in the navigation database:
• approaches with a glide path (GP) angle displayed on the final approach
segment of the LEGS page. The final approach segment is completely
compatible with VNAV and complies with final approach step down
altitudes (minimum altitude constraints).
• approaches where no GP angle is published and where the approach end
of the runway is defined by a runway waypoint (RWxx) or a missed
approach point fix (MXxx or a named waypoint) exists. Normally these
waypoints display an approximate 50 foot threshold crossing altitude
constraint and may be used “as is” for VNAV. If the RWxx waypoint
altitude constraint does not coincide with approximately 50 feet, this
waypoint may be modified with a threshold crossing altitude of
approximately 50 feet.
Note: Threshold crossing altitude normally require entry of a four-digit
number. Example: enter 80 feet as 0080.
VNAV may be used for approaches modified in this way; however, the
approach should be flown by constant reference to raw data (VOR, NDB,
DME, etc.) and compliance with each minimum altitude constraint is
required. Use of a DA(H) is not appropriate when the final approach is
manually constructed in this manner.
Note: ILS approaches are in the process of being coded with the appropriate
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：
767机组训练手册Flight Crew Training Manual (FCTM)767(76)
