Aircraft Communications Addressing, and Reporting System (ACARS)
ACARS is a digital datalink system for transmission of short messages between aircraft and ground stations via airband radio or satellite.
The protocol was designed by ARINC and deployed in 1978, using the Telex format. More ACARS radio stations were added subsequently by SITA.
ACARS messages will be sent as soon as the Aircraft detects an antenna. If no antenna is detected the message will be halted and sent later.
ACARS integration with N-OC is set up in the menu COM CHANNELS:
COM:
The airline pay ARINC/SITA per message sent. To minimize the cost, it is possible to bounce the ACARS message from the ARINC OPSCENTER or the SITA Gateway to an email account.
Criteria | Description |
Name | This field is mandatory. |
IN/OUT | IN |
Host | Provider . eg. smtp.gmail.com |
Port | Normally port 993, but check with the provider |
SSL | Secure Socket Layer. Maybe the provider requires this option. |
User | Always Sleipner. |
User Name | Enter Email account. |
Password | Password to the Email account |
Communication type | Enter Email. |
File type | ARINC, SITA or SITATEX. Depending on the message format. |
Cycle Time | Time is in seconds. |
Example:
N-OC accepts the following ACARS messages:
DEP
Criteria | Description |
Flight number | PD458 |
Vehicle registration | C-GLQB |
Departure station (ICAO) | CYHZ |
Arrival station (ICAO) | CYHZ |
BlockOff time | OT |
TakeOff time | OF |
FB | If (OT) -> Fuel On Board. If (OF (with or without OT)) -> Take Off Fuel unit is defined by setup ACARSFuelUnit – if not defined, then kgs |
DT DDL YHZ 141110 M05A | time of message and DEP station (IATA). We parse only 141110 -> 14AUG19 1110 and it's message time, which is used if ACARS message contains not complete information (e.g. only flight number without stations) – then application tries to obtain |
ARR
Criteria | Description |
ON | touch down time |
IN | block on time |
FB | if (ON) -> Fuel Arrival if (OT) -> fuel remaining |
A80
Criteria | Description |
Flight number | VV378/ |
Vehicle registration | HK-4811 |
Message time | 131432 |
Departure station IATA | LIM |
Departure station (ICAO) | SPJC |
Arrival station (ICAO) | SPST |
Block off time | OUT |
Take off time | OFF |
Touch down time | ON |
Block on time | IN |
FOB | Fuel on board in the different stages of OOOI |
|
|
A80 | can contain all of OUT, OFF, ON, IN |
A8A | only OUT |
A8B | only OFF |
A8C | only ON |
A8D | only IN |
A8E | only RTN (return to ramp) |
A83 |
|
A85, A87, A8E | do not contain OOOI times, but contain Free Text |
Criteria | Description |
A81 A84 | Free Text. The message will be displayed as a MVT note on the flight. |
AGM, and A80 | with subtype OPSCTL - contain FreeTexts |
Note: If you receive new messages from the pilot, a circle with a number will indicate the number of new messages.
M3K - OUT
Criteria | Description |
Flight number | S66382 |
Vehicle registration | OY-SRG |
OUT date and time | 120157 |
Departure station (ICAO) depending on airline it can be IATA | LFML |
Arrival station (ICAO) | LFBD |
Fuel on board | xxxx |
M3B - OFF
Criteria | Description |
flight number | S66382 |
vehicle registration | OY-SRG |
OFF date and time | 120211 |
Date/ departure station (ICAO) | 12LFML0157 |
OFF and ETA at arrival station (ICAO) | 02110307LFBD |
M3I - ON
Criteria | Description |
Flight number | S66382 |
Vehicle registration | OY-SRG |
ON date and time | 120302 |
Date/departure station (ICAO) | 12LFML |
ON at arrival station (ICAO) | LLFBD0302 |
M31 - IN
Criteria | Description |
Flight number | S66382 |
vehicle registration | OY-SRG |
IN date and time | 120309 |
Date/departure station (ICAO)/ | 12LFML |
ON and IN at arrival station (ICAO) | LFBD03020308 |
Fuel on board | 0118034 |
M31 - M34
These messages are mainly used in the APAC area.
M31 OUT
Criteria | Description |
Flight number | RH331 |
Vehicle registration | B-LNX |
OUT date and time | 122217 |
Departure station (IATA) | HKG |
ICAO Departure and Arrival Airport. Sleipner will verify the ICAO codes | VHHH VTBS |
M1A TAX
Criteria | Description |
Flight number | RH331 |
Vehicle registration | B-LNX |
OUT date and time | 122224 |
Departure station (IATA) | HKG |
Fuel on board | 243 |
ICAO Departure and Arrival Airport. Sleipner will verify the ICAO codes | VHHH VTBS |
M32 OFF
Criteria | Description |
Flight number | RH331 |
Vehicle registration | B-LNX |
OUT date and time | 122239 |
Departure station (IATA) | HKG |
Take Off fuel | 242 |
Fuel consumption, this field is not read. | 0006 |
ICAO Departure and Arrival Airport. Sleipner will verify the ICAO codes | VHHH VTBS |
M33 ON
Criteria | Description |
Flight number | RH331 |
Vehicle registration | B-LNX |
ON date and time | 130055 |
Arrival station (IATA) | DMK |
Arrival fuel | 108 |
Fuel Burn. (Fuel on board - Arrival fuel) | 0134 |
ICAO Departure and Arrival Airport. Sleipner will verify the ICAO codes | VHHH VTBS |
M4A
Criteria | Description |
Flight number | RH331 |
Vehicle registration | B-LNX |
ON date and time | 130055 |
Arrival station (IATA) | DMK |
Remaining fuel | 101 |
Fuel Burn. (Fuel on board - Arrival fuel) | 0138 |
ICAO Departure and Arrival Airport. Sleipner will verify the ICAO codes | VHHH VTBS |
M34
Criteria | Description |
Flight number | RH331 |
Vehicle registration | B-LNX |
ON date and time | 130055 |
Arrival station (IATA) | BKK |
Remaining fuel | 101 |
Fuel Burn. (Fuel on board - Arrival fuel) | 0138 |
ICAO Departure and Arrival Airport. Sleipner will verify the ICAO codes | VHHH VTBS |
M3A - not supported
M3E
M39 - not supported
RTN
Flight activity info
The data from the ACARS message will update the Flight activity window.
All received Messages can be found in the message tab.
Times are in the Times section
Notes:
ACARS doesn't have Delay reasons in the message. Those come from the MVT message or entered manually
The last message wins. Meaning that if MVT is received after the Acars, then the mvt times are taken.
If the Arrival messages come before the Departure message, there is a risk that the Dep message will be rejected.
Fuel is in the Fuel section
Down link
NOC can receive A81, A84 and AGM text messages from the aircraft.
The message is shown on the flight as a MVT note and on the aircraft panel number of unread messages are shown.
Receiving the message
- Right click in the aircraft panel
- Select the ACARS symbol or click on the message bubble.
- An open the message window will appear and the messages from the selected aircraft will be shown.
Note: You can search for a period or aircraft.
Uplink
The uplink method can be different from airline to airline depending on the Vendor of the equipment in the aircraft and the communication vendor (ARINC, Sita etc.).
- The Communication vendor will search for the aircraft and deliver the message.
- Enter the message, click Next.
- A window with the ACARS receivers will open.
Note: For this to work, you need to specify an ACARS template for the aircraft. See Aircraft Uplink template.
Configuration in Integration Factory
You need to create a template and an event.
- In the Integration factory you create the basic body of the message.
- Press “Finish” to execute.
- The template is used in the ACARS Message Uplink Event tab which can be found in the Automation Factory menu.
COM Channel
- Add the receiver COM channel.
Setup Parameters
Go to Setup while searching for “Setup” in the search field.
ACARSFuelUnit
Fuel unit for ACARS messages
- Enter either kgs/liters/tons/lbs/gallons. Fuel unit multiplier is used to multiply the input from ACARS.
Note: For default "Kgs" is selected. The final selection must be saved.
Fuel unit multiplier:
ACARSReferenceDateMode
Defines ACARS mode for searching flights
Options: UTC/Local/Ignore
AllowedIncomingMessagePeriod
Hours before and after current time. Sleiper will only process incoming messages for flights in this period. Empty field disables the setting.
Format: hours, hours
Note: This parameter is important if you operate the same flight number every day.
Refer to: Incoming Messages for further details.