Search Results

Standard

TIMELY RECOVERY OF FLIGHT DATA (TRFD)

2021-08-06

CURRENT

ARINC681

The difficulty in locating crash sites has prompted international efforts for alternatives to quickly recover flight data. This document describes the technical requirements and architectural options for the Timely Recovery of Flight Data (TRFD) in commercial aircraft. ICAO and individual Civil Aviation Authorities (CAAs) levy these requirements. The ICAO Standards and Recommended Practices (SARPs) and CAA regulations cover both aircraft-level and on-ground systems. This report also documents additional system-level requirements derived from the evaluation of ICAO, CAA, and relevant industry documents and potential TRFD system architectures. It describes two TRFD architectures in the context of a common architectural framework and identifies requirements. This report also discusses implementation recommendations from an airplane-level perspective.

Standard

STANDARD DATA INTERFACES FOR GALLEY INSERT (GAIN) EQUIPMENT PART 2 CAN COMMUNICATIONS, VERIFICATION, AND SYSTEM TEST GUIDANCE

2014-08-26

CURRENT

ARINC812AP2

The purpose of this specification is to define test procedures to verify the implementation of the Controller Area Network (CAN) interface for Galley Systems, as defined in ARINC Specification 812A, Part 1.

Standard

ROADMAP FOR IPV6 TRANSITION IN AVIATION

2020-06-19

CURRENT

ARINC686

ARINC Report 686 represents the consensus of industry to prepare a roadmap migration from IPv4 to IPv6. This document describes airline objectives (air and ground side when possible) towards the development and introduction of IPv6. There are three distinct elements considered: 1) the applications for addressing aspects 2) the communication network(s) over which the applications are running for the IP protocol level itself and associated features, and 3) the physical link(s) the network(s) interface.

Standard

ONBOARD SECURE WI-FI NETWORK PROFILE STANDARD

2021-06-18

CURRENT

ARINC687

This document defines a standard implementation for strong client authentication and encryption of Wi-Fi-based client connections to onboard Wireless LAN (WLAN) networks. WLAN networks may consist of multi-purpose inflight entertainment system networks operating in the Passenger Information and Entertainment System (PIES) domain, dedicated aircraft cabin wireless networks or localized Aircraft Integrated Data (AID) devices operating in the Aircraft Information Services (AIS) domain. The purpose of this document is to focus on the client devices requiring connections to these networks such as electronic flight bags, flight attendant mobile devices, onboard Internet of Things (IoT) devices, AID devices (acting as clients) and mobile maintenance devices. Passenger devices are not within the focus of this document.

Standard

ONBOARD MOBILE TELEPHONY SYSTEM (OMTS)

2009-05-29

CURRENT

ARINC824

This document provides standards necessary to achieve interchangeability between equipment providers. Attachment 1 specifies an interconnection scheme by which aircraft can be wired to enable full interchangeability between OMTS products from different suppliers. Attachment 1 also specifies a minimum interface configuration which can be viewed as a desirable future implementation on new aircraft because of its potential for significant weight and space savings along with the possibility for less complex integration into the OEM production environment. The OMTS standard includes the physical interfaces, wiring, connectors, space envelopes, equipment chassis, unit co-location requirements, and power requirements. The basic functionality within each component of the OMTS is covered. Detailed functionality, protocols, and design parameters unique to each system supplier are not covered in this document.

Standard

NETWORK SERVER SYSTEM (NSS)

2005-08-31

CURRENT

ARINC763-3

The network server system description includes a common file server, data processing, mass storage and interface capabilities to a number of terminals connected via an onboard aircraft Local Area Network (LAN). The Network Server System is a central node through which terminals are able to communicate with avionics systems, access data and applications stored in the NSS mass memory storage.

Standard

MEDIA INDEPENDENT SECURE OFFBOARD NETWORK

2020-06-19

CURRENT

ARINC848

ARINC Specification 848 is a functional standard based on a protocol specification profile for a secured network interface. The purpose is to define a common method of initiating a mutually authenticated tunnel between an aircraft service and its Enterprise service. ARINC Specification 848 defines a standard implementation for securing the communications between an onboard Local Area Network (LAN) and an Enterprise LAN on the ground. Various aircraft network architectures and various air to ground communication channels (aka media) are accommodated in this document. For example, L-band Satellite Communication (Satcom), Ku/Ka-band Satcom, Gatelink Cellular, and Gatelink are considered.

Standard

MARK 2 NETWORK SERVER SYSTEM (NSS) FORM AND FIT DEFINITION

2008-12-09

CURRENT

ARINC763A

This document defines both wired and wireless NSS components that enable the creation of airborne networks that are scalable, interchangeable, upgradeable, and remotely manageable with minimum cost. Aircraft equipment configurations and aircraft wiring recommendations are also described to allow aircraft network growth through the simple addition or replacement of NSS components. Hardware characteristics of standardized components are described without specifying equipment capacity or the operational functions of those components.

Standard

INTERSYSTEM NETWORK INTEGRATION

2021-06-24

CURRENT

ARINC688

The purpose of this document is to provide guidelines for integrating previously standalone cabin systems such as cabin management systems, In-Flight Entertainment (IFE) systems, In-Flight Connectivity (IFC) systems, galley systems, surveillance systems, etc. Resource sharing between systems can reduce airline costs and/or increase functionality. But, as systems expose their internal resources to external systems, the risk of an intrusion that could degrade function and/or negatively expose the supplier’s or airline’s brand increases. This document provides a recommended IP networking design framework between aircraft systems to reduce the operational security threats while still supporting the necessary intersystem routing.

Standard

INTERNET PROTOCOL SUITE (IPS) FOR AERONAUTICAL SAFETY SERVICES PART 1 AIRBORNE IPS SYSTEM TECHNICAL REQUIREMENTS

2021-06-21

CURRENT

ARINC858P1

ARINC 858 Part 1 defines the airborne data communication network infrastructure for aviation safety services using the Internet Protocol Suite (IPS). ARINC 858 builds upon ICAO Doc 9896, Manual on the Aeronautical Telecommunication Network (ATN) using Internet Protocol Suite (IPS) Standards and Protocol. IPS will extend the useful life of data comm services presently used by operators, e.g., VDL, Inmarsat SBB, Iridium NEXT, and others. It represents the evolutionary path from ACARS and ATN/OSI to the end state: ATN/IPS. ARINC 858 includes advanced capabilities such as aviation security and mobility. This product was developed in coordination with ICAO WG-I, RTCA SC-223, and EUROCAE WG-108.

Standard

GUIDANCE FOR SECURITY EVENT LOGGING IN AN IP ENVIRONMENT

2017-06-21

CURRENT

ARINC852

This report sets forth guidance for IP-based onboard networks and systems residing in the Airline Information Services (AIS) and Passenger Information and Entertainment Services (PIES) Domains by establishing a common set of security related data elements and format(s) that are produced by aircraft systems, suitable for use by airline IT and/or avionic supplier analytical ground tools.

Standard

GUIDANCE FOR DISTRIBUTED RADIO ARCHITECTURES

2021-07-15

CURRENT

ARINC678

The purpose of this document is to evaluate Communication, Navigation, and Surveillance (CNS) Distributed Radio architectures and the feasibility of distributing the RF and systems processing sections to ensure the following: Reduce cost of equipment Reduce Size, Weight, and Power (SWaP) Ease of aircraft integration Growth capability built into the design Maintain or improve system availability, reliability, and maintainability It provides a framework to determine whether it is feasible to develop ARINC Standards that support CNS distributed radio architectures.

Standard

ETHERNET SWITCH UNIT (ESU)

2003-12-29

CURRENT

ARINC765

ARINC Characteristic 765 defines an Ethernet Switch Unit (ESU), which fits in the general architectural philosophy and aircraft infrastructure for the proper use and interface of various information network related equipment. This document specifies an ESU intended for various aircraft information network related equipment. It provides a wired network connection among the connected devices based on interfaces defined by ARINC Specification 664 and IEEE 802.3 CSMA/CD (Ethernet).

Standard

EMBEDDED INTERCHANGE FORMAT FOR AIRPORT MAPPING DATABASE

2007-11-19

CURRENT

ARINC816-1

This document defines an open encoding format for airport databases which are loaded in airborne systems. This format, when designed and implemented, will enable a quick, economic, and efficient use of AMDB. However, since industry does not require applications to be standardized, data interpretation is not addressed in this document.

Standard

EMBEDDED INTERCHANGE FORMAT FOR AIRPORT MAPPING DATABASE

2016-08-31

CURRENT

ARINC816-3

This document defines an open encoding format for airport databases which are loaded in airborne systems. This format, when designed and implemented, will enable a quick, economic, and efficient use of AMDB. However, since industry does not require applications to be standardized, data interpretation is not addressed in this document.

Standard

CONSIDERATIONS FOR AVIONICS NETWORK DESIGN

1995-10-09

CURRENT

ARINC428

This standard provides the framework for developing a set of requirements for an avionics data bus network. This standard is intended to provide system-level considerations for the development of such a network, which may include a mix of standard data buses and private data buses.

Standard

COMMUNICATIONS MANAGEMENT UNIT (CMU) MARK 2

2019-11-26

CURRENT

ARINC758-4

This ARINC Standard specifies the ARINC 758 Mark 2 Communications Management Unit (CMU) as an on-board message router capable of managing various datalink networks and services available to the aircraft. Supplement 4 adds Ethernet interfaces, per ARINC Specification 664 Part 2. This will allow the CMU to communicate with IP based radio transceivers (e.g., L-Band Satellite Communication Systems (Inmarsat SwiftBroadband (SBB) and Iridium Certus), ACARS over IP, AeroMACS, etc.).

Standard

CNS/ATM AVIONICS, FUNCTIONAL ALLOCATION AND RECOMMENDED ARCHITECTURES

2001-01-15

CURRENT

ARINC660A

This standard expands ARINC 660 to include industry-defined architectures for the CNS/ATM operating environment. These architectures are intended to meet long-term requirements (e.g., ADS-B, CPDLC, etc.) and provide growth for the future. Airlines support the implementation of these architectures for the long-term. This standard represents broad airline consensus for developing avionics equipment providing CNS/ATM operating capabilities.

Standard

CNS/ATM AVIONICS, FUNCTIONAL ALLOCATION AND RECOMMENDED ARCHITECTURES

1995-12-15

CURRENT

ARINC660

Defines a set of standard aircraft avionics architectures that support a cost-effective evolution to the fully operational CNS/ATM environment. These architectures are intended to meet near-term requirements (e.g., FANS-1, SCAT-1, etc.) and provide growth for supporting the full CNS/ATM function set. This standard represents broad airline consensus for developing avionics equipment providing CNS/ATM operating capabilities.

Standard

CNS/ATM AVIONICS ARCHITECTURES SUPPORTING NEXTGEN/SESAR CONCEPTS

2014-01-10

CURRENT

ARINC660B

This document identifies and describes the aircraft avionics capability necessary for operation in the evolving Communications Navigation Surveillance/Air Traffic Management (CNS/ATM) environment expected for the FAA NextGen program, Single European Sky ATM Research (SESAR) program and considerations of the Japan Collaborative Actions for Renovation of Air Traffic Systems (CARATS). These capabilities are intended to satisfy the industry's long-term CNS/ATM operational objectives.