This document covers metric studs made from a corrosion and heat resistant, age hardenable iron base alloy of the type identified under the Unified Numbering System as UNS S66286. The following specification designations and their properties are covered:
AS22759 specification covers fluoropolymer-insulated single conductor electrical wires made with tin-coated, silver-coated, or nickel-coated conductors of copper or copper alloy as specified in the applicable detail specification. The fluoropolymer insulation may be polytetrafluoroethylene (PTFE), fluorinated ethylene propylene (FEP), polyvinylidene fluoride (PVF2), ethylene-tetrafluoroethylene copolymer (ETFE), or other Fluoropolymer resin. The fluoropolymer may be used alone or in combination with other insulation materials. These abbreviations shall be used herein. When a wire is referenced herein, it means an insulated conductor (see 7.7).
This document provides recommendations for several aspects of air-breathing gas turbine engine performance modeling using object-oriented programming systems. Nomenclature, application program interface, and user interface are addressed with the emphasis on nomenclature. The Numerical Propulsion System Simulation (NPSS) modeling environment is frequently used in this document as an archetype. Many of the recommendations for standards are derived from NPSS standards. NPSS was chosen because it is an available product. The practices recommended herein may be applied to other object-oriented systems. While this document applies broadly to any gas turbine engine, the great majority of engine performance computer programs have historically been written for aircraft propulsion systems. Aircraft and propulsion terminology and examples appear throughout.
This recommended practice provides a method of characterizing Electrohydrostatic Actuator (EHA)/Electrohydrostatic Module (EHM) duty cycles for the following purposes: a To enable the comparison of the severity of different EHA/EHM applications. This allows the use of previously qualified designs without the need for repeat testing. b To define parameters for endurance-test design of EHAs; e.g., a way of executing a life-equivalent test in a shorter duration by increasing the speed of cycles and/or the level of applied loads.
This document establishes guidelines for a Reliability Assessment Plan (herein also called the Plan), in which Electronic Engine Control manufacturers document their controlled, repeatable processes for assessing reliability of their products. Each Electronic Engine Control manufacturer (the Plan owner) prepares a Plan, which is unique to the Plan owner. This document describes processes that are intended for use in assessing the reliability of Electronic Engine Controls, or subassemblies thereof. The results of such assessments are intended for use as inputs to safety analyses, certification analyses, equipment design decisions, system architecture selection and business decisions such as warranties or maintenance cost guarantees.
Propulsion measurements and thrust methods presented in the current published versions of AIR1703 and AIR5450 place a primary focus on the engine reactionary force (thrust) acting to propel an aircraft in the forward direction. In contrast, this document addresses the use of the engine reactionary force in the opposite direction (reverse thrust) to supplement aircraft deceleration. This document’s application spans commercial and military transport turbofan engine applications for various engine and reverse thrust configurations. The discussion and examples primarily focus on separate flow exhaust turbofan engines. Piston and turboprop variable-pitch propeller blade applications are not covered. Although reverse thrust has been utilized for in-flight deceleration, primarily for short takeoff and landing aircraft and military fighter applications, this application of reverse thrust is only covered in a cursory manner.
The Generic Open Architecture (GOA) Framework family of documents is organized into sets. This is the introductory document for those sets. The GOA family of documents is intended to support the development of affordable systems through the use of open systems concepts. The GOA family of documents is intended to provide input for the systems engineering process. The documents are applicable to the analysis of existing architectures as well as the development of new system architectures using open systems concepts. The domain specific documents catalog appropriate interface standards and, along with the domain independent documents, define a technical architecture for an associated specific domain. In other words, they provide the “rules and regulations” (i.e., the “building codes”) to be used during the systems engineering process when developing a system architecture for use in that domain.
This document is a companion document to SAE AS4893 “Generic Open Architecture (GOA) Framework Standard” and provides an overview and rationale for SAE AS4893. The GOA Framework establishes an architectural framework to assist in the application of open systems interface standards to the design of specific hardware/software systems. The GOA Framework standard is intended for use by both system designers and system implementers in the development of open systems architectures. It is intended that domain specific guidelines be developed to provide clarification for application of the GOA Framework. The Generic Open Architecture (GOA) Framework was initially developed by the SAE to provide a framework which could be used to classify interfaces needed in airborne avionics systems. At the time of the development of the GOA Framework, development of such a classification was considered crucial to the application of open systems standards to military avionics.