Search Results

Standard

LOGICAL SOFTWARE PART PACKAGING FOR TRANSPORT

2020-11-16

CURRENT

ARINC641-1

The purpose of this standard is to provide a method for packaging aircraft software parts for distribution using contemporary media or by electronic distribution. This project intends to standardize and provide guidance for the storage of floppy based software, currently packaged in media set parts. This standard format can be then stored or distributed on a single physical media member (CD-ROM), or by electronic crate. The obsolescence of floppy disks drive an urgent need for this guidance.

Standard

BITE GLOSSARY

1986-12-18

CURRENT

ARINC612

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.

Standard

AIRCRAFT SOFTWARE COMMON CONFIGURATION REPORTING

2019-08-13

CURRENT

ARINC843-1

This standard defines a common configuration report format that can be retrieved from an aircraft for use by ground tools and maintenance personnel. Reports will be generated in Extensible Markup Language (XML) format and structured as defined by this document. Several optional elements and attributes are defined to allow flexibility for a given report. This standard provides aircraft manufacturers, regulatory agencies, and airlines a format standard for aircraft configuration reporting, and facilitates automated comparison of configuration data reports (e.g., authorized versus as flying, etc.).

Standard

TIMELY RECOVERY OF FLIGHT DATA (TRFD)

2021-08-06

CURRENT

ARINC681

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.

Standard

EMBEDDED INTERCHANGE FORMAT FOR OBSTACLE DATABASES

2018-12-21

CURRENT

ARINC815

This document defines an open encoding format for obstacle databases. This format, when designed and implemented, will enable a quick, economic, and efficient use of Obstacle Databases (ObsDBs). However, since industry does not require applications to be standardized, data interpretation is not addressed in this document.

Standard

EMBEDDED INTERCHANGE FORMAT FOR TERRAIN DATABASES

2018-12-21

CURRENT

ARINC813

This document defines an open encoding format for terrain databases. This format, when designed and implemented, will enable a quick, economic, and efficient use of Terrain Databases (TerrDBs). However, since industry does not require applications to be standardized, data interpretation is not addressed in this document.

Standard

AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE PART 3A CONFORMITY TEST SPECIFICATIONS FOR ARINC 653 REQUIRED SERVICES

2019-07-18

CURRENT

ARINC653P3A-1C1

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.

Standard

CABIN CONNECTORS AND CABLES PART 1 DESCRIPTION AND OVERVIEW

2012-11-19

CURRENT

ARINC800P1

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.

Standard

MULTIPLE-INPUT COCKPIT PRINTER

1998-06-01

CURRENT

ARINC740-1

This standard describes the form, fit, function and interfaces of an airborne printer capable of communicating with multiple systems one at a time. The printer contains the circuitry for acquisition, buffering and processing of coded alphanumeric messages for print-out on half-width paper.

Standard

NAVIGATION SYSTEMS DATABASE

2011-12-05

CURRENT

ARINC424-20

THE CURRENT VERSION OF THIS DOCUMENT IS 424-21. THIS PREVIOUS VERSION IS AVAILABLE FOR YOUR CONVENIENCE. This standard provides a data base comprising standards used for the preparation of a navigation system data base. This data may be used with the operational flight software in a wide range of navigational equipment.

Standard

NAVIGATION SYSTEMS DATABASE

2005-11-23

CURRENT

ARINC424-18

THE CURRENT VERSION OF THIS DOCUMENT IS 424-21. THIS PREVIOUS VERSION IS AVAILABLE FOR YOUR CONVENIENCE. This standard provides a data base comprising standards used for the preparation of a navigation system data base. This data may be used with the operational flight software in a wide range of navigational equipment.

Standard

NAVIGATION SYSTEM DATA BASE

2004-08-31

CURRENT

ARINC424-17

THE CURRENT VERSION OF THIS DOCUMENT IS 424-21. THIS PREVIOUS VERSION IS AVAILABLE FOR YOUR CONVENIENCE. This standard provides a data base comprising standards used for the preparation of a navigation system data base. This data may be used with the operational flight software in a wide range of navigational equipment.

Standard

NAVIGATION SYSTEM DATA BASE

2002-08-30

CURRENT

ARINC424-16

THE CURRENT VERSION OF THIS DOCUMENT IS 424-21. THIS PREVIOUS VERSION IS AVAILABLE FOR YOUR CONVENIENCE. This standard provides a data base comprising standards used for the preparation of a navigation system data base. This data may be used with the operational flight software in a wide range of navigational equipment.

Standard

AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE, PART 3A, CONFORMITY TEST SPECIFICATION FOR ARINC 653 REQUIRED SERVICES

2014-01-13

CURRENT

ARINC653P3A

The scope of this Compliance Test Specification is to define test procedures to demonstrate compliance of the API behavior only. This does not include performance tests (e.g., benchmark tests), nor demonstration of capability of the operating systems to manage combinations of configuration parameters.

Standard

AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE PART 3A CONFORMITY TEST SPECIFICATIONS FOR ARINC 653 REQUIRED SERVICES

2018-09-07

CURRENT

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

Standard

AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE PART 3B CONFORMITY TEST SPECIFICATIONS FOR ARINC 653 EXTENDED SERVICES

2018-09-07

CURRENT

ARINC653P3B

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.

Standard

AIRCRAFT SOFTWARE COMMON CONFIGURATION REPORTING

2015-07-31

CURRENT

ARINC843

This standard defines a common configuration report format that can be retrieved from an aircraft for use by ground tools and maintenance personnel. Reports will be generated in Extensible Markup Language (XML) format and structured as defined by this document. Several optional elements and attributes are defined to allow flexibility for a given report. This standard provides aircraft manufacturers, regulatory agencies, and airlines a format standard for aircraft configuration reporting, and facilitates automated comparison of configuration data reports (e.g., authorized versus as flying, etc.).

Standard

ELECTRONIC FLIGHT BAG (EFB) APPLICATION CONTROL INTERFACE (ACI) STANDARD

2012-11-20

CURRENT

ARINC840-2

The document defines a common software interface boundary between Electronic Flight Bag (EFB) application software and the EFB platform. The standard interface will allow EFB applications to be launched and controlled independent of other EFB applications. Supplement 2 provides enhancements to the original specification, including a data repository service where common flight data parameters can be used among several applications running on the EFB. A virtual keyboard and line printer service is also included.

Standard

LOADABLE SOFTWARE PART DEFINITION FORMAT

2014-01-02

CURRENT

ARINC838

This Specification defines: The syntax (simple generic grammar) and semantics (definition of the fields, such as name, type, constraints and meaning) of the ARINC 838 Loadable Software Part Definition Format in Section 3. The definition of XML notation of the grammar in Section 4. The definition of binary notation of the grammar in Section 5.

Standard

FLIGHT MANAGEMENT COMPUTER SYSTEM

1994-06-01

CURRENT

ARINC702-6

This standard defines a FMCS for installation in commercial transport aircraft. The FMCS provides performance data, performance computations, fuel management functions, and navigation and guidance to a desired flight plan.