This ADB Subcommittee is responsible for the standardization of the aeronautical database structures for terrain data (ARINC 813), obstacle data (ARINC 815) and airport surface data (ARINC 816).
The AEEC has prepared airborne radio transceiver standards (ARINC 766) for broadband wireless communication on the airport surface using the AeroMACS profile of IEEE 802.16 Wi-Max.
The AOC Subcommittee develops and maintain a set of standardized AOC messages (ARINC 633) capable of being used by multiple airlines on multiple aircraft types.
The Weather Radar Working Group will define a new federated weather radar system for new aircraft type design using remote RF components and advanced antenna design using Electronically Scanned Array (ESA).
The AGCS Subcommittee develops ARINC Standards that ensure that current and emerging satellite air-ground communication system definitions are aligned with airline operational requirements and defined for cost-effective implementation. This includes Inmarsat (ARINC 781) and Iridium (ARINC 771) services.
The goal of the activity is to define standard interface requirements for a new ARINC 600 Size 4 connector.
The goal of the APEX Subcommittee is to develop ARINC 653, Avionics Application Software Standard Interface, defining a standard interface between avionics application software and Real Time Operating System (RTOS).
The CSS develops ARINC Standards for numerous cabin systems used by the cabin crew and for airline passenger entertainment. This includes equipment interface standards and networking standards to allow airlines to implement preferred systems for their passengers.
The CDS Subcommittee develops ARINC 661 flight deck display interface standards for primary flight display and related applications (e.g., FMS) widely used on all aircraft types. Growth for CNS/ATM applications that provide advanced operational concepts, such as touch screen, is provided.
The DLK Subcommittee develops and maintains ARINC Standards for communication services that promote reliable, uniform, and cost efficient transfer of data between the aircraft and various locations on the ground. These include legacy ACARS, ATN/OSI and current developments such as Controller Pilot Data Link Communication (CPDLC) using Data Comm services.
The Data Link Users Forum is a coordinating activity among airlines and cargo carriers, data link service providers, aircraft manufacturers, avionics manufacturers, and others. It focuses on technical issues of mutual interest to operators. The discussions lead to the identification and resolution of numerous issues that collectively improve data link performance. The product of this activity assures that operators receive significant operational and economic benefits of air/ground communication services.
The EFB Subcommittee develops ARINC Standards that enable standardized EFB installation and connectivity on all types of aircraft . The standards are comprised of both hardware and software specifications and apply to interfaces, wiring and connectors, data protocols and application control.
The EFB Users Forum is a joint activity with IATA that enables airlines and other aircraft operators to state their preferences in the evolution of EFB hardware, software applications, and connectivity to the ground. This ensure operational benefit to the flight deck crew and the economic benefit to the airlines. Flight Operations, Information Technology, Engineering, and Maintenance disciplines are represented among the participants of the EFB Users Forum.
The Fiber Optics Subcommittee develops physical interfaces standards, design guidelines, component specifications, test procedures, and maintenance procedures for fiber optic components used on all types of aircraft.
ARINC 702A Flight Management Computer standards are developed for emerging airspace requirements and take advantage of advancements in Communication, Navigation and Surveillance (CNS), all with the collective goal to increase the capacity and efficiency of the airspace.
The goal of the GAIN Subcommittee is to standardize galley insert physical dimensions, electrical interfaces, communication protocol, test guidelines, and maintenance provisions.
The goal of the GAT/TRFD Working Group is to propose solutions that can positively identify and track an aircraft with minimal impact on aircraft production and retrofit.
The goal is to maintain the ARINC Standards for GNSS-based navigation and landing system equipment used on all types of aircraft. This includes the latest GNSS navigation sensors: ARINC 743A, ARINC 743B, ARINC 743C, and ARINC 755.
The IPS Subcommittee leads the standardization effort to provide ATN/IPS safety services to the aircraft. It will define a transition path from ACARS and ATN/OSI services to ATN/IPS as the end state. ARINC Report 658 provides the roadmap to ATN/IPS. Technical requirements are coordinated with aviation Standards Development Organizations (SDOs), Air Navigation Service Providers (ANSPs) and others.
The KSAT Subcommittee develops ARINC Standards for broadband satellite systems and aircraft installation provisions for Ku-Band and Ka-Band satcom equipment. This equipment provides standardized network interfaces and domain separation for non-safety satcom installations.
The NDB Subcommittee maintains ARINC 424 data base standards used with Flight Management Computers and Flight Management Functions to improve overall aircraft performance.
The NIS Subcommittee develops ARINC Standards for secure broadband equipment interfaces, digital signature, and a roadmap for introducing IPv6 into aviation. The goal is to define standards for aviation that are based upon openly available commercial standards.
The SDL Subcommittee develops ARINC Standards for software data loading. This includes standards for file format, media type, part numbering and terminology will be developed in a way that can be used for various data loading devices.
The SAI Subcommittee provides technical leadership in the development of ARINC Standards used for new aircraft and major derivatives programs. It works with the airframe manufacturers and Air Navigation Service Providers (ANSPs) to develop standards for CNS/ATM, namely NextGen and SESAR airspace requirements. New project proposals (APIMs) are developed and reviewed by the SAI Subcommittee prior to more formal consideration by the AEEC Executive Committee.
The goal is to maintain Traffic Surveillance standards which define avionics airborne equipment with Traffic Alert and Collision Avoidance System (TCAS), Air Traffic Control Transponder (ATCRBS/Mode S), and Automatic Dependent Surveillance-Broadcast (ADS-B) functionalities.
ARINC Specification 429, Digital Information Transfer System (DITS) is updated as necessary to coordinate with industry ARINC 429 labels, word structure and equipment ID assignments
The AEEC serves as the administrator of the Manufacturer's Designator Codes for loadable software parts documented in ARINC Report 665, Loadable Software Standards.
The goal of the AT-ASB Working Group is to develop a standard that eliminates differences in service bulletins for avionics products from different suppliers.
The Field Loadable Software (FLS) Working Group will update ARINC 667 to maintain common terminology, management practices, communications standards, storage formats, and distribution methods related to aircraft software configuration management.
The European FSTD Technical Group (EFTeG) was chartered as a result of feedback from FSEMC conferences. The flight simulation industry perceived a need for a forum for simulator operators that are subject to EASA regulations to discuss technical issues. This forum is also intended for EASA flight simulation regulatory representatives to discuss regulatory qualification and compliance questions with operators.
The objective of the Future Concepts for Simulators (FCS) Subcommittee is to foster the development of Flight Training Device (FTD) engineering and maintenance concepts.
The intent of the meeting is to open up discussion to alternative means of validation of FSTDs – and share and promote new ideas and ways of optimizing regular testing and checking methods. We invite your organization to participate in this “idea generation” activity to ensure we consider ideas from across the industry.
The objective of the Simulator Software (SimSoft) Working Group is to identify, mitigate, and improve the development and use of software used in Flight Training Device (FTD) operations, engineering, and maintenance.