Search Results

Standard

AERONAUTICAL MOBILE AIRPORT COMMUNICATION SYSTEM (AEROMACS) TRANSCEIVER AND AIRCRAFT INSTALLATION STANDARDS

2017-07-07

CURRENT

ARINC766

This documents defines the Installation Characteristics of an airborne radio transceiver capable of broadband wireless communication with an Airport Surface Network. The Aeronautical Mobile Airport Communications System (AeroMACS) Radio Unit (ARU) will operate in the aeronautical protected frequency of 5091 MHz to 5150 MHz, utilizing the IEEE 802.16e WiMAX protocol. It is intended to offload some of the congested narrowband VHF airport traffic used for ATS and AOC communications. ARU and Antenna Form, Fit, Function and Interfaces are described.

Standard

AIRCRAFT DATA NETWORK PART 1 SYSTEMS CONCEPTS AND OVERVIEW

2006-06-30

CURRENT

ARINC664P1-1

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.

Standard

AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE PART 0 OVERVIEW OF ARINC 653

2019-08-07

CURRENT

ARINC653P0-2

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.

Standard

AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE PART 0 OVERVIEW OF ARINC 653

2021-11-15

CURRENT

ARINC653P0-3

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.

Standard

AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE PART 0 OVERVIEW OF ARINC 653

2015-08-03

CURRENT

ARINC653P0-1

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.

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

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

COMMON TERMINOLOGY AND FUNCTIONS FOR SOFTWARE DISTRIBUTION AND LOADING

2018-07-11

CURRENT

ARINC645

This document provides airlines, airframe manufacturers, aircraft equipment suppliers, and others with information that is specific to data, software, and ground tools used in aviation configuration and data management.

Standard

COMMON TERMINOLOGY AND FUNCTIONS FOR SOFTWARE DISTRIBUTION AND LOADING

2021-08-11

CURRENT

ARINC645-1

This document provides airlines, airframe manufacturers, aircraft equipment suppliers, and others with information that is specific to data, software, and ground tools used in aviation configuration and data management. As a starting point, this document provides guidance on: Which standard to use in specific situations The use of and how integrity checks should be applied Common terminology in airborne software management Since airplanes started using software controlled hardware, there has been a need to standardize processes and terminology. This document is the centroid to which other software standards are related.

Standard

DATA LABELS

2019-01-21

CURRENT

ARINC429P1-19DL

This product is a Zip file that contains a subset of material in ARINC Specification 429, Part 1. Specifically: Attachment 1-1, Label Codes, in an Excel file; Attachment 1-2, Equipment Codes, in a Word file; Attachment 2A, Data Standards - BCD Data, in a Word file; and Attachment 2B, Data Standards - BNR Data, in a Word file.

Standard

EMBEDDED INTERCHANGE FORMAT FOR AIRPORT MAPPING DATABASE

2016-08-31

CURRENT

ARINC816-2C1

This document defines an open encoding format for airport databases which are loaded in airborne systems. This format, when designed and implemented, will enable a quick, economic, and efficient use of AMDB. However, since industry does not require applications to be standardized, data interpretation is not addressed in this document.

Standard

EMBEDDED INTERCHANGE FORMAT FOR AIRPORT MAPPING DATABASE

2007-11-19

CURRENT

ARINC816-1

This document defines an open encoding format for airport databases which are loaded in airborne systems. This format, when designed and implemented, will enable a quick, economic, and efficient use of AMDB. However, since industry does not require applications to be standardized, data interpretation is not addressed in this document.

Standard

EMBEDDED INTERCHANGE FORMAT FOR AIRPORT MAPPING DATABASE

2016-08-31

CURRENT

ARINC816-3

This document defines an open encoding format for airport databases which are loaded in airborne systems. This format, when designed and implemented, will enable a quick, economic, and efficient use of AMDB. However, since industry does not require applications to be standardized, data interpretation is not addressed in this document.

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

FLIGHT RECORDER ELECTRONIC DOCUMENTATION (FRED)

2009-07-01

CURRENT

ARINC647A-ER1

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.

Standard

GATE-AIRCRAFT TERMINAL ENVIRONMENT LINK (GATELINK)-AIRCRAFT SIDE

1994-01-01

CURRENT

ARINC751

This standard describes the electrical and optical interface definitions for Gatelink communications. Gatelink is a 100 Mbps full-duplex communication link between a communication system inside the airport terminal (or at the maintenance position) and a communication system onboard a parked aircraft.

Standard

GUIDANCE FOR TARGET HARDWARE DESIGN PART 2 AIRBORNE HIGH SPEED DATA LOADER (ARINC REPORT 615-4)

2016-07-29

CURRENT

ARINC844P2

ARINC Specification 844, prepared in two parts, defines the requirements of a Target Data Loader (TDL) from the target hardware point of view. Both parts are based on two data loading standards: Part 1 clarifies ARINC Report 615-3: Airborne Computer High Speed Data Loader, Part 2 clarifies ARINC Report 615-4: Airborne Computer High Speed Data Loader. ARINC Report 615 was originally written from the data loader point of view. It is important that a target designer have a general understanding of the operation of a data loader in its modern implementation. Equally important is the need for data loader manufacturers to understand the standardized implementation requirements and supported subset of ARINC 615 features that are defined in ARINC 844, Parts 1 and 2. Therefore, ARINC Specification 844 is expected to provide value to both data loader and target implementers.

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

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.