Create account

Log in

Article Talk

Read Edit View history

Search

Aircraft Communications Addressing and Reporting System

From Wikipedia, the free encyclopedia Main page Contents Featured content Current events Random article Donate to Wikipedia Interaction Help About Wikipedia Community portal Recent changes Contact Wikipedia Toolbox Print/export Languages Deutsch Franais Italiano

This article has multiple issues. Please help improve it or discuss these issues on the talk page . This article may require copy editing for improper tenses and excessive acronyms. (January 2013)
The template below (Expert-subject ) is being considered f or possible deletion. See templates f or discussion to help reach a consensus.

This article needs attention from an expert in Aviation. The specific problem is: references and information on current technology. (January 2013) This article includes a list of references, but its sources remain unclear because it has insufficient inline citations. (April 2012) Aircraft Communications Addressing and Reporting System (ACARS) is a digital datalink system for transmission of short, relatively simple messages between aircraft and ground stations via radio or satellite. The protocol, which was designed by Aeronautical Radio, Incorporated (ARINC) to replace their very high frequency (VHF) voice service and deployed in 1978, [1] uses telex formats. SITA later augmented their worldwide ground data network by adding radio stations to provide ACARS service. Over the next 20 years, ACARS will be superseded by the Aeronautical Telecommunications Network (ATN) protocol for Air Traffic Control communications and by the Internet Protocol for airline communications.
Are you a developer? Try out the HTML to PDF API

open in browser PRO version

pdfcrowd.com

Nederlands Norsk bokml Polski Portugus Suomi Trke Edit links

Contents [hide] 1 History of ACARS 1.1 Introduction of ACARS systems 1.2 OOOI events 1.3 Flight management system interface 1.4 Maintenance data download 1.5 Interactive crew interface 2 How it works 2.1 VHF subnetwork 2.2 SATCOM and HF subnetworks 2.3 Datalink message types 3 Example transmissions 3.1 Departure delay downlink 3.2 Weather report uplink 3.3 FDAMS message downlink 4 Aircraft equipment 5 Datalink service provider 6 Ground end system 7 ARINC specifications 8 Acronyms and glossary 9 GIS and data discovery 10 See also 11 References 12 External links

History of ACARS

[edit]

Prior to the introduction of datalink, all communication between the aircraft (i.e., the flight crew) and personnel on the ground was performed using voice communication. This communication used either VHF
open in browser PRO version
Are you a developer? Try out the HTML to PDF API

pdfcrowd.com

or HF voice radios, which was further augmented with SATCOM in the early 1990s. In many cases, the voice-relayed information involved dedicated radio operators and digital messages sent to an airline teletype system or its successor systems.

Introduction of ACARS systems

[edit]

The engineering department at Aeronautical Radio, Inc (ARINC), in an effort to reduce crew workload and improve data integrity, introduced the ACARS system in July 1978. The first day of operations saw about 4,000 transactions. A few experimental ACARS systems were introduced earlier, but ACARS did not start to get any widespread use by the major airlines until the 1980s. The original ARINC development team was headed by Crawford Lane and included Betty Peck, a programmer, and Ralf Emory, an engineer. The terrestrial central site, a pair of Honeywell Level 6 minicomputers, and (AFEPS) software were developed by a subcontractor, Eno Compton of ECOM, Inc. Although the term ACARS is often understood as the data link avionics line-replaceable unit installed on aircraft, the term actually refers to a complete air and ground system. The original expansion of the abbreviation was Arinc Communications Addressing and Reporting System.[2] Later, it was changed to Airline Communications, Addressing and Reporting System. On the aircraft, the ACARS system was made up of an avionics computer called an ACARS Management Unit (MU) and a Control Display Unit (CDU). The MU was designed to send and receive digital messages from the ground using existing VHF radios. On the ground, the ACARS system was made up of a network of radio transceivers managed by a central site computer called AFEPS (Arinc Front End Processor System), which received (or transmitted) the datalink messages as well as routed them to various airlines on the network. The initial ACARS systems were designed to ARINC Characteristic 597. This was later upgraded in the late 1980s by the publication of ARINC Characteristic 724. ARINC 724 is intended for aircraft installed with avionics supporting digital data bus interfaces. ARINC 724 was updated to the current standard ARINC Characteristic 724B, which is the predominate standard for all digital aircraft. [clarification needed] With the introduction of ARINC 724B, the ACARS MUs were also coupled with industry standard protocols for operation with flight management system MCDUs (ARINC 739), and printers (ARINC 740 and ARINC 744).
open in browser PRO version
Are you a developer? Try out the HTML to PDF API

pdfcrowd.com

The ACARS MU has been since expanded to serve broader needs using a Communications Management Unit (CM) defined by ARINC Characteristic 758. Today, new aircraft designs integrate CM functions in Integrated Modular Avionics (IMA). ARINC Standards are prepared by the Airlines Electronic Engineering Committee (AEEC).

OOOI events

[edit]

One of the initial applications for ACARS was to automatically detect and report changes to the major flight phases (Out of the gate, Off the ground, On the ground, and Into the gate), referred to in the industry as OOOI.[3] These OOOI events are determined by algorithms that use aircraft sensors (such as doors, parking brake and strut switch sensors) as inputs. At the start of each flight phase, a digital message is transmitted to the ground containing the flight phase, the time at which it occurred, and other related information such as amount of fuel on board or flight origin and destination. These messages are used to track the status of aircraft and crews.

Flight management system interface

[edit]

In addition to detecting events on the aircraft and sending messages automatically to the ground, initial systems were expanded to support new interfaces with other on-board avionics. During the late 1980s and early 1990s, a datalink interface between the ACARS MUs and Flight Management Systems (FMS) was introduced. This interface enabled flight plans and weather information to be sent from the ground to the ACARS MU, which would then be forwarded to the FMS. This feature gave the airline the capability to update FMSs while in flight, and allowed the flight crew to evaluate new weather conditions, or alternative flight plans.

Maintenance data download

[edit]

The introduction in the early 1990s of the interface between the FDAMS / ACMS systems and the ACARS MU resulted in datalink's gaining wider acceptance by airlines. The FDAMS / ACMS systems which analyze engine, aircraft, and operational performance conditions were now able to provide performance data to the airlines on the ground in real time using the ACARS network. This reduced the need for airline personnel to go to the aircraft to off-load the data from these systems. These systems were capable of
open in browser PRO version
Are you a developer? Try out the HTML to PDF API

pdfcrowd.com

identifying abnormal flight conditions and automatically sending real-time messages to an airline. Detailed engine reports could also be transmitted to the ground via ACARS. The airlines used these reports to automate engine trending activities. This capability enabled airlines to better monitor their engine performance and identify and plan repair and maintenance activities. In addition to the FMS and FDAMS interfaces, the industry started to upgrade the on-board maintenance computers in the 1990s to support the transmission of maintenance-related information in real-time through ACARS. This enabled airline maintenance personnel to receive real-time data associated with maintenance faults on the aircraft. When coupled with the FDAMS data, airline maintenance personnel could now start planning repair and maintenance activities while the aircraft was still in flight.

Interactive crew interface

[edit]

All of the processing described above is performed automatically by the ACARS MU and other associated avionics systems, without flight crew intervention. As part of the growth of ACARS functionality, the ACARS MUs also interfaced directly with a control display unit (CDU), located in the cockpit. This CDU, often referred to as an MCDU or MIDU, provides the flight crew with the ability to send and receive messages similar to todays email. To facilitate this communication, the airlines in partnership with their ACARS vendor defined MCDU screens that could be presented to the flight crew and enable them to perform specific functions. This feature provides the flight crew flexibility as to the types of information requested from the ground and the types of reports sent to the ground. As an example, the flight crew could pull up an MCDU screen that allowed them to send to the ground a request for various types of weather information. After the desired locations and type of weather information were entered, ACARS transmitted this information to the ground. In response to this request message, ground computers sent the requested weather information back to the ACARS MU, which was then displayed and/or printed. Airlines began adding new messages to support new applications (weather, winds, clearances, connecting flights, etc.) and ACARS systems were customized to support airline-unique applications, and unique ground computer requirements. This resulted in each airline having its own unique ACARS application operating on its aircraft. Some airlines have more than 75 MCDU screens for their flight crews, where other may have only a dozen different screens. In addition, since each airlines ground computers were different,
open in browser PRO version
Are you a developer? Try out the HTML to PDF API

pdfcrowd.com

the contents and formats of the messages sent by an ACARS MU were different for each airline. In the wake of the crash of Air France Flight 447, there has been discussion about making ACARS an "online-black-box."[4] If such a system were in place, it would avoid the loss of data due to: (1) black-box destruction, and (2) inability to locate the black-box following loss of the aircraft. However the cost, due to the high bandwidth requirements, would be excessive and there have been very few incidents where the black boxes were not recoverable.

How it works

[edit]

A person or a system on board may create a message and send it via ACARS to a system or user on the ground, and vice versa. Messages may be sent either automatically or manually.

VHF subnetwork

[edit]

A network of VHF ground radio stations ensure that aircraft can communicate with ground end systems in real-time from practically anywhere in the world. VHF communication is line-of-sight, and provides communication with ground-based transceivers (often referred to as Remote Ground Stations or RGSs). The typical range is dependent on altitude, with a 200-mile transmission range common at high altitudes. Thus VHF communication is only applicable over landmasses which have a VHF ground network installed. A typical ACARS VHF transmission. Mode A Aircraft B-18722 Ack NAK
Sample ACARS VHF transmission Sorry, your brow ser either has JavaScript disabled or does not have any supported player. You can dow nload the clip or dow nload a player to play the clip in your brow ser. The sound of an ACARS VHF transmission made on 130.025 MHz, recorded at Petaluma, California on 15 August 2006
Problems listening to this file? See media help.

Block id 2 Flight Label CI5118 B9

Msg No. L05A

open in browser PRO version
Are you a developer? Try out the HTML to PDF API

pdfcrowd.com

Message /KLAX.TI2/024KLAXA91A1

SATCOM and HF subnetworks

[edit]

SATCOM can provide worldwide coverage. Depending on the satellite system in use, coverage may be limited or absent at high latitudes (such as needed for flights over the poles). HF datalink is a relatively new network whose installation began in 1995 and was completed in 2001. Aircraft with HF or global SATCOM datalink can fly polar routes and maintain communication with ground based systems (ATC centers and airline operation centers). ARINC is the only service provider for HF datalink.

Datalink message types

ACARS messages may be of three types: Air Traffic Control (ATC) Aeronautical Operational Control (AOC) Airline Administrative Control (AAC)

[edit]

ATC messages are used to communicate between the aircraft and Air Traffic Control. These messages are defined in ARINC Standard 623 . ATC messages are used by aircraft crew to request clearances, and by ground controllers to provide those clearances. AOC and AAC messages are used to communicate between the aircraft and its base. These messages are either standardized according to ARINC Standard 633 or defined by the users, but in the latter case they must meet at least the guidelines of ARINC Standard 618 . Various types of messages are possible, for example, relating to fuel consumption, engine performance data, aircraft position, in addition to free text .

Example transmissions
Departure delay downlink

[edit] [edit]

A pilot wants to inform his flight operations department that departure has been delayed by Air Traffic Control. The pilot loads a CMU MCDU screen that allows him to enter the expected length of and reason for the delay. After entering the information on the MCDU, he depresses a SEND key on the MCDU. The
open in browser PRO version
Are you a developer? Try out the HTML to PDF API

pdfcrowd.com

CMU detects that the SEND key was pushed, and then generates a digital message containing the delay information. This message may include such information as aircraft registration number, the origination and destination airport codes, the current Estimated Time of Arrival (ETA) before the delay and the current expected duration of the delay. The CMU then sends the message to an existing radio (HF, SATCOM or VHF, with the selection of the radio based on special logic contained within the CMU). For a message to be sent over the VHF network, the radio transmits the VHF signals containing the delay message, which is then received by a VHF Remote Ground Station (RGS). Most ACARS messages are only 100 to 200 characters in length. Such messages are made up of a oneblock transmission from (or to) the aircraft. One ACARS block is constrained to be no more than 220 characters within the body of the message. For downlink messages which are longer than 220 characters, the ACARS unit splits the message into multiple blocks, transmitting each block to the RGS (there is a constraint that no message may be made up of more than 16 blocks). The RGS collects each block of such multi-block messages until the complete message is received before processing and routing the message. ACARS also contains protocols to support a retry of failed messages or retransmission of messages whenever the service provider changes. Once the RGS receives the complete message, the RGS forwards the message to the datalink service provider's (DSP) main computer system. The DSP ground network uses landlines to link the RGS to the DSP. The DSP uses information contained in their routing table to forward the message to the airlines or other destinations. This table is maintained by the DSP and identifies each aircraft (by tail number) and the types of messages that it can process. (Each airline must tell its service provider(s) what messages and message labels their ACARS systems will send, and, for each message, where they want the service provider to route the message. The service provider then updates their routing tables from this information.) Each type of message sent by the CMU has a specific message label, which is contained in the header information of the message. Using the label contained in the message, the DSP looks up the message in the table and forwards it to the airlines computer system. which then processes message. This processing performed by an airline may include reformatting the message, populating databases for later analysis, or forwarding the message to other departments, such as flight operations, maintenance, engineering, finance, or other organizations within an airline. In the example of a delay message, it may be routed via the airlines network to both their operations department as well as to a facility at the aircrafts
open in browser PRO version
Are you a developer? Try out the HTML to PDF API

pdfcrowd.com

destination, notifying them of a potential late arrival. The elapsed transmission time from the moment the flight crew presses the send key to the moment it is processed by an airlines computer system varies, but is generally on the order of 6 to 15 seconds. The messages that are sent to the ground from the CMU are referred to as downlink messages.

Weather report uplink

[edit]

For a message to be transmitted to the aircraft (referred to as an uplink message), the process is nearly a mirror image of how a downlink is sent from the aircraft. For example, in response to an ACARS downlink message requesting weather information, a weather report is constructed by the airlines computer system. The message contains the aircraft registration number in the header of the message, with the body of the message containing the actual weather information. This message is sent to the DSP's main computer system. The DSP transmits the message over their ground network to a VHF remote ground station in the vicinity of the aircraft. The remote ground station broadcasts the message over the VHF. The on-board VHF radio receives the VHF signal and passes the message to the CMU (with the internal modem transforming the signal into a digital message). The CMU validates the aircraft registration number, and processes the message. The processing performed on the uplink message by the CMU depends on the specific airline requirements. In general, an uplink is either forwarded to another avionics computer, such as an FMS or FDAMS, or is processed by the CMU. For messages destined for the CMU (such as a weather report uplink), the flight crew refers to a specific MCDU screen which contains a list of all received uplink messages. The flight crew then selects the weather message for viewing on the MCDU. The ACARS unit may also print the message on the cockpit printer (either automatically upon receiving the message or in response to the flight crew's pressing a PRINT prompt on the MCDU screen).

FDAMS message downlink

[edit]

Messages are sent to the ground from other on-board systems in a manner similar to the delay message example discussed above. As an example, an FDAMS system may have a series of active algorithms
open in browser PRO version
Are you a developer? Try out the HTML to PDF API

pdfcrowd.com

monitoring engine exceedance conditions during flight (such as checking whether engine vibration or oil temperature exceeds normal operating conditions). Upon detecting such an event, the FDAMS system automatically creates an engine exceedance condition message, with applicable data contained within the body of the message. The message is forwarded to the CMU, using what is referred to as ARINC 619 data protocols. The CMU then transmits the message to the ground. In this case, the service provider's routing table for an engine exceedance message is typically defined to have the message routed directly to an airlines maintenance department. This enables airline maintenance personnel to be notified of a potential problem in real time. There are three major components to the ACARS datalink system: Aircraft equipment Service provider Ground processing system

Aircraft equipment
The heart of the datalink system on board the aircraft is the ACARS Management Unit (MU). The older version of MU is defined in ARINC Characteristic 724B . Newer versions are referred to as the Communications Management Unit (CMU) and are defined in ARINC Characteristic 758 .

[edit]

Aircraft equipment consists of airborne end systems and a router. End systems are the source of ACARS downlinks and the destination for uplinks. The MU/CMU is the router. Its function is to route a downlink by means of the most efficient air-ground subnetwork. In many cases, the MU/CMU also acts as an end system for AOC messages. Typical airborne end systems are the Flight Management System (FMS), datalink printer, maintenance computer, and cabin terminal. Typical datalink functions are: FMS - sends flight plan change requests, position reports, etc. Receives clearances and controller instructions. Printer - as an end system, can be addressed from the ground to automatically print an uplink message. Maintenance computer - downlinks diagnostic messages. In advanced systems, in-flight troubleshooting can be conducted by technicians on the ground by using datalink messages to command diagnostic
open in browser PRO version
Are you a developer? Try out the HTML to PDF API

pdfcrowd.com

routines in the maintenance computer and analyzing downlinked results. Cabin terminal - Often used by flight attendants to communicate special passenger needs, gate changes due to delays, catering, etc. ACARS messages are transmitted over one of three air-ground subnetworks. VHF is the most commonly used and least expensive. Transmission is line-of-sight so VHF is not available over the oceans or other vast expansions of uninhabited surface, such as the Amazon Basin. SATCOM is a fairly expensive service that provides (near) worldwide coverage. The Inmarsat satellite network does not cover the polar regions. The Iridium satellite network became usable for ACARS transport in 2007 and provides excellent coverage in the polar regions. HF is a more recently established subnetwork. Its purpose is to provide coverage in the polar regions where Inmarsat coverage is unreliable. The router function built into the MU/CMU determines which subnetwork to use when routing a message from the aircraft to the ground. The airline operator provides a routing table that the CMU uses to select the best subnetwork.

Datalink service provider

[edit]

The role of the datalink service provider (DSP) is to deliver a message from the aircraft to the ground end system, and vice versa. Because the ACARS network is modeled after the point-to-point telex network, all messages come to a central processing location. The DSP routes the message to the appropriate end system using its network of land lines and ground stations. Before the days of computers, messages came to the central processing location and were punched on paper tape. The tape was then physically carried to the machine connected to the intended destination. Today, the routing function is done by computer, but the model remains the same. There are currently two primary service providers of ground networks in the world (ARINC and SITA), although specific countries have implemented their own network, with the help of either ARINC or SITA. ARINC operates a worldwide network and has also assisted the Civil Aviation Administration of China
open in browser PRO version
Are you a developer? Try out the HTML to PDF API

pdfcrowd.com

(CAAC), as well as Thailand and South America with the installation of VHF networks. SITA has operated the network in Europe, Middle East, South America and Asia for many years. They have also recently started a network in the USA to compete with ARINC. Until recently, each area of the world was supported by a single service provider. This is changing, and both ARINC and SITA are competing and installing networks that cover the same regions.

Ground end system

[edit]

The ground end system is the destination for downlinks and the source of uplinks. Generally, ground end systems are either government agencies such as CAA/FAA, an airline operations headquarters, or, in the case of small airlines or general aviation consumers, a subscription based solution. CAA end systems provide air traffic services such as clearances. Airline and general aviation operations provide information necessary for operating the airline or flight department efficiently, such as gate assignments, maintenance, and passenger needs. In the early history of ACARS most airlines created their own host systems for managing their ACARS messages. Commercial off-the-shelf products are now widely available to manage the ground hosting.

ARINC specifications

[edit]

Much of the processing performed by the CMU as well as basic requirements of the hardware are defined by ARINC specifications . The following is a list of the major ARINC specifications that define standards that govern many aspects of ACARS systems: ARINC documents and their specifications ARINC Design Guidance for Avionics Equipment. Includes definition of the Aircraft Personality Module 607 (APM) required for ARINC 758 CMU installation. Specification for receiving and broadcasting ARINC 429 broadcast data (data transfer between ARINC avionics LRUs). ARINC 429 is the one-way communication data bus (one pair of data bus use for 429 transmit data and another pair of data bus use for receive data). Defines the air/ground protocols for communicating between the ACARS/CMU and VHF ground
open in browser PRO version
Are you a developer? Try out the HTML to PDF API

pdfcrowd.com

ARINC systems. Also defines the format of the ACARS messages sent by the ACARS/CMU as well as 618 received by the ACARS CMU. The format of this message is called a Type A message. This characteristic has been updated to define the future VDL Mode 2 AOA operation. Defines the protocols for the ACARS/CMU to use to transfer file data between other avionics in the ARINC aircraft. ARINC 619 covers file protocols that are used to interface with FMS, FDAMS, the cabin 619 terminal, maintenance computers, SATCOM systems and HF voice data radios. Defines ground-to-ground communication protocols. This includes the format of messages routed ARINC between a service provider and an airline or other ground system. This is referred to as a Type B 620 message (the air/ground Type A message is reformatted to a Type B message for ground transmissions). ARINC Describes the processing associated with sending ATC application messages over todays 622 ACARS links (including ARINC 623 ATC messages). This characteristic identifies ATC related messages that can be generated or received by an ARINC ACARS MU/CMU system (does not include FANS-1 or FANS-A messages that are processed by 623 the FMS). Specification for a bi-directional data bus for sending and receiving data between multiple avionics ARINC LRUs. The specification was initially developed for use on Boeing 777 commercial airplanes, but 629 was published as an ARINC industry standard in 1999. Specification for VHF Data Link (VDL) Mode 2. This specification provides general and specific ARINC design guidance for the development and installation of the protocols needed to exchange bit631 oriented data across an air-ground VHF Digital Link (VDL) in an Open System Interconnection (OSI) environment. ARINC Specification for an ACARS MU for ARINC 724B wiring. 724B ARINC Specification for interfacing with Multi-purpose cockpit display units. 739 ARINC
open in browser PRO version
Are you a developer? Try out the HTML to PDF API

pdfcrowd.com

740 ARINC 744

Specification for interfacing to cockpit printers.

Specification for a CMU relative to ARINC 758 wiring. This specification identifies various levels of ARINC functionality, these in turn defining future growth phases for the CMU. Initial CMU systems which 758 perform todays ACARS functions are classified as Level OA. Two-part specification that defines a security framework for protecting ACARS datalink messages exchanged between aircraft and ground systems. Security services include confidentiality, data ARINC integrity, and message authentication. Part 1, ACARS Message Security (AMS), specifies the 823 security protocol, and Part 2, Key Management, specifies life-cycle management of the cryptographic keys necessary for secure and proper operation of AMS.

Acronyms and glossary

[edit]

It has been rumored that the introduction of datalink into the airline industry originated as part of a contest to see how many acronyms could be developed around a specific technology. Whether this is true or not, the industry is at the point where acronyms are now nested within acronyms. For example, AOA is an acronym for ACARS Over AVLC, where AVLC itself is an acronym for Aviation VHF Link Control and VHF is also an acronym for Very High Frequency. ACARS Aircraft Communications Addressing and Reporting System ACMS Aircraft Condition Monitoring System AMS ACARS Message Security, as specified in ARINC 823 AOA ACARS Over AVLC. With the introduction of VDL Mode 2, the ACARS protocols were modified to take advantage of the higher data rate made possible by Mode 2. AOA is an interim step in replacing the
open in browser PRO version
Are you a developer? Try out the HTML to PDF API

pdfcrowd.com

ACARS protocols with ATN protocols. ATN Aeronautical Telecommunications Network. As air traffic increases, ACARS will no longer have the capacity or flexibility to handle the large number of datalink communications. ATN is planned to replace ACARS in the future and will provide services such as authentication, security, and a true internetworking architecture. Europe is leading the US in the implementation of ATN. AVLC Aviation VHF Link Control. A particular protocol used for aeronautical datalink communications CDU Control Display Unit CMF Communications Management Function. The software that runs in a CMU, and sometimes as a software partition in an integrated avionics computer. CMU Communications Management Unit. Successor to the MU, the CMU performs similar datalink routing functions, but has additional capacity to support more functions. CMU standards are defined in ARINC Characteristic 758. FDAMS Flight Data Acquisition and Management System FMS Flight Management System. FMS standards are defined in ARINC Characteristic 702 and 702A. HFDL High Frequency Data Link is an ACARS communications media used to exchange data such as Airline Operational Control (AOC) messages, Controller Pilot Data Link Communication (CPDLC) messages and Automatic Dependent Surveillance (ADS) messages between aircraft end-systems and corresponding ground-based HFDL ground stations. HF High Frequency. A portion of the RF spectrum. LRU
open in browser PRO version
Are you a developer? Try out the HTML to PDF API

pdfcrowd.com

Line Replaceable Unit. An avionics "black box" that can be replaced on the flight line, without downing the aircraft for maintenance. MCDU Multifunction Control Display Unit. A text-only device that displays messages to the aircrew and accepts crew input on an integrated keyboard. MCDU standards are defined in ARINC Characteristic 739. MCDUs have seven input ports and can be used with seven different systems, such as CMU or FMS. Each system connected to an MCDU generates its own display pages and accepts keyboard input, when it is selected as the system controlling the MCDU. MIDU Multi-Input Interactive Display Unit (often used as a third cockpit CDU). MU Management Unit. Often referred to as the ACARS MU, this is an avionics LRU that routes datalink messages to and from the ground. OOOI Shorthand for the basic flight phasesOut of the gate, Off the ground, On the ground, In the gate. POA Plain Old ACARS. Refers to the set of ACARS communications protocols in effect before the introduction of VDL Mode 2. The term is derived from POTS (Plain old telephone service) that refers to the wired analog telephone network. SATCOM Satellite Communications. Airborne SATCOM equipment includes a satellite data unit, medium to high power amplifier, and an antenna, possibly with a steerable beam. A typical SATCOM installation can support a datalink channel as well as one or more voice channels. VDL VHF Data Link VHF Very High Frequency. A portion of the RF spectrum, defined as 30 MHz to 300 MHz.

GIS and data discovery

open in browser PRO version
Are you a developer? Try out the HTML to PDF API

[edit]
pdfcrowd.com

In 2002, ACARS was added to the NOAA Observing System Architecture. NOSA provides near real time WMS maps and an ID search from the NOSA homepage.

See also
Acronyms and abbreviations in avionics SELCAL

[edit]

References

[edit]

1. ^ Carlsson, Barbara (October 2002), "GLOBALink/VHF: The Future Is Now" , The Global Link: 4, retrieved 2007-01-24 2. ^ http://www.arinc.com/downloads/product_collateral/acars_first_datasheet.pdf 3. ^ http://aspmhelp.faa.gov/index.php/OOOI_Data 4. ^ Online-Black-Box soll Crashs schneller aufklren on: June 6, 2009. . (Germ an) Spiegel-Online. June 6, 2009. Accessed

External links
ARINC , inventors of ACARS acarsd , free ACARS decoder software for Linux/Windows ACARS on NOSA ARINC Standards Document List
V T E V T E V T E

[edit]

, list and describe the ARINC standards

[show ] [show ] [show ]

Earth-based meteorological equipment and instrumentation Earth-based meteorological observation systems and weather stations Telecommunications

Categories: 1978 introductions Aircraft instruments Meteorological data and networks

open in browser PRO version
Are you a developer? Try out the HTML to PDF API

Aviation communications

Avionics

pdfcrowd.com

This page w as last modified on 14 March 2013 at 11:39. Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization. Contact us Privacy policy About Wikipedia Disclaimers Mobile view

open in browser PRO version

Are you a developer? Try out the HTML to PDF API

pdfcrowd.com