Search Results

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 SAE Aerospace Recommended Practice (ARP) provides guidelines for the format and content of documents defining the interface between electronic propulsion control systems and aircraft systems. The scope includes civilian aircraft powered by turbofan, turboprop, and turboshaft engines equipped with electronic engine controls.

This SAE Aerospace Information Report (AIR) provides an overview of fire and overheat protection approaches that have been utilized for engine electronic units. While the electronic engine control (EEC) is the engine electronic unit specifically addressed in this document, the approaches presented can extend to any engine electronic unit, including monitoring units and other electronic based engine components.

This SAE Aerospace Information Report (AIR) enumerates areas of concern which need to be addressed when the aircraft propulsion control system functions are distributed. Distributed items may include electronic control sensors, electrical or hydraulic power sources, computer hardware and software, etc. This report identifies many factors which should be considered to determine the best system architecture for any given application.

This SAE Aerospace Recommended Practice (ARP) provides guidance and interpretation on how to apply the objectives and activities in ARP4754A, “Guidelines for Development of Civil Aircraft and Systems”, to propulsion systems with electronic engine control. As the ARP4754A was developed and written more generally at the aircraft level, guidance will be provided to allocate ARP4754A objectives and activities to each side of the aircraft/engine interface. Using this guidance, certification applicants (aircraft and engine manufacturers) will be able to make proposals to coordinate their activities with their respective authority based on this allocation with the objective of distributing efficiently the compliance demonstration efforts between engine and aircraft certification and of avoiding unnecessary duplication of work.

The purpose of this document is to provide reference material for establishing compatibility of electronic gas turbine engine control systems and associated components with the electromagnetic environment and achieving compliance with associated airworthiness requirements.

The purpose of this document is to provide reference material for establishing compatibility of electronic gas turbine engine control systems and associated components with the electromagnetic environment and achieving compliance with associated airworthiness requirements.

The purpose of this document is to provide reference material for establishing compatibility of electronic gas turbine engine control systems and associated components with the electromagnetic environment and achieving compliance with associated airworthiness requirements.

This document is intended for use by manufacturers of aircraft, engines and Electronic Engine Controls [EECs] as a component change process and evaluation guideline. Its purpose is to provide an effective means of managing the modification of electronic hardware. The process defined in this document is based upon: an understanding of the electronic component market evolution, e.g., obsolescence; lessons learned from the effects caused by the introduction of electrical component changes in a service fleet environment; industry best practice; and an understanding of the applicable regulations.

This document is intended for use by manufacturers of aircraft, engines and Electronic Engine Controls [EECs] as a component change process and evaluation guideline. Its purpose is to provide an effective means of managing the modification of electronic hardware. The process defined in this document is based upon: an understanding of the electronic component market evolution, e.g., obsolescence; lessons learned from the effects caused by the introduction of electrical component changes in a service fleet environment; industry best practice; and an understanding of the applicable regulations.

This paper presents guidelines for development of a procedure for external software loading of an electronic engine control(EEC)for a commercial application, on-wing or in a qualified service shop. This paper makes the following assumptions: a. The EEC is designed to accept external software loading. b. The EEC is certified as part of an engine. c. The support equipment is qualified in accordance with procedures set forth by the engine (and aircraft, if necessary) certifying authority if the EEC cannot detect an integrity violation of the loaded program. The software to be loaded has been approved by the engine and aircraft certifying authorities. One or more configurations of EEC hardware has been identified for each version of software which is to be loaded in the EEC. It is appropriate to use these guidelines in the initial development phase, although the certification issues would not be applicable.

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.

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.

This SAE Aerospace Recommended Practice (ARP) provides methodologies and approaches which have been used for conducting and documenting the analyses associated with the application of Time Limited Dispatch (TLD) to the thrust control reliability of Full Authority Digital Engine Control (FADEC) systems. The TLD concept is one wherein a fault-tolerant system is allowed to operate for a predetermined length of time with faults present in the redundant elements of the system, before repairs are required. This document includes the background of the development of TLD, the structure of TLD that was developed and implemented on present generation commercial transports, and the analysis methods used to validate the application of TLD on present day FADEC equipped aircraft.

This SAE Aerospace Recommended Practice (ARP) provides methodologies and approaches which have been used for conducting and documenting the analyses associated with the application of Time Limited Dispatch (TLD) to the thrust control reliability of Full Authority Digital Electronic Control (FADEC) systems. The TLD concept is one wherein a redundant system is allowed to operate for a predetermined length of time with faults present in the redundant elements of the system, before repairs are required. This document includes the background of the development of TLD, the structure of TLD that was developed and implemented on present generation commercial transports, and the analysis methods used to validate the application of TLD on present day FADEC equipped aircraft.

This SAE Aerospace Recommended Practice (ARP) provides methodologies and approaches which have been used for conducting and documenting the analyses associated with the application of Time Limited Dispatch (TLD) to the thrust control reliability of Full Authority Digital Electronic Control (FADEC) systems. The TLD concept is one wherein a redundant system is allowed to operate for a predetermined length of time with faults present in the redundant elements of the system, before repairs are required. This document includes the background of the development of TLD, the structure of TLD that was developed and implemented on present generation commercial transports, and the analysis methods used to validate the application of TLD on present day FADEC equipped aircraft.

This SAE Aerospace Recommended Practice (ARP) provides methodologies and approaches which have been used for conducting and documenting the analyses associated with the application of Time Limited Dispatch (TLD) to the thrust control reliability of Full Authority Digital Electronic Control (FADEC) systems. The TLD concept is one wherein a redundant system is allowed to operate for a predetermined length of time with faults present in the redundant elements of the system, before repairs are required. This document includes the background of the development of TLD, the structure of TLD that was developed and implemented on present generation commercial transports, and the analysis methods used to validate the application of TLD on present day FADEC equipped aircraft.

The purpose of this SAE Aerospace Information Report (AIR) is to provide guidance for aircraft engine and propeller systems (hereafter referred to as propulsion systems) certification for cybersecurity. Compliance for cybersecurity requires that the engine control, propeller control, monitoring system, and all auxiliary equipment systems and networks associated with the propulsion system (such as nacelle systems, overspeed governors, and thrust reversers) be protected from intentional unauthorized electronic interactions (IUEI) that may result in an adverse effect on the safety of the propulsion system or the airplane. This involves identification of security risks, their mitigation, verification of protections, and their maintenance in service. This document is intended to serve as suitable guidance for propulsion system manufacturers and applicants for propulsion system type certification.

This SAE Aerospace Information Report (AIR) provides guidelines to document the functional and physical interface requirements for the electrical systems (including an EPCS and its components) between a given propulsion system and the aircraft on which the system is installed and the functionality pertinent to each interface. The scope includes civilian aircraft powered by turbofan, turboprop, and turboshaft engines equipped with electronic engine controls.