0% found this document useful (0 votes)
21 views12 pages

PDF N Fcom Sva TF N Eu 20120817 DSC 22 45

Uploaded by

kaspour
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
21 views12 pages

PDF N Fcom Sva TF N Eu 20120817 DSC 22 45

Uploaded by

kaspour
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 12

AIRCRAFT SYSTEMS

AUTO FLIGHT - AOC FUNCTIONS


Intentionally left blank
AIRCRAFT SYSTEMS
AUTO FLIGHT - AOC FUNCTIONS
A318/A319/A320/A321
FLIGHT CREW PRELIMINARY PAGES - TABLE OF CONTENTS
OPERATING MANUAL

DSC-22_45-PLP PRELIMINARY PAGES


TABLE OF CONTENTS

General.....................................................................................................................................................................A
Flight Plan Initialization Function.............................................................................................................................B
Takeoff Data Function............................................................................................................................................. C
Wind Data Function.................................................................................................................................................D
Flight Reports...........................................................................................................................................................E

SVA A318/A319/A320/A321 FLEET DSC-22_45-PLP-TOC P 1/2


FCOM 07 APR 11
AIRCRAFT SYSTEMS
AUTO FLIGHT - AOC FUNCTIONS
A318/A319/A320/A321
FLIGHT CREW PRELIMINARY PAGES - TABLE OF CONTENTS
OPERATING MANUAL

Intentionally left blank

SVA A318/A319/A320/A321 FLEET DSC-22_45-PLP-TOC P 2/2


FCOM 07 APR 11
AIRCRAFT SYSTEMS
AUTO FLIGHT - AOC FUNCTIONS
A318/A319/A320/A321
FLIGHT CREW
OPERATING MANUAL

GENERAL
Applicable to: ALL

The FMS AOC function gives an interface between a ground station and one onboard FMGC,
allowing data transmission between these two computers via the ACARS Management Unit or the
ATSU.
Two different sets of message can be exchanged:
UPLINK messages from the ground station. They consist in reception of data requested or directly
sent to the crew.
DOWNLINK messages from the FMGC (master). They consist in reports or requests sent to the
ground station.
The FMGS/ACARS or FMGS/ATSU interface enables the following AOC capabilities.
‐ F-PLN initialization (flight plan and performance data)
‐ Takeoff data
‐ Wind data
‐ Flight reports
‐ Broadcast data
Crews can send message using ACARS FUNCTION pages or relevant MCDU pages.
Only one FMGC talks to the ground station. This FMGC is called FMGC “master”.
GENERAL SCRATCHPAD MESSAGES
NOT XMITTED TO ACARS: A crew request or report was sent to the ground but the
communication was not established or not acknowledged.
NO ANSWER TO : A crew request was previously sent to the ground and no answer
REQUEST (uplink message) was received within 4 min.

FLIGHT PLAN INITIALIZATION FUNCTION


Applicable to: ALL

This function enables lateral and vertical flight plan data as well as initialization data to be exchanged
between the aircraft and a ground station. The aircraft may send flight plan requests for active and
secondary flight plan. (downlink messages). The ground station may send flight plan and initialization
data (uplink messages) either under aircraft request or automatically without any request.
Each uplink message concerns either the active or secondary flight plan but never both flight plans at
the same time. The data sent to the aircraft are checked for flight plan consistency.
An MCDU message comes up when an uplink message is received. “ACT (or SEC) RTE UPLINK”.
If an error prevents the decoding process of the message, “INVALID RTE UPLINK” is displayed on
the MCDUs.

SVA A318/A319/A320/A321 FLEET DSC-22_45 P 1/8


FCOM A to B → 07 APR 11
AIRCRAFT SYSTEMS
AUTO FLIGHT - AOC FUNCTIONS
A318/A319/A320/A321
FLIGHT CREW
OPERATING MANUAL

An uplink message can be routed to the active flight plan if no engine is started and no active flight
plan exists. Otherwise, it is routed to the secondary flight plan. The flight crew will insert it into the
secondary flight plan or will reject it using the CLR key.
Note: The flight plan may also be initialized using the AOC FUNCTION page selected from DATA
INDEX page.

INITIALIZATION DATA
On ground and before engine start, the ground station may also send data to initialize the F-PLN.
This data is always associated with the uplink flight plan. It is either automatically inserted with the
active flight plan data, or stored in the secondary with the corresponding flight plan.
Initialization data is made of part or all of the following elements:
ZFW, ZFWCG, taxi fuel, block fuel, cruise flight level, tropopause altitude, cruise temperature,
transition altitude, cost index, performance factor.
Note: After engine start an uplink initialization data message is rejected automatically without
any scratchpad message.
SCRATCHPAD MESSAGES RELATED TO FLIGHT PLAN AND INITIALIZATION DATA
INVALID RTE UPLINK An error is detected, the uplink message is rejected.
ACT or SEC RTE UPLINK A F-PLN is stored in the active or secondary flight plan.
FLT NUMBER UPLINK FLT NBR has been initialized within a F-PLN message without
previous request.
CHECK FLT NUMBER The uplinked FLT NBR differs from the one specified in the request.

SVA A318/A319/A320/A321 FLEET DSC-22_45 P 2/8


FCOM ←B→ 07 APR 11
AIRCRAFT SYSTEMS
AUTO FLIGHT - AOC FUNCTIONS
A318/A319/A320/A321
FLIGHT CREW
OPERATING MANUAL

CHECK CO RTE The uplinked CO RTE ident differs from the one specified in the
request.
INVALID FLT NBR UPLINK The uplink contains a valid F-PLN but the FLT NBR is invalid.
INIT DATA UPLINK Initialization data is received
INVALID INIT UPLINK Initialization uplink message has been rejected
RTE DATALINK IN PROG A flight plan modification is performed after a F-PLN INIT request has
been sent; this message is displayed until the uplink is received.
UPLINK INSERT IN PROG This message is displayed during insertion of a Flight Plan.

TAKEOFF DATA FUNCTION


Applicable to: ALL

The takeoff data function is available for the active flight plan only. It is used to request to the ground
station, information data for up to 2 runways and to receive this data for up to 4 runways.
The crew sends a request indicating the departure airport, runway idents, CG, GW and weather
conditions (such as BARO setting wind, temperature...). In response he receives the takeoff speeds
for up to 4 runways but only one set of data may be inserted in the active flight plan for the selected
active runway.
Takeoff speeds are computed for max and flex takeoff.
The takeoff data function has required the modification of the standard PERF TAKEOFF page and
the addition of 2 news pages:
• UPLINK TO DAT REQ page that enables the crew to specify a request to the ground.
• UPLINK XXX TO DATA page (XXX for MAX or FLEX)
These 2 pages are accessed from the PERF TAKEOFF page in PREFLIGHT and DONE phase only.

SVA A318/A319/A320/A321 FLEET DSC-22_45 P 3/8


FCOM ← B to C → 07 APR 11
AIRCRAFT SYSTEMS
AUTO FLIGHT - AOC FUNCTIONS
A318/A319/A320/A321
FLIGHT CREW
OPERATING MANUAL

SCRATCHPAD MESSAGES RELATED TO TAKEOFF DATA


TAKEOFF DATA UPLINK : Takeoff data uplink message is received
INVALID TAKEOFF : The UPLINK message is rejected
UPLINK

WIND DATA FUNCTION


Applicable to: ALL

This function enables the crew to request and to receive forecasted winds associated to the active or
secondary flight plan.
The uplink message (ground station to aircraft) may be received upon crew request or automatically
without crew request.
The request is initiated from WIND pages or from ACARS FUNCTION page (Refer to
DSC-22_20-70-B Wind Data - Request for Wind Data).

SVA A318/A319/A320/A321 FLEET DSC-22_45 P 4/8


FCOM ← C to D → 07 APR 11
AIRCRAFT SYSTEMS
AUTO FLIGHT - AOC FUNCTIONS
A318/A319/A320/A321
FLIGHT CREW
OPERATING MANUAL

The uplink wind data when received are directly displayed on the wind pages but not inserted in the
flight plan, one set for each flight phase: CLIMB, CRUISE, DESCENT. The alternate wind at alternate
cruise flight level is displayed on DESCENT page.
‐ Winds are associated to altitude for climb an descent phases
‐ Winds are associated to waypoint for cruise phase and step level. One wind per waypoint.
• On ground and without entered winds, an uplink message is directly inserted in the flight plan.
• In flight, winds are temporary stored until the crew inserts it phase per phase.
Phase of flight is indicated in the WIND title page.
• Clearing the INSERT UPLINK* prompt using the CLR key deletes the uplink wind data for the
selected phase.
When uplink winds are deleted, the wind page reverts to the previous status.
The flight plan B page is modified of the uplink wind only after it is inserted by the crew. AOC uplink
winds are then considered as crew manual entries (large font).
SCRATCHPAD MESSAGES RELATED TO WIND DATA
INVALID WIND UPLINK An error is detected, the uplink is rejected.
WIND DATA UPLINK Uplinked winds are received.
WIND UPLINK PENDING A temporary flight plan exists or a DIR TO page is displayed when a
wind uplink is received. The message is stored.
WIND UPLINK EXISTS A F-PLN modification (active or secondary) is attempted when uplink
winds are not inserted. This message disappears automatically when
the wind uplink is inserted or deleted.
CHECK DEST DATA The aircraft is at 180 nm from destination, and the destination QNH,
TEMP or WIND displayed on the PERF APPR page was received by
AOC uplink or, if following insertion of a descent wind uplink, a conflict
concerning the above parameters exists.
CHECK ALTN WIND The uplinked alternate cruise flight level differs from the default
alternate cruise flight level.

FLIGHT REPORTS
Applicable to: ALL

Flight reports provide real time information to the ground concerning the aircraft current situation and
position.
Several types of flight reports are available:
‐ The Position report : provides current aircraft position
‐ the Progress report : provides data relative to the destination

SVA A318/A319/A320/A321 FLEET DSC-22_45 P 5/8


FCOM ← D to E → 07 APR 11
AIRCRAFT SYSTEMS
AUTO FLIGHT - AOC FUNCTIONS
A318/A319/A320/A321
FLIGHT CREW
OPERATING MANUAL

‐ The Flight-Plan report : provides the active route


‐ the Performance Data report : provides performance data currently used by FMS.
These reports may be manually initiated via a dedicated prompt or automatically sent in response to
a ground request or upon specific conditions.
POSITION REPORT
This report is sent:
‐ manually via a MCDU prompt or
‐ following a ground request or
‐ automatically upon sequencing a designated reporting fix (designated by the ground in a uplink
message).
The manual POSITION REPORT downlink prompt is displayed on the PROG page. (SEND POS
prompt).

Note: Position report are initiated from active flight plan only.
POSITION REPORT CONTENT
‐ Aircraft position
‐ Overfly reporting waypoint
‐ Time of report (UTC)
‐ Aircraft altitude
‐ Next reporting waypoint
‐ ETA at next reporting waypoint
‐ Reporting waypoint following next report
‐ SAT
‐ Current wind
‐ Remaining fuel

SVA A318/A319/A320/A321 FLEET DSC-22_45 P 6/8


FCOM ←E→ 07 APR 11
AIRCRAFT SYSTEMS
AUTO FLIGHT - AOC FUNCTIONS
A318/A319/A320/A321
FLIGHT CREW
OPERATING MANUAL

PROGRESS REPORT
A progress report contains data relative to the aircraft arrival time and EFOB at destination for the
active F-PLN.
This downlink message is automatically sent following:
‐ a ground request or
‐ a change of destination or
‐ a change of runway or
‐ a specific event. The possible events that can be selected in the navigation database policy file
are :
• X minutes to Top of Descent
• Z minutes to Destination
• ETA changes more than W minutes from the previous report.
X, Z and W are minutes of time set in the navigation database policy file.
The progress report cannot be manually sent by the crew via a dedicated MCDU prompt.
PROGRESS REPORT CONTENT
‐ Flight Number
‐ Arrival Airport Ident
‐ Destination Runway Ident
‐ Predicted remaining fuel
‐ ETA at destination
‐ Reason for report (specific event, ground request...).
FLIGHT PLAN REPORT
The F-PLN report broadcasts flight plan data to the ground. Only data from the active flight plan
can be sent.
This downlink message is sent to the ground:
‐ automatically following a ground request
‐ manually by the crew using a prompt displayed on the ACARS FUNCTION page ( DSC-22_20
Auto Flight - Flight Management/50 Controls and Indicators/10 MCDU - Page Description/25
FMS2 Honeywell/ACARS Function Page). This prompt may be invalidated through the
navigation database policy file.
The Flight Plan report can be downlinked either while on ground or in flight during any flight phase.
FLIGHT PLAN REPORT CONTENT
The report contains the active and alternate flight plan.

SVA A318/A319/A320/A321 FLEET DSC-22_45 P 7/8


FCOM ←E→ 07 APR 11
AIRCRAFT SYSTEMS
AUTO FLIGHT - AOC FUNCTIONS
A318/A319/A320/A321
FLIGHT CREW
OPERATING MANUAL

PERFORMANCE DATA REPORT


The Performance Data report is a downlink message that allows the transmission of performance
data (CG, FUEL, CG...) relative to the active F-PLN.
This message is automatically sent following a ground request. Manual sending is not possible.
PERFORMANCE DATA REPORT CONTENT
Sends to the ground:
‐ Current GW
‐ Cruise Altitude
‐ Current CG
‐ Fuel on Board
‐ Block Fuel
‐ Reserve Fuel
‐ Cost Index
‐ Top of Climb Temperature
‐ Climb Transition Altitude
‐ Tropopause Altitude
‐ Taxi Fuel
‐ ZFW
‐ ZFWCG

SVA A318/A319/A320/A321 FLEET DSC-22_45 P 8/8


FCOM ←E 07 APR 11

You might also like