Search Results

This Characteristic provides the definitions for the physical form and fit dimensions, the electrical interfaces, and the functions of an independent power supply for cockpit voice recorders or crash survivable recorders that combine voice with other recording functions. The RIPS is used to provide backup power that is independent of the aircraft generated power buses.

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. ...This structure is intended for use with all civil recorders and should support use with military recorders....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 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 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. ...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 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 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 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. ...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 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. ...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.

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 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 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 standard provides design guidance for development and installation of a QAR, whose basic functions are to store digital data supplied at the output of an ARINC 573 FDAU or other similar acquisition unit and provide an easy access to this stored data for systematic ground processing for performance monitoring, maintenance monitoring or other purposes.

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.

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.

This standard provides design guidance for the development and installation of an expandable Flight Data Acquisition and Recording System. The functions defined include flight data acquisition through suitable electrical interfaces, conversion of analog input signals into a standard serial data output and the capability for expansion to permit increased data handling capacity.

The purpose of this document is to delineate, in an organized fashion, the protocols used by Aircraft Communication Addressing and Reporting System (ACARS) Management Units (MU) defined in ARINC Characteristic 724B and Communications Management Unit (CMU) defined in ARINC Characteristic 758, in their interactions with other onboard avionics equipment. The purpose of this document is to delineate, in an organized fashion, the protocols used by Aircraft Communication Addressing and Reporting System (ACARS) Management Units (MU) defined in ARINC Characteristic 724B and Communications Management Unit (CMU) defined in ARINC Characteristic 758, in their interactions with other onboard avionics equipment.

ARINC Report 679 defines the functional characteristics of an airborne server that will support Electronic Flight Bags (EFBs) and similar peripherals used in the flight deck, cabin, and maintenance applications. The document defines how EFBs will efficiently, effectively, safely, and securely connect to the airborne server in a way that offer expanded capabilities to aircraft operators. The airborne server has two main functions, first to provide specific services to connected systems, and second to provide centralized security for the EFB and its data. This document is a functional airborne server definition. It does not define the physical characteristics of the server.

This document sets forth the characteristics of an Aircraft Interface Device (AID) intended for installation in commercial aircraft. The intent of the document is to provide general and specific design guidance for the development of an AID for use in retrofit applications associated with aircraft typically developed between the mid-1970s through the 1990s, that primarily utilize ARINC 700 series avionics, and that interface with the aircraft via ARINC 429 and ARINC 717 unidirectional buses and Hi/Lo discrete signals. This document describes the desired operational capability of the AID and the standards necessary to ensure interchangeability.

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 document defines a Communications Management Unit (CMU) as an on-board message router capable of managing various datalink networks and services available to the aircraft. Supplement 3 was developed to support ATS/ATN datalink recording requirements. The existing simulator data bus interface was converted to a shared simulator/CVR interface.

This document identifies and describes the aircraft avionics capability necessary for operation in the evolving Communications Navigation Surveillance/Air Traffic Management (CNS/ATM) environment expected for the FAA NextGen program, Single European Sky ATM Research (SESAR) program and considerations of the Japan Collaborative Actions for Renovation of Air Traffic Systems (CARATS). These capabilities are intended to satisfy the industry's long-term CNS/ATM operational objectives.

This standard expands ARINC 660 to include industry-defined architectures for the CNS/ATM operating environment. These architectures are intended to meet long-term requirements (e.g., ADS-B, CPDLC, etc.) and provide growth for the future. Airlines support the implementation of these architectures for the long-term. This standard represents broad airline consensus for developing avionics equipment providing CNS/ATM operating capabilities.

The purpose of this standard is to provide a source of definitions of terms and acronyms commonly used in the air transport maintenance community for test and evaluation with an emphasis on terms applicable to BITE.