This SAE Standard provides performance and general design requirements and related test procedures for a combination tail and floodlamp for use on industrial wheeled equipment that may be operated on public roads.
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.).
This specification describes the general connectors, contacts, and backshells in their shape and characteristic for cabin systems for commercial aircrafts. ARINC 600, ARINC 404, and ARINC 801 connector specifications are published as independent standards.
This specification describes the general connectors, contacts, and backshells in their shape and characteristic for cabin systems for commercial aircrafts. ARINC 600, ARINC 404, and ARINC 801 connector specifications are published as independent standards.
The purpose of this standard is to provide a method for packaging aircraft software parts for distribution using contemporary media or by electronic distribution. This project intends to standardize and provide guidance for the storage of floppy based software, currently packaged in media set parts. This standard format can be then stored or distributed on a single physical media member (CD-ROM), or by electronic crate. The obsolescence of floppy disks drive an urgent need for this guidance.
This document specifies how application to application navigation is managed on tablet EFB devices. Topics include: inter-application navigation for users, blending of multiple applications into a single workflow, single data entry with data shared across applications.
This standard defines a common configuration report format that can be retrieved from an aircraft for use by ground tools and maintenance personnel. Reports will be generated in Extensible Markup Language (XML) format and structured as defined by this document. Several optional elements and attributes are defined to allow flexibility for a given report. This standard provides aircraft manufacturers, regulatory agencies, and airlines a format standard for aircraft configuration reporting, and facilitates automated comparison of configuration data reports (e.g., authorized versus as flying, etc.).
This document defines an Aircraft Data Interface Function (ADIF) developed for aircraft installations that incorporate network components based on commercially available technologies. This document defines a set of protocols and services for the exchange of aircraft avionics data across aircraft networks. A common set of services that may be used to access specific avionics parameters are described. The ADIF may be implemented as a generic network service, or it may be implemented as a dedicated service within an ARINC 759 Aircraft Interface Devices (AID) such as those used with an Electronic Flight Bag (EFB). Supplement 8 includes improvements in the Aviation Data Broadcast Protocol (ADBP), adds support for the Media Independent Aircraft Messaging (MIAM) protocol, and contains data security enhancements. It also includes notification and deprecation of the Generic Aircraft Parameter Service (GAPS) protocol that will be deleted in a future supplement.
The purpose of this document is to provide an overview of data networking standards recommended for use in commercial aircraft installations. These standards provide a means to adapt commercially defined networking standards to an aircraft environment. It refers to devices such as bridges, switches, routers and hubs and their use in an aircraft environment. This equipment, when installed in a network topology, can optimize data transfer and overall avionics performance.
The purpose of this document is to establish guidelines that should be observed during initial design, production, and maintenance of aircraft components, and to present short-term and long-term strategies to minimize the costs and impacts associated with decreasing availability of components.
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.
This document describes the technical requirements, architectural options, and recommended interface standards to support an Autonomous Distress Tracking (ADT) System intended to meet global regulatory requirements for locating aircraft in distress situations and after an accident. This document is prepared in response to International Civil Aviation Organization (ICAO) and individual Civil Aviation Authorities (CAAs) initiatives.
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.
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.
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.