RTCA DO-258A-2005 PDF

Full title and description

Interoperability Requirements for ATS Applications Using ARINC 622 Data Communications (RTCA DO-258A, April 7, 2005). This document (often referred to as the FANS 1/A Interoperability Standard) defines interoperability requirements and allocations for airborne and ground systems supporting ATS (Air Traffic Services) applications implemented over ARINC 622-style data links, including CPDLC and ADS-C, and aligns FANS 1/A interoperability with related SPR/MOPS work.

Abstract

DO-258A specifies the interoperability requirements necessary for controller–pilot data link communications (CPDLC), automatic dependent surveillance contracts (ADS‑C) and other ATS applications that use ARINC 622 data communications. The revision updates the original DO-258 (2000) to align interoperability requirements with Continental SPR standards (DO‑290) and to include interfaces such as HF data link where applicable. The document allocates requirements across stakeholders (aircraft equipment, ground ATS systems and communications service providers) to ensure end-to-end operational interoperability.

General information

• Status: Active / Most current (DO-258A remains the referenced FANS 1/A interoperability standard).
• Publication date: April 7, 2005 (DO-258A revision).
• Publisher: RTCA, Inc. (with the EUROCAE counterpart ED‑100A commonly cited for the same content).
• ICS / categories: Aviation / aircraft systems and aeronautical communications (commonly classified under ICS aviation/aerospace categories such as 49.020—aircraft and space vehicle engineering).
• Edition / version: Revision A (DO‑258A).
• Number of pages: Approximately 287 pages (published DO-258A page count as listed in standards catalogs).

Scope

DO-258A governs the end-to-end interoperability requirements for ATS data link applications operating over ARINC 622-based message transport (the FANS 1/A family). It covers message formats, procedures, timing/latency considerations, error detection (e.g., CRC usage), logon/session behavior, protocol interactions with HF/VDL/SATCOM where appropriate, and the allocation of responsibilities between airborne equipment, ground ATS systems and communications service providers to achieve reliable CPDLC, ADS‑C and associated ATS services. The revision aligns those interoperability requirements with Continental Safety & Performance Requirements (DO‑290) and other SPR/MOPS as needed.

Key topics and requirements

• Interoperability requirements for CPDLC (message definitions, sequencing, acknowledgements, timing and operational interaction).
• ADS‑C message and reporting profiles including timestamps, reporting modes (periodic, event, waypoint) and transit/latency considerations.
• ARINC 622 message transport and interface allocation (aircraft ↔ ground ↔ communications providers).
• Procedures for logon, address verification, session management and security-relevant operational behaviors.
• Error detection and data integrity measures (e.g., CRC usage and checks to mitigate undetected corruption).
• Alignment with Safety & Performance Requirements (SPR) and other interoperability/production standards (e.g., DO‑290, DO‑306) to ensure consistent system-level performance.

Typical use and users

Primary users are avionics manufacturers, airborne system integrators, ANSP (Air Navigation Service Provider) system designers, certification authorities, airline engineering teams and communications service providers. DO‑258A is used to design, test and certify airborne CPDLC/ADS‑C implementations and to ensure ground system interoperability and operational readiness for FANS 1/A services. It is also used by regulators and operational planners when defining service acceptance, monitoring and approvals.

Related standards

DO‑258A is commonly referenced alongside several RTCA/EUROCAE documents that define related SPR/MOPS and interoperability baselines, including DO‑290/ED‑120 (Continental SPR), DO‑306/ED‑122 (Oceanic SPR), DO‑280B/ED‑110B (ATN Baseline 1 interop), DO‑305A/ED‑154A (FANS/ATN interop) and the EUROCAE counterpart ED‑100A. These documents are used together to cover performance, safety, production and system-level interoperability for air/ground data link services.

Keywords

DO-258A, ED-100A, FANS 1/A, ARINC 622, CPDLC, ADS-C, data link, interoperability, ATS applications, HF Data Link, SATCOM, VDL, SPR, MOPS.

FAQ

Q: What is this standard?

A: DO-258A is RTCA’s Interoperability Requirements standard for ATS applications implemented over ARINC 622 data communications (the FANS 1/A interoperability standard, Revision A published April 7, 2005).

Q: What does it cover?

A: It covers interoperability requirements for CPDLC, ADS‑C and related ATS messaging transported over ARINC 622 — covering message formats, procedures, timing/latency, session/logon behavior, data integrity measures and the allocation of responsibilities among airborne, ground and communications providers to achieve interoperable ATS services.

Q: Who typically uses it?

A: Avionics manufacturers, aircraft integrators, ANSP/ground system engineers, airlines, certification authorities and communications service providers use DO‑258A for design, interoperability testing, system procurement and certification planning.

Q: Is it current or superseded?

A: DO‑258A (Revision A, 2005) is the current FANS 1/A interoperability reference (commonly referenced with EUROCAE ED‑100A). It remains the baseline interoperability document for ARINC 622‑based FANS 1/A CPDLC/ADS‑C implementations; other SPR/MOPS (for example DO‑290 or DO‑306) address complementary performance and safety requirements. Users should confirm whether any program- or region-specific supplements or later amendments apply for a particular project.

Q: Is it part of a series?

A: Yes — DO‑258A is part of the family of RTCA/EUROCAE documents covering ATS data link, interoperability and SPR/MOPS. Relevant companion standards include DO‑290, DO‑306, DO‑280B and the EUROCAE equivalents (ED‑120, ED‑122, ED‑110B, ED‑100A, etc.). These are frequently used together for system design, certification and operational approval.

Q: What are the key keywords?

A: FANS 1/A, ARINC 622, CPDLC, ADS‑C, interoperability, ATS data link, ED‑100A, RTCA DO‑258A.