UPLINK FLX TO DATA Page (with Uplinked Data Not Inserted)
Figure 007
UPLINK MAX TO DATA Page (with Uplinked Data Inserted)
Figure 008
(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. However, if the A/C is on ground, prior to engine start and the data have not get been entered or inserted on any wind page of the receiving FPLN, then wind data are directly inserted into that FPLN without passing through a temporary review state. 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 various flight levels. 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. (Ref. Fig. 009, 010, 011)
CLIMB WIND Page (without Uplinked Data)
Figure 009
CRUISE WIND Page (with Wind Request Pending)
Figure 010
CLIMB WIND Page (after Reception of Wind Data)
Figure 011
(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. 012) 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 AOC policy file of the AMI (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 AOC policy file of the AMI (Ref. Para. D-(1). The progress report cannot be sent manually in a direct manner
(e.g. via a dedicated prompt). However, the message may result from a pilot action (e.g. changing the destination). Progress reports are only sent relative to the active flight plan.
(c)
Flight plan report The flight plan report allows the transmission of flight plan data from the active route to the ground. This message is sent either via a manual selection of a prompt on the MCDU or automatically in response to a ground request.
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：A320飞机维护手册 AMM AUTO FLIGHT 自动飞行4(68)
