Search Results

The Aerospace Technical Paper Collection is a family of technical papers as either an annual subscription (current papers, archived papers, or both) or a perpetual collection (1906-1997). This collection is perfect for aerospace engineers, managers, or educators who need access to the most current content covering today's most relevent topics. Please contact one of our sales representatives to learn more and start your subscription today! SAE Sales Team customersales@sae.org 1-888-875-3976 (U.S. and Canada) 1-724-772-4086 (Outside the U.S.)

The purpose of this standard is to provide a method for packaging aircraft software parts for distribution using contemporary media or by electronic distribution. This project intends to standardize and provide guidance for the storage of floppy based software, currently packaged in media set parts. This standard format can be then stored or distributed on a single physical media member (CD-ROM), or by electronic crate. The obsolescence of floppy disks drive an urgent need for this guidance.

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

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 is based upon the SAE ARP5602 document, A Guideline for Aerospace Platform Fiber Optic Training and Awareness Education. ARINC Report 807: Fiber Optic Training Requirements is a subset of the SAE ARP5602 document designed to meet the requirements of the commercial air transport industry. Certification to the SAE ARP5602 document fulfills the requirements of ARINC Report 807. This document defines recommended general practices for training requirements of aerospace fiber optic systems. It is the intention of this document to outline proven training practices and general standards of workmanship for technicians engaged in aerospace fiber optic manufacturing, installation, maintenance, and repair for the air transport industry. It is also recommended that management and purchasing personnel receive fundamental training to familiarize themselves with the requirements of aerospace fiber optics.

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.

ARINC Specification 848 is a functional standard based on a protocol specification profile for a secured network interface. The purpose is to define a common method of initiating a mutually authenticated tunnel between an aircraft service and its Enterprise service. ARINC Specification 848 defines a standard implementation for securing the communications between an onboard Local Area Network (LAN) and an Enterprise LAN on the ground. Various aircraft network architectures and various air to ground communication channels (aka media) are accommodated in this document. For example, L-band Satellite Communication (Satcom), Ku/Ka-band Satcom, Gatelink Cellular, and Gatelink are considered.

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.

"Spotlight on Design" features video interviews and case study segments, focusing on the latest technology breakthroughs. Viewers are virtually taken to labs and research centers to learn how design engineers are enhancing product performance/reliability, reducing costs, improving quality, safety or environmental impact, and achieving regulatory compliance. Sensors are essential to the safety, efficiency, and dependability of modern vehicles. Crash sensors can anticipate a collision faster than humans would, and tire pressure sensors can alert the driver or pilot in case action is needed. In the episode "Sensors: Advanced Safety" (20:36) Continental engineers look at the evolution of passive safety systems, discuss the changes in sensors over the last ten years and what is coming next. Engineers at Meggitt demonstrate how tire pressure monitoring system sensors for aerospace are built and tested.

Given the fast changing market demands, the growing complexity of features, the shorter time to market, and the design/development constraints, the need for efficient and effective verification and validation methods are becoming critical for vehicle manufacturers and suppliers. One such example is fault-tree analysis. While fault-tree analysis is an important hazard analysis/verification activity, the current process of translating design details (e.g., system level and software level) is manual. Current experience indicates that fault tree analysis involves both creative deductive thinking and more mechanical steps, which typically involve instantiating gates and events in fault trees following fixed patterns. Specifically for software fault tree analysis, a number of the development steps typically involve instantiating fixed patterns of gates and events based upon the structure of the code. In this work, we investigate a methodology to translate software programs to fault trees.

There are many macro drivers that are creating opportunities for transportation electrification. They include the environment, dependence on foreign oil, national security, battery technology and government incentives to name a few. In light of this growing momentum consumers will have choices to where they can charge ? at home, workplace or publicly. Electrical vehicle supply equipment will drive value throughout the supply chain ? installer, building owner, automaker, suppliers, utilities and consumers. Market acceptance will occur when consumer?s needs and wants are met. To meet these needs access to products through multiple channels will be required. Presenter Manoj Karwa, Leviton Manufacturing Co. Inc.