曝光台 注意防骗
网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者
phrase like “EXPECT RADAR vectors to final approach.” When
using SIDs, such waypoints typically occur at the end of the common
portion prior to specific transition legs. When using STARs, this will
usually occur at the last waypoint. The electronic database
instructions may specify guidance actions to the FMS which
will result in not maintaining an existing heading. The charted
procedure takes precedence and the pilot must remain in
compliance with the charted procedure unless other wise directed by
ATC.
The actual translation of charted procedures into the electronic
navigation database is accomplished in accordance with the rules
set forth in ARINC Specification 424, Navigation System Data Base.
These rules are adhered to strictly by the industry in attempting to
translate procedures into an electronic navigation database. All
situations may not be covered, or the correct application of the rules
may produce confusing results.
Procedures for a SID or STAR Containing a Radar Vector
1. Compare the chart to the navigation database. If charted SID or
STAR procedures specify a heading to be flown while expecting
RADAR vectors, review the flight plan data in the FMS to assure
the correct heading is coded and followed by a (VECTOR) leg. If
this is not the case, be prepared to use other than FMS
guidance after the waypoint where the vector leg is to start.
TEMPORARY CHANGE
Page 2 of 2
14 June 2002
2. If the charted procedure does not specify a heading, assume
that ATC wants you to maintain the existing heading until
receiving a specific vector heading. If the navigation database
contains headings not shown on the chart, discontinue FMS
guidance unless such headings are specifically authorized by
ATC.
3. If the navigation database does not contain a vector heading or
course to be maintained from the waypoint where the charted
vector begins, but merely shows the next wayoint that is part of
an enroute transition (SID) or approach transition or approach
segment (STAR) after the vector, discontinue FMS guidance
over the vector waypoint and maintain heading until instructions
are received from ATC. Do not allow the FMS to sequence and
commence a turn to the next leg since this would clearly not
comply with the intent to maintain heading and await vectors. In
all cases where ATC expects the pilot to maintain heading and
await further heading information, ATC expects the pilot to
overfly the waypoint. In many cases, linking a STAR and
approach creates a NO LINK between the last STAR waypoint
and the first approach waypoint. Leaving the NO LINK in the
flight plan assures that the vector waypoint is overflown, and the
last heading maintained, until further pilot action is taken.
TEMPORARY CHANGE
2423sv602-TC-1 Page 1 of 1
2423sv702-TC-1 May 1, 1998
2423sv603-TC-1
2423sv703-TC-1
MANUAL AFFECTED: Operator’s Manuals, Report No.
2423sv602 dated 1/15/98, 2423sv603 dated 1/30/98
2423sv702 dated 2/26/98, and 2423sv703 dated 2/16/98.
FILING INSTRUCTIONS: Insert this Temporary Change
into, Section IV, adjacent to page 4-6.
INSTRUCTIONS: Add the following paragraphs.
Waypoint Naming Conventions
ARINC 424 provides waypoint naming conventions which are used
by Jeppesen in the data base. Listed below are the most common
ones which may be encountered when accessing the Jeppesen data
base.
D235H DME waypoint on the 235° radial at 8 nm (H is 8th letter)
XYZ29 ’x’ point on enroute chart, 29 nm from the XYZ VOR.
12ABC ’x’ point on enroute chart, 112 nm from ABC VOR.
FF26 Final Approach Fix for Runway 26
OM26 Outer Marker for Runway 26
MM26 Middle Marker for Runway 26
CF26 Final Approach Course Fix for Runway 26 (usually
located on final approach course about 2 nm outside of
FAF).
RW26 Threshold coordinates for Runway 26.
MA26 Missed Approach Point for Runway 26.
R-345 DME Arc Terminator on 345° radial.
Latitude/Longitude Named Waypoints (Oceanic)
5275N N52 W75
75N70 N75 W170
5020E N50 E20
50E20 N50 E120
5275W S52 W75
52W20 S52 W120
6030S S60 E30
60S30 S60 E130
Section IV
Data Base
4-6 2423sv602
Change 1
Regional Map
Section IV
Data Base
2423sv602 4-7
Change 1
NAVIGATION DATA BASE LOADING
The NAV Data Base is updated through the Data Transfer Unit
(DTU). The DTU utilizes 3 1/2” floppy disks as the input media for
loading the data base. The entire Nav Data Base is reloaded at
each update. Each disk is dated and should be verified to be
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：
庞巴迪挑战者手册10(38)
