-
the UPLINK TO DATA REQ page which allows the crew to specify and send a request to the ground

 -
the UPLINK XXX TO DATA page which displays takeoff speeds and parameters received from the ground for pilot review before insertion into the FM. There are two sets of ACARS TAKEOFF pages: one for MAX takeoff (XXX = MAX), one for FLEX takeoff (XXX = FLX). (Ref. Fig. 004, 005, 006, 007)

 (4)
 Wind data The wind data function allows the uplink of forecasted climb, cruise, descent, and alternate atmospheric data. This message is received in response to a crew manual request or automatically without any solicitation. A manual request is initiated from the ACARS FUNCTION page (Ref. Para. D-(1)) or from any available WIND page. The WIND pages may be accessed on ground from the INIT A page and on ground or in flight from the VERT REV page. When winds are manually requested, a downlink request message is sent and is composed of one or more of the following wind requests depending on flight phase: climb winds, cruise winds, descent winds, alternate wind. The subsequent uplink message may contain one or more of the following information: climb winds, cruise winds descent winds, alternate wind. When wind data are uplinked, whether automatically or in response to a manual request, the pilot has the opportunity to view the winds in a temporary store prior to insertion in the receiving flight plan.

 MCDU - ACARS Takeoff Data
 Figure 004

 UPLINK TO DATA REQ Page (with Default Values)
 Figure 005

 UPLINK FLX TO DATA Page (with Uplinked Data Not Inserted)
 Figure 006

 UPLINK MAX TO DATA page (with Uplinked Data Inserted)
 Figure 007

 The uplinked winds are directly displayed on the WIND pages; one WIND page exists per flight phase (CLIMB, CRUISE, and DESCENT, with the alternate wind displayed on the DESCENT WIND page). When inserted, valid uplink wind data overwrites all the previously defined wind data for the corresponding flight phase. Winds are sent either by altitude only or by an altitude/waypoint combination depending on the flight phase:
 -
in climb and descent, winds are sent by altitude only

 -
in cruise, winds are sent with the associated flight plan waypoints

 and are linked to cruise flight levels defined in the flight plan. A manual wind request from a WIND page may be initiated from either the active or secondary flight plan. The subsequent uplink is then associated to the flight plan from which the request was initiated. Otherwise, when a wind uplink is received which does not correspond to a pending request, the wind uplink is associated with active flight plan, when defined. Same wind pages are defined for primary and for secondary flight plan. (Ref. Fig. 008, 009, 010)

 CLIMB WIND Page (without Uplinked Data)
 Figure 008

 CRUISE WIND Page (with Wind Request Pending)
 Figure 009

 CLIMB WIND Page (after Reception of Wind Data)
 Figure 010

 (5) Flight reports Flight reports provide real-time information to the ground concerning the aircraft current situation and position. Several types of flight reports are available and consist of a position report, a progress report, a flight plan report and a performance data report. The position report provides current aircraft position information to the ground. The progress report provides data relative to the destination. The flight plan report provides the active lateral flight plan route to the ground. The performance data report provides the active performance data currently used by the FM. Each report is independent of each other. These reports are sent automatically in response to a ground request or upon satisfying predetermined conditions, though not all reports have the same activation mechanism. The unique requirements of each report are given in the following sections.
 (a)
 Position report (Ref. Fig. 011) A position report is sent in response to a ground request or automatically upon crossing a designated position reporting fix. Position reporting fixes are designated only by the ground in a position report uplink message. The position report may also be sent manually via a prompt on the MCDU. The manual sending of a position report may be inhibited via the Nav data base policy file (Ref. Para. D-(1)). Position reports are only sent relative to the active flight plan.

 (b)
 Progress report A progress report contains data relative to the aircraft arrival time and EFOB at the destination. This message is sent in response to a ground request or automatically upon crossing a designated trigger. Specific triggers may be customized by the airline in the Nav data base policy file (Ref. Para. D-(1). The progress report cannot be sent manually in a direct manner
　
中國航空網(wǎng) www.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：A320飛機維護(hù)手冊 AMM AUTO FLIGHT 自動飛行4(58)