(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.

 REPORT Page (Prompt for Downlink of Position Report)
 Figure 011

 Manual sending of a flight plan report can be inhibited via the Nav data base policy file (Ref. Para. D-(1)).
 (d) Performance data report The performance data report allows the transmission of performance data (weight, fuel, CG, etc.) from the active route to the ground. This message is sent automatically in response to a ground request for the performance data report.
 (6)
 Response downlink messages

 (a)
 Rejection message When an error has been detected in an uplink message, the rejection message transmits an error code identifying the reason for rejecting the message.

 (b)
 Response message When an uplink message has not been rejected by the system, a response message is downlinked indicating whether it is accepted and inserted in the system by the pilot or cancelled by the pilot.

 (7)
 Broadcast data This is a set of data which is automatically broadcast by the FM on the output ACARS bus to the ACARS MU if ACARS is installed. Use of these data (selection of data, time of transmission to ground, etc.) is entirely defined by the MU. The transmission protocol of broadcast data is left to the ACARS MU. Activation or de-activation of downlink transmission is made in the ACARS MU and not in the Nav data base policy file. This set of data is not printed by any FM function. Nevertheless, some data may be part of printed reports or uplink printouts. Transmitted data are:

 -Flight Number
 -Active Data Base
 -Company Route
 -Active Waypoint
 -
Wind Velocity

 -
Wind Direction

 -Zero Fuel Weight
 -Block Fuel
 -Fuel On Board
 -Aircraft Gross Weight
 -Destination Runway (Ref. NOTE)
 -Alternate Destination
 -Estimated Time of Arrival
 -
Discrete AP Modes

 -
Discrete Flight Phase.

 NOTE : Destination Runway is Destination Airport Ident (4 characters)
____ if no runway is defined; else it is Runway Ident (7 characters).

 B. PRINT Function

 (1)
 General description The PRINT function allows various FM reports to be printed, either automatically or on manual action. This function is completely independent of the ACARS function and is available even if the ACARS is not installed. Additionally, several features of the PRINT function are optionally programmable either through the Nav data base policy file (Ref. Para. D-(1)) or through manual selection on the MCDU. Several types of reports can be printed. These include flight plan initialization data, takeoff data, wind data and flight report data. Flight plan data, takeoff data and wind data can be either data uplinked via the ACARS or actual system data. Flight report data are available as pre-flight, in-flight and post-flight information, composed of predicted data, actual data or a combination of the two. ACARS-generated flight plan initialization, takeoff and wind data may be printed when they are received and checked by the FM if the automatic print function is activated within the Nav data base policy file and on the PRINT FUNCTION page. Current FM flight plan initialization, takeoff and wind data may be printed upon manual action by pushing the line key adjacent to the PRINT indication on the PRINT FUNCTION page. FM-generated flight reports may be automatically printed at predefined events if the automatic print function is activated within the Nav data base policy file and on the PRINT FUNCTION page or upon manual action by pushing the line key adjacent to the PRINT indication on the PRINT FUNCTION page. Generally, a print report initiated by a manual action consists of FM data whereas a report initiated automatically consists of ACARS uplinked data (an exception occurs for flight reports which may be printed automatically). Manually-initiated reports can be generated at any time. However, the printing of the flight plan initialization, takeoff and wind reports are mutually exclusive of each other; only one present report can be active at a time, although the print requests may be queued. While a report is printing (either manually or automatically initiated), triggers for automatic printing of the same type of report are ignored.