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 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 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.
ARINC 800 is the first industry standard intended for characterization of aviation-grade high-speed (Gbps) Ethernet links. The test methods are based on realistic representation of cabin networks. The notional cabling architecture is based on IFE seat distribution using multiple intermediate disconnects. Sequential testing is supported by building up number of connectors in the link. Test guidelines for mixed intermediate cable lengths are provided.
This document defines general practices for testing the physical layer of a fiber optic cable system. It is the intention of this document to outline proven practices for engineers and technicians engaged in testing and supporting fiber optic cable systems in aircraft. This document defines general practices for testing the physical layer of a fiber optic cable system. It is the intention of this document to outline proven practices for engineers and technicians engaged in testing and supporting fiber optic cable systems in aircraft.
ARINC 653, Part 3A is the Compliance Test Specification for ARINC 653 Required Services presently defined in ARINC 653 Part 1. The document specifies a set of stimuli and the expected responses. Future work on the ARINC 653 document set includes an effort to define Operating System services for multi-core processor environments. The Compliance Test Specification is expected to be updated in step with ARINC 653, Part 1.
This report defines the requirements and recommended practices for production testing of aircraft passenger seats and seat groups. Production testing is performed at the seat manufacturers' facilities prior to the shipment of the seats to the airframe manufacturers, Maintenance, Repair, and Overhaul (MRO), or airlines/operators for installation in the aircraft. Using this guidance, rework is minimized and schedules remain minimally affected.
This document establishes techniques for validating that a mission store complies with the interface requirements contained in MIL-STD-1760 Revision D.
This SAE Aerospace Recommended Practice (ARP) provides guidance to develop and assure validation and verification of IVHM systems used in autonomous aircraft, vehicles and driver assistance functions. IVHM covers a vehicle, monitoring and data processing functions inherent within its sub-systems, and the tools and processes used to manage and restore the vehicle’s health. The scope of this document is to address challenges and identify recommendations for the application of integrated vehicle health management (IVHM) specifically to intelligent systems performing tasks autonomously within the mobility sector. This document will focus on the core aspects of IVHM for autonomous vehicles that are common to both aerospace and automotive applications. It is anticipated that additional documents will be developed separately to cover aspects of this functionality that are unique to each application domain.
This activity is focused on more electric and all electric type power systems for air vehicles. The scope of which includes source, distribution and user contributions to electrical power quality, failure modes, coordination, system reliabilty and robustness, impacts of being flight critical and the gaps which exist in present standards and guidance documents.