Search Results

This document specifies how application to application navigation is managed on tablet EFB devices. Topics include: inter-application navigation for users, blending of multiple applications into a single workflow, single data entry with data shared across applications.

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.

The purpose of this document is to evaluate Communication, Navigation, and Surveillance (CNS) Distributed Radio architectures and the feasibility of distributing the RF and systems processing sections to ensure the following: Reduce cost of equipment Reduce Size, Weight, and Power (SWaP) Ease of aircraft integration Growth capability built into the design Maintain or improve system availability, reliability, and maintainability It provides a framework to determine whether it is feasible to develop ARINC Standards that support CNS distributed radio architectures.

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.

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.

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.

This SAE Aerospace Recommended Practice (ARP) provides guidance to develop and assure validation and verification of IVHM systems used in autonomous aircraft, vehicles and driver assistance functions. IVHM covers a vehicle, monitoring and data processing functions inherent within its sub-systems, and the tools and processes used to manage and restore the vehicle’s health. The scope of this document is to address challenges and identify recommendations for the application of integrated vehicle health management (IVHM) specifically to intelligent systems performing tasks autonomously within the mobility sector. This document will focus on the core aspects of IVHM for autonomous vehicles that are common to both aerospace and automotive applications. It is anticipated that additional documents will be developed separately to cover aspects of this functionality that are unique to each application domain.

This SAE Aerospace Information Report will be a compilation of system safety engineering and management terms and definitions covering concepts used across multiple products and disciplines

This AIR addresses the use of Software tools to supplement or automate human activities in the development of systems, but not the hardware or software items within those systems. If a systems development tool is also used in the scope of hardware or software item development, for that usage it would then become subject to the guidance presented in DO-254 and DO-178B/C, respectively.

This AIR will provide a basic understanding of STPA and how it can be applied to development and safety assessment of civil aircraft. It will explain, by way of an example, the information needed to begin STPA, the expected STPA outputs, and the phases of aircraft development and safety assessment that can be supported by STPA.

Clarify the role of the human considerations in Functional Hazard Assessments by identifying the sufficient input information regarding those considerations from the development process, how failure conditions may use that information, and what information the safety assessment process provides to other processes, particularly Human Factors, to assure those aspects of failure conditions are valid.

This AIR would examine the applicability of ARP 4754 and ARP 4761 to UAS and would identify the shortcomings in both recommended practices with regards to the specific technical aspects needed for UAS development.

This Aerospace Informational Report (AIR) provides guidance on using environmental, electrochemical, and electrical resistance measurements to monitor environment spectra and corrosivity of service environments, focusing on parameters of interest, existing measurement platforms, deployment requirements, and data processing techniques. The sensors and monitoring systems provide discrete time-based records of 1) environmental parameters such as temperature, humidity, and contaminants; 2) measures of alloy corrosion in the sensor; and 3) protective coating performance in the sensor. These systems provide measurements of environmental parameters, sensor material corrosion rate, and sensor coating condition for use in assessing the risk of atmospheric corrosion of the structure.

Development of a new Industry Standard related to GIDEP Reporting.

The SAE E-32 Committee is requested to develop standards for Commercial Aircraft Engine Monitoring to support the Continued Airworthiness of aircraft in general, with particular emphasis on the ETOPS (Extended Operations) to support the regulations. 14CFR A33.3 (c) ETOPS Requirements. For an applicant seeking eligibility for an engine to be installed on an airplane approved for ETOPS, the Instructions for Continued Airworthiness must include procedures for engine condition monitoring. The engine condition monitoring procedures must be able to determine prior to flight, whether an engine is capable of providing, within approved engine operating limits, maximum continuous power or thrust, bleed air, and power extraction required for a relevant engine inoperative diversion. For an engine to be installed on a two-engine airplane approved for ETOPS, the engine condition monitoring procedures must be validated before ETOPS eligibility is granted.

The ARP shall cover the objectives and activities of Verification & Vallidation Processes required to assure high quality and/or criticality level of an IVHM Systems and Software.

The processes outlined in this document cover the entire aircraft for both commercial and military applications. In addition to on-board systems, it covers on-ground elements as well. The practical application of this standardized process is detailed in the form of a checklist. As in all HM-1 documents, the scope of this document covers sensing and acquisition systems, typically on board, data transmission systems and processes, methods and hardware for data analysis, and finally, maintenance actions. The on-board aspects relating to safety of flight, pilot notification, etc., are addressed by the other SAE Committees standards and documents. To help explain the process and the use of the checklist, some high-level use cases related to maintenance credit applications are included.

Aeroengine Hazard Zone document will standardize the major aspects of processes that may be used for the determination of hazards to aerospace personnel when performing duties on turbojet, turbofan, turboprop and auxiliary power units installed on aircraft. It includes discussions of basic definitions, analytical and methods to describe the hazard zones for a given propulsion system installed on various aircraft. Standardization of definitions of sources of hazards, tools, presentation of hazard zones would benefit airplane, engine, airline customers and airport planners.