-
The STORED RUNWAY pages are closed loop and can be slewed horizontally using the left or right arrow key. The first defined runway page follows the last defined runway page.

 -
The STORED RUNWAY may be used as an origin or destination or alternate, but there will be no associated SIDS or STARs available. FA and CF legs have to be associated with the RUNWAY.

 -
The FA leg is characterized by the altitude of 1500 ft, and used for Departure; the CF leg is ended at 5 NM from the runway and used for approach. In both cases the fix is the runway threshold.

 -All stored runways can be automatically deleted on ground. This function is activated by program pin.
 4 If a pilot wants to define a new runway, he may have access to
_ the NEW RUNWAY page from DATA INDEX B page if no stored runway exists or from the STORED RUNWAY page. (Ref. Fig. 078)
 a Data fields:
_
 -1L-IDENT: the runway identifier must be entered here (7 characters max).
 -2L-LAT/LONG: the latitude and longitude of the threshold point must be entered here.
 -4L-5L-6L: length, threshold elevation and course must be entered on these lines. The data entered for length is automatically interpreted either in meters (M) or in feet (FT) following the OPC Length Unit value. The data entered for threshold elevation is always interpreted in feet. The data entered for course may be referenced to magnetic
 (M) or true (T) north, following pilot entry into the scratchpad. If no reference is specified by the pilot, the course data is interpreted in the context of the current NORTH REF pushbutton switch setting.

 NEW RUNWAY Page
 Figure 078

 -1R-LS IDENT: this field is blank until all mandatory data for the new runway is entered. Once it is done, then it is displayed with brackets to allow the crew to enter the LOC, ILS or MLS identifier (if there is one) into this field. Following this field entry, the NEW NAVAID page is immediately displayed with IDENT (field 1L), RWY IDENT (field 1R) and COURSE (field 3R) automatically filled in with corresponding data from the NEW RUNWAY page. It is up to the pilot to complete that NEW NAVAID page before having the STORE prompt facility (particularly to precise if it is LOC, ILS or MLS class related, into 2L).
 -5R-RETURN: causes the display of the page which was being displayed when NEW RUNWAY page was accessed.
 -6R-STORE: this prompt is displayed when all mandatory data have been entered. This LS key must be pressed to enter the runway into the FMGC. Upon insertion, the page changes to the previously displayed page:
 *
 STORED RUNWAY with the newly entered runway being displayed.

 *
 any page where an airport or runway entry is possible. If the page is left without STORE being pressed, then runway data are deleted. If there are already 10 stored runways, one must be deleted to make room for the one being entered. The first one stored (1/10) is deleted (if not a runway in the flight plan) and the remaining stored runways are moved up (2/10 becomes 1/10, etc.). The newly entered runway becomes 10/10. If the 1/10 was a runway in the ACTIVE, TEMPORARY or SECONDARY flight plan try deleting 2/10, etc. If all stored runways are all flight plan runways including stored route runways, insertion is not allowed and the message (LIST OF 10 IN USE) is displayed.

 -If the NEW RUNWAY page is displayed due to entry of an airport that is not in the data base, the airport ident remains in the scratchpad. The pilot can then append the runway number to the airport ident and enter it into field 1L.
 -A runway cannot be defined at an airport which has runways defined in the data base except if that airport has been defined itself with the NEW RUNWAY function.
 (g)
 Airways Airways are stored in the NAV Data Base as a series of airway fixes. The following data are required for airways:

 -Airway identifier
 -List of Airway fixes
 -Required Navigation Performance (RNP).

 (h)
 Holding patterns The holding patterns stored in the NAV Data Base are holding patterns which occur in the en route and terminal areas. The following data may be provided for holding patterns:

 -Holding Pattern Fix: Fix defined in navaid or waypoint file
 -Inbound course
 -True indicator for Hold Inbound course
 -Altitude
 -Turn direction
 -Leg length

 (i)
 Company route

 1 The company routes (CO RTE) stored in the NAV Data Base
_ designates all or part of a flight plan. The data elements that may be included as part of the CO RTE specification are as follows:
 -CO RTE identifier
 -Origin/DEST Airport
 -CRZ ALT
　
中國航空網 www.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：A320飛機維護手冊 AMM AUTO FLIGHT 自動飛行3(65)