Refine Your Search

Topic

Search Results

Standard

3GCN - SEAT DISTRIBUTION SYSTEM

2014-08-15
CURRENT
ARINC809-3
This specification defines general architectural philosophy and specific design guidance for the proper installation and interface of various cabin equipment within the seats. Consistency with this specification allows each component installed on the seat to operate in concert when integrated with other relevant cabin type equipment. Standard electrical and mechanical interfaces of the In- Flight Entertainment System (IFES) equipment for the 3rd Generation Cabin Network (3GCN) associated with the seat are defined. This equipment consists of the headphone jacks (HPJ), passenger control unit (PCU)/multi function handset (including the cord), seat video display (SVD), remote data outlet (RDO), integrated seat box (ISB) which includes the seat power box (SPB)/seat data box (SDB), remote power outlet (RPO), and in-seat cables. Appropriate definitions are also provided for other electrical devices associated with the seat control/position mechanism.
Standard

AIR TRANSPORT INDICATOR CASES AND MOUNTING

1976-12-15
CURRENT
ARINC408A
This standard defines mechanical dimensions and thermal standards for aircraft indicators and displays. Thermal interface data is included for indicators and their operating environment. These indicators may be stand alone or part of larger integrated display system. This standard defines mechanical dimensions and thermal standards for aircraft indicators and displays. Thermal interface data is included for indicators and their operating environment. These indicators may be stand alone or part of larger integrated display system.
Standard

AIRBORNE COMPUTER DATA LOADER

1985-11-15
CURRENT
ARINC603-1
This standard describes the desired characteristics of a data loader intended for use with airborne computers installed on commercial transport aircraft. The data loader transfers data from a tape cartridge to an avionics computer via an ARINC 429 data bus.
Standard

AIRBORNE COMPUTER HIGH SPEED DATA LOADER

1992-08-15
CURRENT
ARINC615-3
This standard provides general and specific guidance for the development of a Portable Data Loader (PDL) for carry-on application and an Airborne Data Loader (ADL) for on-board the airplane. It specifies use of a 3.5 inch floppy disk to upload and download of data and operational programs using an ARINC 429 data bus connected to avionics computers.
Standard

AIRBORNE COMPUTER HIGH SPEED DATA LOADER

2002-05-06
CURRENT
ARINC615-4_ER2
This standard provides general and specific guidance for the development of a Portable Data Loader (PDL) for carry-on application and an Airborne Data Loader (ADL) for on-board the airplane. It specifies use of a 3.5 inch floppy disk to upload and download of data and operational programs using an ARINC 429 data bus connected to avionics computers.
Standard

AIRBORNE ILS RECEIVER

1988-10-31
CURRENT
ARINC578-4
This standard provides basic requirements for a new-generation ILS receiver, whose function is the reception of ILS localizer and glide slope signals and the recovery there from of course-line deviation information for visual display to the pilot, and for use by an automatic flight control system during automatically controlled approaches and landings.
Standard

AIRBORNE PASSENGER ADDRESS AMPLIFIER

1984-07-06
CURRENT
ARINC715-3
This standard describes the characteristics of a PA AMP designed for installation in commercial aircraft. Its function is to amplify control voice, music and internally generated chime audio signals to drive the aircraft cabin loudspeaker system.
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 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

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

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

AVIONCS APPLICATION SOFTWARE STANDARD INTERFACE PART 2 EXTENDED SERVICES

2015-08-21
CURRENT
ARINC653P2-3
As avionics software continues to evolve, so does ARINC Specification 653. ARINC 653 Part 2 specifies extensions (i.e., optional services) to the required Application Program Interfaces (APIs) described in ARINC 653 Part 1. Supplement 3 adds optional multicore services capabilities.
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

AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE PART 1 REQUIRED SERVICES

2015-08-21
CURRENT
ARINC653P1-4
This standard defines a general-purpose Application/Executive (APEX) software interface between the Operating System of an avionics computer and the application software. The interface requirements between the application software and operating system services are defined in a manner that enables the application software to control the scheduling, communication, and status of internal processing elements. Supplement 4 adds multicore processor service capabilities.
Standard

AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE PART 1 REQUIRED SERVICES

2019-12-23
CURRENT
ARINC653P1-5
This standard defines a general-purpose Application/Executive (APEX) software interface between the Operating System of an avionics computer and the application software. The interface requirements between the application software and operating system services are defined in a manner that enables the application software to control the scheduling, communication, and status of internal processing elements. Supplement 5 adds multicore processor service capabilities.
Standard

AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE PART 2 EXTENDED SERVICES

2019-12-23
CURRENT
ARINC653P2-4
As avionics software continues to evolve, so does ARINC Specification 653. ARINC 653 Part 2 specifies extensions (i.e., optional services) to the required Application Program Interfaces (APIs) described in ARINC 653 Part 1. Supplement 4 adds optional multicore services capabilities.
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

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