Refine Your Search

Topic

Search Results

Standard

ACARS PROTOCOLS FOR AVIONIC END SYSTEMS

2017-11-29
CURRENT
ARINC619-5
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.
Standard

ADVANCED FLIGHT MANAGEMENT COMPUTER SYSTEM

2014-12-15
CURRENT
ARINC702A-4
The Advanced FMCS provides expanded functions beyond that defined in ARINC 702 to support the anticipated requirements for operation in the CNS/ATM operating environment. GNSS and RNP based navigation, air-to-ground data link for communications and surveillance, and the associated crew interface control/display definitions are included.
Standard

ADVANCED FLIGHT MANAGEMENT COMPUTER SYSTEM

2018-08-28
CURRENT
ARINC702A-5
The Advanced FMCS provides expanded functions beyond that defined in ARINC 702 to support the anticipated requirements for operation in the CNS/ATM operating environment. GNSS and RNP based navigation, air-to-ground data link for communications and surveillance, and the associated crew interface control/display definitions are included. The NextGen/SESAR concepts and their relative effects on the FMS are addressed in this document. The functional requirements also apply to a Flight Management Function (FMF) in an Integrated Modular Avionics (IMA) architecture with software partitions.
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

AIR TRANSPORT AVIONICS EQUIPMENT INTERFACES

2017-07-11
CURRENT
ARINC600-20
ARINC 600 is a mechanical packaging standard that is used with the ARINC 700-series of digital avionics equipment. It provides mechanical, electrical, and environmental interfaces between LRUs and the racks or cabinets in which they are installed. Provides connector shell definition, connector insert layout and mounting dimensions.
Standard

AIRBORNE GLOBAL POSITIONING SYSTEM RECEIVER

1990-03-01
CURRENT
ARINC743
This standard provides design guidance for the development of GPS sensors for airline use. It describes the operational capability of the GPS receiver and the standards necessary to ensure interchangeability. GPS provides navigation data to pilots and provides data for use by other aircraft systems.
Standard

AIRBORNE WEATHER RADAR WITH FORWARD LOOKING WINDSHEAR DETECTION CAPABILITY

1999-11-15
CURRENT
ARINC708A-3
This standard defines an airborne pulse Doppler weather radar system for weather detection and ranging. It expands the capabilities of the ARINC 708 system through the inclusion of forward looking windshear prediction. It also provides ground-mapping capabilities to facilitate navigation by display of significant land contours.
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

AIRCRAFT DATA NETWORK PART 3 INTERNET-BASED PROTOCOLS AND SERVICES

2009-02-16
CURRENT
ARINC664P3-2
This specification defines Network and Transport layer provisions for data networks that are installed on commercial aircraft. The definitions are based on Internet Engineering Task Force (IETF) Internet protocol and service standards that have been published as Request for Comments (RFC). In some cases the protocols and services are tailored for use on board aircraft. The specification identifies two types of networks: First, Compliant Aircraft Data Network, which operates fully within the applicable Internet specifications. Second, Profiled Aircraft Data Network, in which one or more industry standard protocols have been extended to address the unique environment of aircraft installations. Within the specification, the functionality of Internet protocols and services are defined with the intent that interoperability of components connected to onboard data networks can be achieved without undue restrictions on the component designer.
Standard

AIRCRAFT DATA NETWORK PART 4 INTERNET-BASED ADDRESS STRUCTURE & ASSIGNED NUMBERS

2007-12-21
CURRENT
ARINC664P4-2
This specification defines the addressing plan and rules for addressing used in Aircraft Data Networks (ADN). The plan is organized in accordance with the seven-layer Open Systems Interconnection (OSI) Reference Model. The specification sets forth the structure of addresses that are employed in the ADN and guidance for address determination. This guidance ensures that all applications - that use this address structure to send messages - can know the address structure of the destination(s) at configuration-time.
Standard

AIRCRAFT DATA NETWORK PART 5 NETWORK DOMAIN CHARACTERISTICS AND INTERCONNECTION

2005-04-12
CURRENT
ARINC664P5
ARINC 664, Part 5 provides the design and implementation guidelines for networks installed in aircraft. Such networks may be used to enable network devices to communicate among themselves and with networks outside of the aircraft. This specification defines a set of domains within the aircraft. These domains are defined in terms of the services they provide, the security they provide to the functions within their boundaries, and the connections required between a domain and other domains and networks external to the aircraft. This specification provides general design and implementation guidelines that, when they are implemented by aircraft devices and configured by the system integrator, the devices provide the required connectivity, quality of service, safety and security.
Standard

AIRCRAFT DATA NETWORK PART 7 AVIONICS FULL-DUPLEX SWITCHED ETHERNET NETWORK

2009-09-23
CURRENT
ARINC664P7-1
The purpose of this document is to define a deterministic network: Avionics Full Duplex Switched Ethernet (AFDX). AFDX is a trademark of Airbus and is used with permission. This document also highlights the additional performance requirements of avionics systems within the context of AFDX.
Standard

AIRCRAFT DATA NETWORK PART 8 INTEROPERATION WITH NON-IP PROTOCOLS AND SERVICES

2010-11-12
CURRENT
ARINC664P8-1
This Specification was written to support future aeronautical applications and services beyond those using Transmission Control Protocol/Internet Protocol (TCP/IP). The initial focus is to support air/ground applications using the Aeronautical Telecommunications Network (ATN). These include Controller-Pilot Data Link Communication (CPDLC), Flight Information System (FIS), and Context Management Application (CMA). Supplement 1 was written to allow interoperation with non-IP protocols and services and upper layer services with respect to the OSI reference model. Supplement 1 reflects ICAO Aeronautical Communication Panel recommendations.
Standard

AIRCRAFT DATA NETWORK, PART 2 - ETHERNET PHYSICAL AND DATA LINK LAYER SPECIFICATION

2009-01-16
CURRENT
ARINC664P2-2
This specification provides Ethernet physical parameters and data link layer specifications for use in a commercial aircraft environment. This specification provides general and specific guidelines for the use of IEEE 802.3 compliant Ethernet, 2000 edition. Physical layer and Medium Access Control (MAC) sub-layers are expected to comply with the Open System Interconnection (OSI) Reference Model to enable maximal utilization of off-the-shelf components, both hardware and software, for aviation use. The Ethernet Physical layer specification defines the electrical and optical parameters for the 10BASE-T, 100BASE-TX, and 100BASE-FX Ethernet implementations. This specification references ARINC Specification 600: Air Transport Avionics Equipment Interfaces for definition of copper-based implementations of the Ethernet Physical layer.
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

AIRCRAFT/GROUND INFORMATION EXCHANGE (AGIE) USING INTERNET PROTOCOLS

2014-09-15
CURRENT
ARINC830
The purpose of this document is to define a general purpose non-proprietary information exchange framework and protocol for the conduct of Internet Protocol based message traffic between aircraft and airline ground infrastructure. This standard is motivated by the vision to substantially simplify information processing management for airlines by eliminating multiple dissimilar implementations with a single universal system and thereby establishing a more economical environment.
Standard

AOC AIR-GROUND DATA AND MESSAGE EXCHANGE FORMAT

2010-03-12
CURRENT
ARINC633-1
The purpose of this specification is to support the exchange of certain Aeronautical Operational Control (AOC) air-ground and ground-ground messages. These messages are defined in this specification, apart from those defined in ARINC Specification 620, because they have unique qualities. Like the messages defined in ARINC Specification 620, their usage necessitates a single definition.
Standard

AOC AIR-GROUND DATA AND MESSAGE EXCHANGE FORMAT

2012-11-28
CURRENT
ARINC633-2
This document defines the exchange of Aeronautical Operational Control (AOC) message formats used for air-to-ground communication and ground-to-ground communication. ARINC Specification 633 simplifies the integration of AOC software from different suppliers, intended for use by different airlines, on different aircraft types. It is expected that AOC applications will be hosted on an Electronic Flight Bags (EFB). Supplement 2 includes an extensive updates to the Flight Plan schema per ICAO Flight Plan 2012. New XML schemas are added to define AOC messages for airport weather, air traffic information services (ATIS), crew list, passenger list, notice to airmen, pilot report, and hazard advisory.
Standard

AOC AIR-GROUND DATA AND MESSAGE EXCHANGE FORMAT

2019-01-02
CURRENT
ARINC633-3
The purpose of ARNC 633 is to specify the format and exchange of Aeronautical Operational Control (AOC) communications. Examples of ARINC 633 AOC Structures/Messages include: Flight Plan, Load Planning (i.e., Weight and Balance and Cargo Planning Load Sheets), NOTAMs, Airport and Route Weather data, Minimum Equipment Lists (MEL) messages, etc. The standardization of AOC messages enable the development of applications shared by numerous airlines on different aircraft types. Benefits include improved dispatchability and reduce operator cost.
X