Refine Your Search

Topic

Author

Affiliation

Search Results

SAE MOBILUS Subscription

SAE Aerospace Technical Papers Collection

2016-11-30
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.)
Standard

Quality Management Systems - Nonconformance Documentation - Word Format

2007-09-26
AS9131AW
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.
Standard

BITE GLOSSARY

1986-12-18
CURRENT
ARINC612
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.
Standard

AIRCRAFT AUTONOMOUS DISTRESS TRACKING (ADT)

2019-08-26
CURRENT
ARINC680
This document describes the technical requirements, architectural options, and recommended interface standards to support an Autonomous Distress Tracking (ADT) System intended to meet global regulatory requirements for locating aircraft in distress situations and after an accident. This document is prepared in response to International Civil Aviation Organization (ICAO) and individual Civil Aviation Authorities (CAAs) initiatives.
Standard

TIMELY RECOVERY OF FLIGHT DATA (TRFD)

2021-08-06
CURRENT
ARINC681
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.
Standard

EMBEDDED INTERCHANGE FORMAT FOR OBSTACLE DATABASES

2018-12-21
CURRENT
ARINC815
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.
Standard

EMBEDDED INTERCHANGE FORMAT FOR TERRAIN DATABASES

2018-12-21
CURRENT
ARINC813
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.
Standard

Training Program Guidelines for Deicing/Anti-Icing of Aircraft on Ground-Digital Annex

2019-09-11
CURRENT
ARP5149CDA
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.
Book

Sensors: Advanced Safety (DVD)

2015-04-15
"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.
Video

Fault-Tree Generation for Embedded Software Implementing Dual-Path Checking

2011-11-17
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.
X