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. Approval as used herein means approval by the engine (and aircraft, if necessary) certifying authority. There are cases where the engine may commence certification activities and no specific aircraft application has been identified. In these cases, the aircraft certification authority should be notified of the EEC''s external software loading capability when the engine''s application is identified. The appropriate documentation can be delivered to the aircraft certifying authority at that time.
After review of the subject material of this ARP, it is found that (1) its current content is extremely limited in scope relative to FADEC architectures in use today and (2) the material which might be added to modernize this document either is already found in other guidance or should be located elsewhere if it is thought to be of value.