Search Results

This specification describes the general connectors, contacts, and backshells in their shape and characteristic for cabin systems for commercial aircrafts. ARINC 600, ARINC 404, and ARINC 801 connector specifications are published as independent standards.

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 establish guidelines that should be observed during initial design, production, and maintenance of aircraft components, and to present short-term and long-term strategies to minimize the costs and impacts associated with decreasing availability of components.

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.

pilots, air traffic controllers, dispatchers, aviation meteorologists

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 SAE Aerospace Information Report (AIR) provides technical information regarding Engine Control Systems Interdependencies strategies and/or functions. This concerns aircraft with multiple power sources: at least two engines, whatever the nature of the power source is (electrical motor or gas turbine engine). Within this document the aircraft stands for fixed-wing aircraft as well as rotorcraft. The term EECS or FADEC is used for the engine electronic control system, whereas the term EEC is used for the electronic unit itself. The scope includes civilian aircraft powered by turbofan, turboprop, turboshaft and electrical engines equipped with electronic engine controls. Military aircraft is taken into consideration, however restricted topics that change the operational behaviors are not discussed.

The E-36 committee is requested to develop a standard or recommended practice for Control System Fault Accommodation to provide guidance on the fault detection and accommodation strategies and robust validation toward certification to FAA Control System regulation 33.28. FAA has written an issue paper on this outlining the risks and vulnerabilities in fault detection/ accommodation based on industry/agency experience over many years; and suggested means of compliance in terms of tests, analyses, simulations. The E-36 is requested to factor in the issue paper and build on the guidance content into an SAE document for reference by the industry. In this endeavor, it is recommended that the SAE standard/ARP consider conventional gas turbine controls as well as emerging architectures such Hybrid and Electric Propulsion Systems.

This Aerospace Recommended Practice will identify the problem with latency in the pilot's instrument control of an aircraft. Recommended evaluation techniques to characterize control problems will be documented.

This SAE Aerospace Information Report (AIR) describes a method for assessing size dependent particle losses in a sampling and measurement system of specified geometry utilizing the non-volatile PM (nvPM) mass and number concentrations measured at the end of the sampling system.1 The penetration functions of the sampling and measurement system may be determined either by measurement or by analytic computational methods. Loss mechanisms including thermophoretic (which has a very weak size dependence) and size dependent losses are considered in this method2 along with the uncertainties due to both measurement error and the assumptions of the method. The results of this system loss assessment allow development of estimated correction factors for nvPM mass and number concentrations to account for the system losses facilitating estimation of the nvPM mass and number at the engine exhaust nozzle exit plane.

Verification of landing gear design strength is accomplished by dynamic and static test programs. This is essentially a verification of the analytical procedures used to design the gear. An industry survey was recently conducted to determine just what analysis and testing are currently being applied to landing gear. Timing in relation to first flight of new aircraft was also questioned. Opinions were solicited from designers of the following categories and/or types of aircraft: a Military - Large Land Based (Bomber) b Military - Small Land Based (Fighter) c Military - Carrier Based (Navy) d Military - Helicopter (Large) e Military - Helicopter (Small-attack) f Commercial - Large (Airliner) g Commercial - Small (Business) h USAF (WPAFB) - Recommendations It is the objective of this AIR to present a summary of these responses. It is hoped that this summary will be useful to designers as a guide and/or check list in establishing criteria for landing gear analysis and test.

The purpose of this document is to establish the requirements for Real-Time Communication Protocols (RTCP). Systems for real-time applications are characterized by the presence of hard deadlines where failure to meet a deadline must be considered a system fault. These requirements have been driven predominantly, but not exclusively, by aerospace type military platforms and commercial aircraft, but are generally applicable to any distributed, real-time, control systems. These requirements are primarily targeted for the Transport and Network Layers of peer to peer protocols, as referenced in the Open System Interconnect Reference Model (2.2.1 and 2.2.2), developed by the International Standards Organization (ISO). These requirements are intended to complement SAE AS4074 (2.1.1) and AS4075 (2.1.2), and future SAE communications standards.

The purpose of this document is to establish the requirements for Real-Time Communication Protocols (RTCP). Systems for real-time applications are characterized by the presence of hard deadlines where failure to meet a deadline must be considered a system fault. These requirements have been driven predominantly, but not exclusively, by aerospace type military platforms and commercial aircraft, but are generally applicable to any distributed, real-time, control systems. These requirements are primarily targeted for the Transport and Network Layers of peer to peer protocols, as referenced in the Open System Interconnect Reference Model (2.2.1 and 2.2.2), developed by the International Standards Organization (ISO). These requirements are intended to complement SAE AS4074 (2.1.1) and AS4075 (2.1.2), and future SAE communications standards.

Manufacturers/designers of all aircraft equipped with a pallet/container capability have provided a means of linking the ground loaders/elevators with the aircraft sill for the smoother transfer of pallets and containers into or out of the aircraft holds. Use of the aircraft attachment points may be used as a means of averting damage to the aircraft door frames and other important parts. Latch-on guarantees fore and aft and vertical alignment of the loader bed with the aircraft doorway, when used in conjunction with the appropriate ground equipment. This SAE Aerospace Information Report (AIR) has been prepared by SAE Subcommittee AGE-2A to present a review of the current range of aircraft attachment points on wide body aircraft and those narrow body aircraft with a ULD cargo capability. Airline operators, who utilized these facilities, have been faced with a growing number of adaptor bars necessary to suit each type of aircraft and door position.