Search Results

This document defines the characteristics necessary to standardize the airborne recorder download file format in order to facilitate data import, transcription, and exchange. A standardized data format will reduce the variety of readout equipment required for airborne recorder data transcription. This document defines the detailed architecture of the Recorder Standard Output (RSO) file. The architecture is a tagged file structure within which many different files and their formats can be supported. The structure is necessary to support newer recording requirements for flight data, data link, audio, and image recording. This structure is intended for use with all civil recorders and should support use with military recorders.

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.

This specification provides the overview of aircraft data networks installed in air-transport aircraft, tutorial information for adaptation of commercial network standards to air-transport aircraft, and terminology used to describe aircraft data networks. This specification explains the dependency of Aircraft Data Network (ADN) standards on network standards developed by the Internet community, IEEE, and ISO. The classes, Compliant Networks and Profiled Networks, used to characterize aircraft networks are introduced.

This standard provides basic requirements for audible warning generators, whose function is to provide 25 different channels with sound and/or voice warnings, activated by discrete input signals and generated as a function of an unsafe condition of important systems of the aircraft. The outputs are available for audible display to the cockpit crew.

This document provides an overview of the entire set of documents collectively referred to as ARINC 653. As this set of documents evolves, Supplements to Part 0 will be made more consistent with Parts 1 through 5 in conjunction with the technical changes expected to be made in the evolution of ARINC 653. A summary of the ARINC 653 documents follows: Part 0 - Overview of ARINC 653, Part 1 - Required Services, Part 2 - Extended Services, Part 3 - Conformity Test Specification, Part 4 - Subset Services, and Part 5 - Core Software Required Capabilities. Supplement 1 reflects the introduction of multicore processor support in Parts 1 and 2.

This document provides an overview of the entire set of documents collectively referred to as ARINC 653. As this set of documents evolves, Part 0 has been adjusted to reflect technical changes made in Supplements to Parts 1 through 5 in conjunction with the technical changes made in the evolution of ARINC 653. A summary of the ARINC 653 documents follows: Part 0 – Overview of ARINC 653 Part 1 – Required Services Part 2 – Extended Services Part 3A – Conformity Test Specification for ARINC 653 Required Services Part 3B – Conformity Test Specification for ARINC 653 Extended Services Part 4 – Subset Services Part 5 – Core Software Recommended Capabilities The term “this document” refers to Part 0 only, while the term “ARINC 653” or “the Specification” refers to the whole set of ARINC 653 documents, currently Parts 0 to 5.

This document provides an overview of the entire set of documents collectively referred to as ARINC 653. As this set of documents evolves, Supplements to Parts 1 through 5 will be made more consistent with Part 0 in conjunction with the technical changes expected to be made in the evolution of ARINC 653. A summary of the ARINC 653 documents follows: Part 0 - Overview of ARINC 653, Part 1 - Required Services, Part 2 - Extended Services, Part 3 - Conformity Test Specification, Part 4 - Subset Services, and Part 5 - Core Software Required Capabilities. Supplement 1 reflects the introduction of multicore processor support in Parts 1 and 2.

A generic data transfer interface is defined for use between avionics computing equipment that exchanges binary message-oriented data. This interface was developed so that various manufacturers can partition Air Traffic Services (ATS) applications and protocols in different manners between various equipment.

This document is the first of a multi-part specification that will provide a catalog of cabin connector and cables that may be used in ARINC Standard cabin systems, including In-Flight Entertainment. Part 1 describes connector and cable requirements and evaluation criteria for the interface components used in the integration of cabin systems. Future releases will define connectors, contacts, and termination methods in Part 2. Cables will be specified in Part 3.

This standard defines the application text formats for character-oriented ATS messages that can be transmitted over the ACARS data link. Several ACARS data links are available, including but not limited to VHF, HF and satellite. The messages defined herein are not specific to any data link. This standard is limited in scope to character-oriented applications.

This document provides guidance for the development and installation of a Cockpit Voice Recorders (CVR) with solid-state memory. Supplement 6 provides the following: " The optional interfaces to data link services and On-Board Maintenance System (OMS) were revised to clarify that if the optional interface is implemented, then it shall be implemented in a specific way. " The power input section was revised to clarity the need for the CVR to be designed to accept 115 Vac power and 28 Vdc power from the aircraft. " The time correlation requirement was revised to specify that the CVR should receive its time signal from the same source as the Flight Data Recorder (FDR). " The OMS interface was updated to describe the correct ARINC 429 Sign Status Matrix (SSM) encoding for new CVR designs.

This Characteristic provides guidance for the development and installation of a new generation of Cockpit Voice Recorders (CVRs) using solid-state memory. This document supersedes the earlier ARINC Characteristic 557. ARINC Characteristic 757A is intended to coexist with ARINC Characteristic 757 CVR. Supplement 1 provides the following: " The CVR unit description was updated to clarify the differences in the equipment designed to ARINC 757A versus that designed to ARINC 757, i.e., data link and OMS interfaces are required for ARINC 757A compliance. " Material was added to maintain document alignment with ARINC 757 which has FDR capability. ARINC 757A recorders are not required to have FDR capability. " The time correlation requirement was revised to specify that the CVR should receive its time signal from the same source as the Flight Data Recorder (FDR). " The OMS interface was updated to describe the correct ARINC 429 Sign Status Matrix (SSM) encoding for new CVR designs.

This standard includes specific requirements necessary to support flight data recording and other flight data acquisition needs. Design details necessary to ensure interchangeability of equipment in a standard aircraft installation is included.

This document is intended to provide design guidance for the development and installation of an Enhanced Airborne Flight Recorder (EAFR). The EAFR standard addresses combinations of any or all of the following in a single Line Replaceable Unit (LRU), a Digital Flight Data Recorder (DFDR) function, a Cockpit Voice Recorder (CVR) function, a data link recording function, and an image recording function. This document does not address the overall flight data recorder system requirements but considers interface and system standards. This document does not replace ARINC Characteristic 747 which defines DFDRs. This document addresses the details of the voice recording function but does not describe the audio distribution system. It does not replace ARINC Characteristic 757 which defines CVRs. The EAFR may be used in a single or dual-redundant installation as permitted by regulation. Both configurations are addressed in this Characteristic.

This document provides design guidance for the development and installation of a Digital Expandable Flight Data Acquisition and Recording System (DEFDARS) primarily intended for airline use. As such, this guidance will include specific requirements necessary to accommodate mandatory flight data recording and other flight data acquisition needs plus the requirements to ensure customer controlled interchangeability of equipment in a standard aircraft installation. The system capability was expanded to accommodate a data bus speed of 1024 words per second.

This document provides design guidance for the development and installation of Flight Data Recorders (FDR) which may utilize solid state memory and which may employ some means of data compression. The Flight Data Recorder will be utilized with a Flight Data Acquisition Unit (FDAU) (ARINC Characteristic 573) or a Digital Flight Data Acquisition Unit (DFDAU) (ARINC Characteristic 717) to accommodate mandatory flight data recording and other flight data acquisition needs. The document provides guidance and information to ensure customer controlled interchangeability of equipment in a standard aircraft installation and in data retrieval. The system capability was expanded to accommodate a data bus speed of 1024 words per second.

This specification is an international standard defining the content and format of electronic files which document Flight Data Recording systems. The FRED specification is an expansion of the Flight Recorder Configuration Standard (FRCS) and is intended to provide guidelines for software systems designers and developers of ground support equipment for flight data recorders. The FRED specification has been developed to facilitate the exchange of Flight Data Recorder (FDR) documentation between aircraft manufacturers, operators, and government agencies. This specification addresses the ARINC Specification 664: Part 7, Avionics Full Duplex Switched Ethernet in numerous sections.

This standard sets forth the characteristics of a Ground Proximity Warning System (GPWS) designed for installation in commercial aircraft. The GPWS provides audible and visible warnings or alerts when an aircraft approaches terrain or deviates below the ILS glide slope beyond the limits set into the system.

This standard sets forth the characteristics of a GPWS designed for installation in commercial aircraft. It aids pilots by providing audible and visible warnings or alerts when an aircraft approaches terrain more closely than, or deviates downward from an ILS glide slope beyond the limits set into the system.

This document defines a Traffic Surveillance capability for NextGen and SESAR airspace environments. Supplement 2 adds hybrid surveillance functionality. It satisfies recent updates to FAA Airworthiness Circular AC 20-151B - Airworthiness Approval of Traffic Alert and Collision Avoidance Systems (TCAS II), and Technical Standard Order TSO-119d requiring the annunciation of a hybrid surveillance failure. Supplement 2 also adds strobe program pinning, updates TCAS inputs status, improves aircraft troubleshooting, and supports recent central maintenance computer function block point updates.