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 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.

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.

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.

ARINC 653, Part 3B is the Compliance Test Specification for ARINC 653 Extended Services presently defined in ARINC 653 Part 2. 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 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.

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.

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.

ARINC Specification 485, Part 2 specifies the ARINC 485-control protocol used by the LRUs described in ARINC Specification 628 Part 2. This document defines a multi-drop bus. The point-to-point configuration is also supported. The point-to-point bus is treated simply as a multi-drop bus with only one drop. There is one master LRU and one or more slave LRUs present on the bus. However; multiple buses may be connected in parallel, where each parallel bus operates independently from each other.

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 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 is a top-level guidance standard intended for the design of Automatic Test Equipment (ATE). It includes the definition of hardware and software needed for analog and digital signal testing using a Test Unit Adapter common interface. This standard describes the overall ATE system concept as well as the definition of the specific elements of those systems.

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 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.

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 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.