2.
The required action by the pilot should the power-up tests fail.
3.4.2.2. Navigation Database
The navigation database (NDB) contains navaids, air-ways, departure/arrival procedures, approach proce-dures, airports and runways.
Objectives that shall be understood:
1.
How to verify or select (if applicable) the current navigation database within the FMS.
2.
Operating limitations of using an expired navigation database.
3.
Navigation charts, supplemented by NOTAMs, supercede the electronic navigation database.
Objectives that should be understood:
1.
How to perform a navigation database update (e.g., disks,PCMCIA card, etc).
2.
The frequency of the updates (e.g.,every 28 days).
3.
The source of the navigation database update (e.g.,FMS manufacturer, a third party, etc.).
3.4.2.3. Date and Time
Date is used to determine NDB effectivity cycle.Time is used in actual and estimated position reporting and planning.
Objectives that shall be understood:
1. How to verify or correct (if applicable)
the date and time of the FMS.
Objectives that should be understood:
1.
The source of the FMS date and time (e.g., directly from GPS, aircraft master clock, etc.).
2.
The effects of incorrect date and time (e.g., RAIM predictions, ETE/ETA, etc.).
3.4.2.4. Software Version
The software version defines the capabilities of the FMS.
Objectives that shall be understood:
1.
How to verify the software version.
2.
Operating limitations associated with the installed software version.
3.4.3. Initialization
3.4.3.1. Position
The initialization of the FMS position is based upon pilot selections and entries.
Objectives that shall be understood:
1. How to initialize the FMS position (and IRS if applicable).
2. The different methods possible for initializa-tion (e.g., named waypoint, latitude/longitude, etc.).
Objectives that should be understood:
1.
The effects of initializing the FMS and IRS to an incorrect position.
2.
The effects of FMS restarts on the FMS
position while the aircraft is inflight.
3.4.3.2. Performance
Performance initialization is necessary for accurate performance predictions.
Objectives that shall be understood:
1.
How to initialize the performance functions.
2.
The required entries for the performance functions.
3.
Operating limitations associated with the performance function (e.g.,VNAV availability when performance is not initialized, advisory information, etc.).
4.
The different performance options available (if applicable).
3.4.3.3. Takeoff and Landing Data
The takeoff and landing data (TOLD) function is the automatic computation of takeoff/landing V-speeds and performance data (if applicable).
Objectives that shall be understood:
1.
How to initialize the TOLD function.
2.
The required entries for the TOLD function.
3.
Operating limitations (e.g., advisory informa-tion).
4.
How to make adjustments to takeoff and land-ing data, if applicable (e.g.,V1 min or max, balanced field length, etc.).
3.4.4. Flight Planning
3.4.4.1. Entry and Modification
A flight plan is a series of waypoints that define an intended route of flight. Each waypoint in the flight plan may be def ined later ally and vertically. The course between two waypoints in the flight plan is called a flight plan leg.
Objectives that shall be understood:
1.
How to name a flight plan.
2.
Different methods of creating an active flight plan (e.g.,manual entry, recall from memory, AFISTM, etc.).
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：NBAA Automated Flight Deck Training Guidelines(8)
