A320X ATSU Tutorial PDF
A320X ATSU Tutorial PDF
ATSU TUTORIAL
AUA303: LOWW - EKCH
Revision Date: 21MAY19
A320-X ATSU Tutorial
Vienna – Copenhagen using Datalink
This tutorial not only covers datalink features, but also the interaction between the flight deck and the cabin, as
well as communication between ground handling and the flight deck, if GSX is used.
Note however that climb-, cruise- and descend wind download is not available without ActiveSky.
SimBrief
SimBrief can be accessed for free at the following website:
www.simbrief.com
FLIGHT PREPARATION
Setting up P3D and the FSL A320
Start Prepar3D and on the opening screen select the following items before loading the simulator:
4. If the A320 loads with engines running, open the MCDU and go to the panel state options. Then select the
“ON GPU” panel state.
The A320 is now placed at gate D22, or in case of the default P3D scenery somewhere near that gate (since the
default scenery, unfortunately, is incomplete and outdated).
Flight Planning
Some key data to use for creating the OFP with the flight planning software of your choice, in order to get the
same or similar data as shown in this tutorial:
• Planned ZFW: 61.0t
• Aircraft type: A320 with CFM engines
• Flight AUA303, STD 14:10h UTC
• Departure: LOWW / Destination: EKCH / Alternate: ESMS
• Route LOWW to EKCH via:
• LANUX L858 HDO M725 GERGA T239 PEROM T298 MONAK
• Departing runway: 11, SID: LANUX1A
• STAR and approach: MONAK1M, ILS approach RWY 04L
• Cruise Level: FL360
With this data in mind, go ahead and create the OFP accordingly. When done, export the OFP file to the following
folder: [Public Documents]\FSLabs Data\Routes
Weather
To recreate the weather and wind data in your OFP, use the following ActiveSky weather:
Active Sky Date and time: If Active Sky is not used, set the weather at your
Historical Weather Jan 30th 2019, 13:20h UTC convenience, with the following suggestions in mind,
to at least approximate some of the data:
• Surface wind: 120°/13kts
• Surface temperature: 1° C
-Important- This tutorial uses historical weather through ActiveSky. If historical weather is used, you must set the
ATSU weather source to ‘HIFI’. See the Introduction Guide’s ATSU chapter for more details on how to configure
this.
Whenever you use real time weather you may wish to use NOAA as weather source, to allow for SIGMET and
forecast data to be received.
AIRCRAFT PREPARATION
After the aircraft is initialised at the gate, using the ‘ON GPU’ panel state, external power is connected, chocks are
in place, the aircraft is empty. If you check the MCDU options payload page, you see that there’s no payload on
board except the crew.
For things to look and feel realistic, you’d want the jetway to be connected to the open L1 door. With GSX in use,
you may trigger the ground services without having to open any menu. Simply “talk” to the ground crew:
• Select ‘INT’ with the INT/RAD switch on the
Audio Control Panel (ACP) (1) to simulate
talking to the ground crew. This will trigger
de-boarding with GSX and therefore move 2
the jetway (or stairs) to the aircraft.
• Since the aircraft is empty already due to the
‘ON GPU’ panel state, the GSX de-boarding 3
process will be finished rapidly. There is no
other way to have GSX activated before
starting the actual boarding process.
Note: If GSX is not used, move the jetway
manually using the CTRL+J keys, or via the SODE 1
menu.
The aircraft is now ready to begin cockpit preparation.
COCKPIT PREPARATION
Start doing your usual cockpit preparation flow. Using datalink services such as ATSU does not change the
workflow, it simply inserts a few extra steps necessary for flight preparation. Steps the previously could not be
simulated realistically, since without datalink it was all based on pieces of paper passed between people.
One important new item to consider is time. The Flight Sim Labs datalink-based flight preparation workflow is
coded to be used together with realistic time intervals between the various steps necessary. However, there is no
need for concern. In a simulated environment, nobody is getting mad at you when you miss your scheduled
departure time, no passengers stop booking your airline due to missed connections. But simply trying to make the
scheduled time specified in the airline’s timetable gives you a new dimension of realism.
That being said, having loaded the scenario at 14:20h local time, it is now a few minutes passed that time, and the
flight AUA303 is scheduled to depart (meaning start the pushback) at 15:10h LT.
So start doing your cockpit preparation workflow, and use the following procedure as an add-on to what you are
already used to doing.
The next step is to initialise the AOC system, that part of ATSU used for information message exchange. ATSU
is also accessed via the MCDU, so press the ‘MCDU MENU’ page to leave the FMGC.
There select ‘ATSU’ followed by ‘AOC MENU’.
- AOC INIT
Of all available AOC pages, the AOC INIT page
should always be the first one to work through.
1
• Looking at the AOC INIT page you can see
that some data has already been filled
through that OFP download from the
previous step. To complete the initialisation, 2
first enter the flight number, you may use
either ICAO or IATA format, so for today use
‘AUA303’ (1). 5 4
• Next select ‘CREW DETAILS’ (2).
• Enter the designator for captain and first
officer, you may use any alpha-numerical
designator (3).
• Return to the previous page and press ‘INIT
DATA REQ*’ (4). This will then insert the 3
estimated time enroute (ETE) (5).
- OFP DATA
The OFP DATA page is used to confirm the data
from your OFP. Sending this data will provide
information to various ground handling stations,
such as fuel order and loadsheet calculation.
• Confirm all data corresponds to your OFP (1).
Carefully check the STD time (2). Make sure
it is the correct one, in this case 14:10h UTC.
However, if for some reason you’ll not be able 1
to meet the STD, you can add the amount of 1
minutes you need.
2
• Select the desired refuelling method (3).
Choose ‘VIA GSX’ if GSX is used, otherwise
use ‘AUTOMATIC’ to simulate the refuelling
3
process internally.
• Select ‘OFP DATA SEND’ (4). This will, 4
among other things, trigger the GSX
refuelling process.
- BOARDING
It’s too early for passenger boarding, however
what we do need at this stage is catering, water
and waste tank servicing. This can be done
while being refuelled and must be finished
before passengers arrive.
• In the AOC MENU select the ‘BOARDING’ 1
page. Then select ‘REQUEST’ with the LKS
6R to get to the 2nd boarding page (1).
• Type in the amount of water and catering you 2 2
require (2), and then select the ‘CATERING’ 3
option (3).
• Hit ‘REQUEST’ (4) to send the catering
request to the appropriate company.
If GSX is used, then the GSX catering
4
process is triggered.
If you do not use GSX, then you can load catering
manually on the MCDU options payload page.
A short while later, things around your aircraft might look like this:
While fuel, catering and water is being loaded, you do have some moments available for important system and
FMGC preparation tasks, such as:
• Align the three ADIRUs
• Check the FMGC flightplan and enter missing bits such as arrival- and approach segments.
- SLOT NOTIFICATION
• On the AOC MENU page select
‘RECEIVED MESSAGES’ (1) to see the
list of messages. 1
• You will see one message labelled “NEW”
(2). This message is sent to inform you
about the departure slot. 2
• The slot notification message includes the
following details from top to bottom (3):
- Flight Number / Departure / Destination
- Flightplan release number, usually 1 if
it is the first version.
3
- Calculated Take-Off Time (CTOT)
- Estimated Off-Block Time (EOBT)
- Delay, if any:
o AW = Weather delay, can occur with
low visibility, snow or strong winds.
o AX = ATC delay
o EN = Enroute delay, this would usually
be delay due to airway congestion.
- Estimated taxi time
If no delay is indicated, the EOBT will equal your STD. In any case, you need to be ready for pushback at the
specified EOBT.
This is a good time to think about when you want the passengers to start boarding the aircraft. You should aim for
boarding to start around 25 minutes before start-up. You can start as early as 40 minutes before EOBT. The
minimum time required would be 15 minutes, anything less than that will probably delay departure.
For this flight, let’s plan for boarding to start 30 minutes prior departure:
- BOARDING
On the AOC MENU page select
‘BOARDING’. This page allows you to send
a message to ground handling, as to when
you would like to start the boarding process.
• Type the desired boarding time into the
scratchpad (1), then select the empty
brackets below ‘BEGIN AT TIME’ (2).
2
• Select ‘REQUEST’ to submit the
message (3). 1 3
• Boarding will start at the time specified
(4).
If GSX is being used, then the GSX 4
boarding function will trigger
automatically at that time. Otherwise an
internal boarding simulation will gradually
Note: If for some reason the actual UTC time you see is already past
add passengers to the aircraft.
13:40h, you may select ‘BOARD NOW’ instead.
Weather Information
At this time, you’ll probably be waiting for the preliminary loadsheet to arrive. The perfect moment to get some
weather information downloaded.
- ATC REQ
Selecting ‘ATC REQ’ on the AOC menu
page, then ‘PRE-DEP CLRNCE’, allows you 1
to request the PDC:
2 3
• Some flight details are already filled in, so
enter ‘AUA303’ as the flight number (1),
your gate number (2), the ATIS info you
have read or listened to (3), and then hit
‘SEND’ (4).
• After you have received the PDC as a 4
message, you need to accept it, then this
will send a message to ATC, confirming Note: The online network controller needs to use the ACARS system
that you have accepted the PDC. to be able to answer your PDC request.
Loadhseet
Check your ATSU messages to see if the loadsheet has arrived. Once it has, open it and check all its pages:
- LOADSHEET
The loadsheet contains all the data you need
to complete the FMGC’s INIT B page.
1
• Select the loadsheet among the received
messages (1).
• Page 1 of the loadsheet will show you the
weight data needed for departure (2).
2
• Page 2 gives you the ZFW CG and the
TOW CG (3).
• Look through the remaining pages of the
loadsheet, then accept it by pressing the
LSK 5L (4).
• Fill in the ZFW and ZFWCG on the
FMGC’s INIT B page. 3
Note: This is only a preliminary loadsheet. The final
loadsheet will be sent to you after boarding has
completed. 4
Fuel Report
With refuelling completed, on the AOC menu page you will see the figure “6” next to the ‘FUEL’-prompt. This
means that the refuelling operator has uplinked a fuel report for you to confirm and send to your airline.
The fuel report contains a lot of numbers concerning the fuel that was ordered. However, it is pretty much self-
explanatory and can be confirmed quickly:
- FUEL
1
• Select the ‘FUEL’-page from the AOC
menu (1).
• Confirm the fuel quantity before refuelling
started (2) and the fuel on board now (3).
Calculate the difference, convert it to 7 4 2
volume and compare with the report (4).
5
• Austrian Airlines calculates in litres (5). To
confirm the fuel, multiply the weight of the 6 3
fuel you got added with the density factor
(6). 0.8 is sufficient, it does not have to be
more precise. 8
• If the value is the same as the one on the
report (4), type it into the scratchpad and
insert it at ‘VOLUME’ (7).
Note: Your actual fuel load may differ from the figures shown
• Send the report (8). here, depending on your calculations for the OFP you
created.
- PERF REQ
Select the ‘PERF REQ’ page within the AOC
menu. Then fill in the details as follows:
• Departure airport and runway (1).
• Confirm that packs off departure is set to 1 1
yes (<y>) (2). All other options are not
required, meaning that with the weather 5 4
scenario mentioned at the beginning of 3 2
this tutorial, the runway is neither wet (3),
nor is anti-ice required (4), due to lack of 6 7
visible moisture. Intersection departure is
also not needed (5).
8
• Fill in the surface wind (6), QNH (7) and
temperature (8) from the ATIS.
9 10
• TOGA thrust is not required (9), and we
want flaps config ‘1+F’ (10).
• Put in the estimated take-off weight (11) 11 12
and MACTOW (12), taken from the
preliminary loadsheet.
13
• Send the data (13).
- PERFORMANCE
Moments later you’ll see the performance
data amongst the list of messages (1). 1
• Select the message and use the arrow
keys to flip through all pages. Part of the
message contains the data on which the
calculations are based. Page 3 shows
you the take-off speeds (2), flaps (3) and
flex thrust setting (4).
2 3
• Open the FMGC take-off PERF page on
the other MCDU and enter the take-off 4
data there.
- WIND REQUEST
With cockpit preparation completed and passenger boarding coming to an end, here’s some items to observe and
take care of:
• Cabin crew will announce the completion of the boarding process via the passenger announcement system
(PA).
• A short time later, the L1 door will be closed by cabin crew.
• Make sure that you are running on APU power at this time.
• With all doors closed, instruct the cabin crew to arm the evacuation slides. Right-click the ‘PA’-button on the
ACP for around 3-4 seconds. Observe all slides showing as armed on the lower ECAM door page.
With boarding completed, expect the final loadsheet to arrive at any moment:
1
2
• Also take note of the final centre of gravity
numbers (3). 3
• Update the FMGC INIT B page
accordingly.
• Accept the final loadsheet (4).
• Use the MACTOW CG value to set the 4
stabiliser trim for departure.
If you’re running behind schedule, processing the final loadsheet may also be done during pushback or taxi.
ON THE MOVE
Gate Departure / Pushback
With the aircraft ready for push-back, all that is needed to get underway is talking to the ground crew. With the
clearance for pushback obtained, you may follow these steps to have a realistic flow for gate departure:
After engine start, do all the necessary cockpit flows and checklists. As soon as you start to taxi, take a moment
to go to the AOC menu page. If you select ‘INIT’, then the arrow keys for page 2, you may take note of the following
data:
Take-off
While taxiing to the runway, you may listen in on the PA channel if you want to, usually the volume is turned down
considerably, so that you don’t get distracted in your workflow.
At some point before reaching the runway, it may be that the only item on your checklist is the cabin report.
Depending on the equipment used, this report is being delivered solely by an ECAM message, by a phone call, or
both of them.
If a buzzer sounds:
• If you arrive at the runway holding point and the cabin has not yet reported ready, cycle the no-smoking sign
OFF and ON again, or press the FWD call button. This will give a signal to the cabin crew to hurry up.
Having done all that, take off and proceed with the flight as usual.
Before Landing
At any time before landing, you may request up-to-date weather data via the AOC ATIS/WX page.
If you are using one of the “Airline Packs” available in the forum’s download section, one of the files installed
contains a list of all gates used at the airports serviced by that particular airline.
In that case you will receive a company message towards the end of your flight, notifying you of the gate to be
used at the destination. Having received that information will enable you to determine the best exit taxiway to use,
and to plan your landing accordingly.
Later during the approach, the cabin crew will again inform you once the cabin is ready. Expect to receive an
ECAM memo and/or a intercom phone call.
After Landing
At any convenient time after landing, access the AOC INIT page again, to review the flight and send a report:
• Arriving at the gate, you can start the de-boarding process by selecting once more ‘INT’ with the INT/RAD-
switch on the Audio Control Panel.
• If GSX is used, the GSX de-boarding process is initiated.
• If no GSX is present, an internal de-boarding process is started, removing the payload gradually to simulate
cargo and passengers being unloaded.
• After having sent the flight report above, head over to Hoppie’s ACARS website to see the flight report:
www.hoppie.nl/acars/system/log.html
This flight report includes time-, fuel- and landing data.
DEBRIEFING
If you arrived at this page after having completed your first flight using ATSU, or you might just have read through
the document in preparation, you might probably be terrified about the added complexity to a normal routine flight.
If this is the case, you don’t need to worry. After you have done the ATSU flow a couple of times, it will feel perfectly
natural and you’ll perceive it as something that makes work much easier, because it allows you to have all
necessary data at hand.
This ATSU-centred workflow allows for a seamless interaction between you in the flight deck, your cabin crew
behind you, and the ground handling personnel outside. It allows you to experience airliner operations as it is done
in today’s modern world, paperless and with the aircraft linked in a chain of computers which are all delivering and
receiving data to make life easier for every person involved.
If you want to do your own flight next, you may still use this document as a guide, as the steps remain the same
for each flight, only the data changes accordingly.