Search Results

AS9131 - This standard defines the common nonconformance data definition and documentation that an internal or external supplier or sub-tier supplier must submit when informing a customer of a nonconformity. The requirements shall be are applicable for reporting a nonconforming product to the owner/operator (i.e., end item user), if specified by contract. Reporting of nonconformance data, either electronically or conventionally on paper, is subject to the terms and conditions of the contract. This also includes, where applicable, data access under export control regulations.

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.

This document defines an Aircraft Data Interface Function (ADIF) developed for aircraft installations that incorporate network components based on commercially available technologies. This document defines a set of protocols and services for the exchange of aircraft avionics data across aircraft networks. A common set of services that may be used to access specific avionics parameters are described. The ADIF may be implemented as a generic network service, or it may be implemented as a dedicated service within an ARINC 759 Aircraft Interface Devices (AID) such as those used with an Electronic Flight Bag (EFB). Supplement 8 includes improvements in the Aviation Data Broadcast Protocol (ADBP), adds support for the Media Independent Aircraft Messaging (MIAM) protocol, and contains data security enhancements. It also includes notification and deprecation of the Generic Aircraft Parameter Service (GAPS) protocol that will be deleted in a future supplement.

The purpose of this document is to provide an overview of data networking standards recommended for use in commercial aircraft installations. These standards provide a means to adapt commercially defined networking standards to an aircraft environment. It refers to devices such as bridges, switches, routers and hubs and their use in an aircraft environment. This equipment, when installed in a network topology, can optimize data transfer and overall avionics performance.

This document defines a standard implementation for strong client authentication and encryption of Wi-Fi-based client connections to onboard Wireless LAN (WLAN) networks. WLAN networks may consist of multi-purpose inflight entertainment system networks operating in the Passenger Information and Entertainment System (PIES) domain, dedicated aircraft cabin wireless networks or localized Aircraft Integrated Data (AID) devices operating in the Aircraft Information Services (AIS) domain. The purpose of this document is to focus on the client devices requiring connections to these networks such as electronic flight bags, flight attendant mobile devices, onboard Internet of Things (IoT) devices, AID devices (acting as clients) and mobile maintenance devices. Passenger devices are not within the focus of this document.

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.

ARINC 814 defines an XML encoding and compression standard for aviation. It is based on the Open Geospatial Consortium (OGC) Binary XML document. Binary XML encoding is extended in a way that is both flexible and robust. Compression is added on top of the binary encoding. ARINC 814 is expected to be used with Aeronautical Databases, in particular, ARINC Specification 813: Embedded Interchange Format for Terrain Databases, ARINC Specification 815: Embedded Interchange Format for Obstacle Databases, and ARINC Specification 816: Embedded Interchange Format for Airport Mapping Database.

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.

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.

This Digital Annex (DA) contains the current, full-PDF version of ARP5149B, Training Program Guidelines for Deicing/Anti-Icing of Aircraft on Ground, as well as .jpeg format files of Appendix D, Application Guidelines Configuration, Critical Component, and Spray Area Diagrams for Aircraft. The .jpeg diagram files may be used by purchasers in accordance with the terms of the included license agreement.

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.

Enhanced License for Data Dictionary for Quantities Used in Cyber Physical Systems (AS6969B) allowing for greater usage as outlined in the terms of the Enhanced License. Terms can be reviewed prior to purchase once item is added to the cart. Data Dictionary for Quantities Used in Cyber Physical Systems (AS6969B) This data dictionary provides definitions for quantities commonly used in the command and control of cyber physical systems. It defines mathematical and logical terms, quantities, measurement units, reference systems, measurands, and measurements. It also defines common quantity modalities. The dictionary is structured to be convenient to data modelers. It is also extendable so that users can create their own quantity domains.

Enhanced License for Data Dictionary for Quantities Used in Cyber Physical Systems (AS6969) allowing for greater usage as outlined in the terms of the Enhanced License. Terms can be reviewed prior to purchase once item is added to the cart. Data Dictionary for Quantities Used in Cyber Physical Systems (AS6969) This data dictionary provides a mathematically coherent set of definitions for quantity types used in data models for unmanned systems. In this data dictionary, a quantity is defined as a property of a phenomenon, substance, or body whose value has magnitude.

Enhanced License and UML Model for Data Dictionary for Quantities Used in Cyber Physical Systems (AS6969) allowing for greater usage as outlined in the terms of the Enhanced License. Data Dictionary for Quantities Used in Cyber Physical Systems (AS6969A) This data dictionary provides definitions for quantities commonly used in the command and control of cyber physical systems. It defines mathematical and logical terms, quantities, measurement units, reference systems, measurands, and measurements. It also defines common quantity modalities. The dictionary is structured to be convenient to data modelers. It is also extendable so that users can create their own quantity domains.