ARINC SPECIFICATION 622-5-2017 PDF

St ARINC SPECIFICATION 622-5-2017

Name in English:
St ARINC SPECIFICATION 622-5-2017

Name in Russian:
Ст ARINC SPECIFICATION 622-5-2017

Description in English:

Original standard ARINC SPECIFICATION 622-5-2017 in PDF full version. Additional info + preview on request

Description in Russian:
Оригинальный стандарт ARINC SPECIFICATION 622-5-2017 в PDF полная версия. Дополнительная инфо + превью по запросу
Document status:
Active

Format:
Electronic (PDF)

Delivery time (for English version):
1 business day

Delivery time (for Russian version):
250 business days

SKU:
Starinc216

Choose Document Language:
€35

Full title and description

ARINC Specification 622-5:2017 — "ATS Data Link Applications Over ACARS Air‑Ground Network". This specification defines Air Traffic Services (ATS) data‑link application processes, message formats and procedures intended to enable interoperable ATS services using the ACARS air–ground network. It provides design guidance to implementers of ATS applications so multiple ground agencies and aircraft operators can interwork reliably over ACARS.

Abstract

The document describes ATS data link processes over ACARS, the ACARS‑compatible system model, ATS Facilities Notification (AFN) procedures and message formats, support for both bit‑oriented and character‑oriented ATS applications, and related context, timers, reason codes and diagnostics. It includes attachments and appendices with message definitions, examples and implementation guidance to ensure worldwide interoperability.

General information

  • Status: Current / Active.
  • Publication date: 23 August 2017.
  • Publisher: Aeronautical Radio, Inc. (ARINC).
  • ICS / categories: Aviation / aeronautical communications and air traffic services; avionics communications and data‑link systems.
  • Edition / version: ARINC 622-5:2017 (2017 edition).
  • Number of pages: 132 pages.

Scope

This specification defines processes and message structures that extend the ACARS system to support ATS functions. It covers the ACARS compatible system model, AFN procedures and state machine, support for bit‑oriented (binary) and character‑oriented applications, address verification, context management, ADS and ATCComm provisions, message envelopes for character applications and a set of specific ATS message types (for example ATIS, oceanic/departure clearances, TWIP, DDTC and Controller‑to‑Pilot Communication). The intent is to provide implementers with uniform formats and procedures so ANSPs, regulators and aircraft operators can interoperate worldwide.

Key topics and requirements

  • Definition of ATS data link processes over the ACARS air–ground network.
  • ACARS compatible system model and required system components.
  • ATS Facilities Notification (AFN) procedures, timers, reason codes and AFN message formats.
  • Support and interfaces for bit‑oriented (binary) ATS applications, including ADS and ATCComm provisions.
  • Support for character‑oriented applications: message envelope, ATIS, oceanic/departure clearance, TWIP, DDTC, CPC and related formats.
  • Context management (CMA), address verification and interworking rules for multi‑agency ATS messaging.
  • Attachments and appendices with IMI/MFI/label definitions, SDL representations, CRC examples and worked AFN examples for implementers.

Typical use and users

Primary users are avionics manufacturers, aircraft systems integrators, airlines and operators implementing ATS data link functionality, air navigation service providers (ANSPs) and ground systems developers, certification and test laboratories, and regulators specifying data‑link procedures. The specification is used as a design and interoperability reference when developing ACARS‑based ATS services and validating message exchange between aircraft and ground ATS systems.

Related standards

Relevant related documents include other ARINC specifications and ACARS/avionics protocol standards such as ARINC 619 (ACARS protocols for avionic end systems) and associated ARINC characteristics referenced for ACARS management, as well as regional and procedural ATM/Eurocontrol guidance where ATS data‑link procedures are harmonized. Implementers should consult ARINC 619‑series material and the ACARS characteristic documents referenced in ARINC 622 for protocol-level dependencies.

Keywords

ARINC 622-5, ACARS, ATS data link, AFN, ACARS compatible system, CMA (context management), ADS, ATCComm, ATIS, TWIP, DDTC, Controller‑to‑Pilot Communication, interoperability, air‑ground network.

FAQ

Q: What is this standard?

A: ARINC 622‑5:2017 is an ARINC specification that defines Air Traffic Services (ATS) data‑link application processes, message formats and procedures for operation over the ACARS air–ground network to ensure interoperable ATS services.

Q: What does it cover?

A: It covers ACARS‑compatible system definitions, ATS Facilities Notification (AFN) procedures and message formats, provisions for bit‑oriented and character‑oriented ATS applications (examples: ATIS, oceanic and departure clearances, TWIP, DDTC, CPC), context management, address verification, timers/reason codes and implementation attachments and appendices.

Q: Who typically uses it?

A: Avionics manufacturers, airlines and operators, ground system developers and ANSPs, systems integrators, certification/test labs and regulators that implement or validate ATS data‑link services over ACARS.

Q: Is it current or superseded?

A: The 2017 edition is the published ARINC 622‑5 release (August 2017) and is listed as the current/active edition in ARINC/standards catalogues. Users should check with ARINC/Aviation authorities for any amendments or later revisions before implementation.

Q: Is it part of a series?

A: Yes — ARINC 622 is part of the ARINC suite of avionics and communications specifications addressing ACARS and related avionics interfaces; it cross‑references other ARINC characteristics and ACARS protocol specifications used for end systems and network management.

Q: What are the key keywords?

A: ACARS, ATS data link, AFN, CMA, ATCComm, ADS, ATIS, DDTC, TWIP, Controller‑to‑Pilot Communication, interoperability, air‑ground network.