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 661 defines logical interfaces to Cockpit Display Systems (CDS) used in all types of aircraft installations. The CDS provides graphical and interactive services to user applications within the flight deck environment. When combined with data from user applications, it displays graphical images to the flight deck crew. The document emphasizes the need for independence between aircraft systems and the CDS. This document defines the interface between the avionics equipment and display system graphics generators. This document does not specify the "look and feel" of any graphical information, and as such does not address human factors issues. These are defined by the airline flight operations community. Supplement 7 adds the definition of: Selector Widget, Tree Widget, New FormatString options, Readouts available in MapItems, Provisions for Touch Screen Displays.
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.
This AIR addresses the use of Software tools to supplement or automate human activities in the development of systems, but not the hardware or software items within those systems. If a systems development tool is also used in the scope of hardware or software item development, for that usage it would then become subject to the guidance presented in DO-254 and DO-178B/C, respectively.
This document describes operational scenarios and examples of system operation based on the experience of different developers of airborne wake vortex safety systems. This information is intended to supplement the recommendations and guidance given in ARP 6267 “Airborne Wake Vortex Safety Systems” as well as facilitate the application of other wake vortex standards and guidance documents generated by SAE and RTCA.
AS 6413 and slash sheets /1 & /2 hold the main information for testing of battery packaging. This document holds further information and expansion of philosophy, clarification etc. surrounding the testing and industry needs.
This AIR will provide a basic understanding of STPA and how it can be applied to development and safety assessment of civil aircraft. It will explain, by way of an example, the information needed to begin STPA, the expected STPA outputs, and the phases of aircraft development and safety assessment that can be supported by STPA.
Clarify the role of the human considerations in Functional Hazard Assessments by identifying the sufficient input information regarding those considerations from the development process, how failure conditions may use that information, and what information the safety assessment process provides to other processes, particularly Human Factors, to assure those aspects of failure conditions are valid.
This AIR would examine the applicability of ARP 4754 and ARP 4761 to UAS and would identify the shortcomings in both recommended practices with regards to the specific technical aspects needed for UAS development.