曝光臺 注意防騙 網(wǎng)曝天貓店富美金盛家居專營店坑蒙拐騙欺詐消費(fèi)者

767-400
Note: When appropriate, compare airplane position on the map with ILS, VOR,
DME, and ADF systems to detect possible map shift errors. Use of the POS
function selectable on the EFIS control panel is the recommended method
for making this comparison. The VOR and ADF pointers should be
displayed on the map.
767-200, 767-300
Note: When appropriate, compare airplane position on the map with ILS, VOR,
DME, and ADF systems to detect possible map shift errors. Use of the
VOR mode selectable on the EFIS control panel is the recommended
method for making this comparison. If ADF pointers are available, they
should be displayed on the map.
RNAV Approaches
767-200, 767-300
RNAV approaches may be flown with any RNP alerting capable FMC (Pegasus)
provided the RNP being used is equal to or less than the RNP specified for the
approach and is consistent with the AFM demonstrated RNP capability.
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.33
767-200, 767-300
FMCs that are not RNP alerting capable (prior to Pegasus) may be used for RNAV
approaches provided the following requirements are met:
• the approach has an RNP no smaller than 0.5NM
• the pilot ensures that DME-DME updating is active prior to commencing
the approach.
767-200, 767-300
With non-RNP alerting capable FMCs, VNAV PTH may be used to fly final
approach, however the MDA(H) published for the approach must be observed. As
a technique, use MDA(H) + 50 feet as the decision altitude and use the same
procedure as is published in the Operations Manual for Instrument Approach
Using VNAV. Use of a VNAV DA(H) is not appropriate.
767-400
RNAV approaches may be flown provided the RNP being used is equal to or less
than the RNP specified for the approach and is consistent with the AFM
demonstrated RNP capability.
Approach Requirements Relating to RNP
With appropriate operational approval, approaches requiring RNP alerting may be
conducted in accordance with the following provisions:
• AFM indicates that the airplane has been demonstrated for selected RNP
• at least one GPS or one DME is operational
• any additional GPS or DME requirements specified by Operations
Specification or by the selected terminal area procedure must be satisfied
• when operating with the following RNP values, or smaller:
• no UNABLE RNP alert is displayed during the approach
Approach Type RNP
NDB, NDB/DME 0.6 NM
VOR, VOR/DME 0.5 NM
RNAV 0.5 NM
GPS 0.3 NM
October 31, 2004
767 Flight Crew Training Manual
Approach and Missed Approach
Copyright © The Boeing Company. See title page for details.
5.34 FCT 767 (TM)
Use of LNAV
To use LNAV for approaches and missed approaches, a proper series of
legs/waypoints that describe the approach route (and missed approach) must
appear on the LEGS page. There are two methods of loading these waypoints:
• Database Selection
This method is required for RNAV and GPS approaches. An approach
procedure selected through the FMC ARRIVALS page provides the
simplest method of selecting proper waypoints. Procedures in the
database comply with obstruction clearance criteria for non-ILS
approaches.
No waypoints may be added or deleted between the FAF and the MAP. If
the approach to be flown is not in the database, another approach having
the same plan view may be selected. For example, an ILS procedure
might be selected if the plan view (route) is identical to an NDB approach.
In this case, waypoint altitudes must be checked and modified as required.
When an approach is flown by this "overlay" method, raw data should be
monitored throughout the approach to assure obstacle clearance.
Note: If an NDB approach for the desired runway is in the database, an
overlay approach should not be used.
If a waypoint is added to or deleted from a database procedure, FMC “on
approach” logic (as described in the Operations Manual) is partially or
completely disabled and the VNAV obstacle clearance integrity of the
procedure may be adversely affected. If an additional waypoint reference
is desired, use the FIX page and do not modify waypoints on the LEGS
page.
• Manual Waypoint Entry
Due to potentially inadequate terrain clearance, manual waypoint entry
should not be accomplished for RNAV or GPS approaches, nor should
this method be used with VNAV after the FAF.
When no procedure is available from the FMC ARRIVALS page, manual
entry of a series of waypoints may be accomplished to define the
　
中國航空網(wǎng) www.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：767機(jī)組訓(xùn)練手冊Flight Crew Training Manual (FCTM)767(75)