Refine Your Search

Search Results

Viewing 1 to 3 of 3
Standard

Electronic Engine Control Hardware Change Management

2021-06-22
CURRENT
ARP6109A
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.
Standard

Electronic Engine Control Hardware Change Management

2014-02-21
HISTORICAL
ARP6109
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.
Standard

External Software Loading of Electronic Engine Controls

2012-09-25
CURRENT
ARP4714A
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. d The software to be loaded has been approved by the engine and aircraft certifying authorities. e 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.
X