From Wikipedia, the free encyclopedia
Guidelines For Development Of Civil Aircraft and Systems
Latest versionA
December 2010 (2010-12)
OrganizationSAE International
DomainAviation Safety

ARP4754, Aerospace Recommended Practice (ARP) ARP4754A (Guidelines For Development Of Civil Aircraft and Systems), is a guideline from SAE International, dealing with the development processes which support certification of Aircraft systems, addressing "the complete aircraft development cycle, from systems requirements through systems verification."[1] Revision A was released in December 2010. It was recognized by the FAA in AC 20-174 published November 2011.[2] EUROCAE jointly issues the document as ED–79.

Objectives of the document[edit]

The Aerospace Recommended Practice (ARP) is a guideline for development of civil aircraft and systems with an emphasis on safety aspects. Revision A is a substantial rewrite of the document which describes the safety process as a part of an Integrated Development Process. A significant new section is devoted to the process of determining Development Assurance Level (DAL) which determines the rigor of complex hardware and software development and verification activities.

It is intended to be used in conjunction with SAE ARP4761 (still under revision in December 2013) and is supported by other aviation standards such as RTCA DO-178C/DO-178B and DO-254.

This guideline addresses Functional Safety and design assurance processes. DAL allocation pertaining to functional failure conditions and hazard severity are assigned to help mitigate risks. Functional Hazard Analyses / Assessments are central to determining hazards and assigning DAL, in addition to requirements based testing and other verification methods. This guideline concerns itself with Physical (item) DAL and Functional (software/systems integration behavior) DAL and the Safety aspects of systems for the whole life-cycle for systems that implement aircraft functions.


ARP4754 was defined in the context of aircraft certification, in particular Part 25 Sections 1301 and 1309 of harmonized civil aviation regulations for transport category airplanes. These are found in the U.S. FAA Federal Aviation Regulations (FAR) at 14 CFR 25.1309 and the corresponding European JAA Joint Aviation Requirements (JAR), which have been replaced by EASA certification standards. FAA Advisory Circular AC 25.1309-1A, System Design and Analysis, explained certification methodology for Part 25 Section 1309.[3]

In May 1996, the FAA Aviation Rulemaking Advisory Committee (ARAC) was tasked with a review of harmonized FAR/JAR 25.1309, AC 1309-1A, and related documents, and to consider revision to AC 1309-1A incorporating recent practice, increasing complex integration between aircraft functions and the systems that implement them,[4] and the implications of new technology. This task was published in the Federal Register at 61 FR 26246-26247 (1996-05-24). The focus was to be on safety assessment and fault-tolerant critical systems.

In a parallel effort, SAE published ARP4754 in November 1996. In 2002 ARAC submitted to the FAA a draft Notice of Proposed Rulemaking (NPRM) and draft revision AC 1309-1B (the draft ARSENAL version) recognizing the role of ARP4754 in complex system certification.[5] This draft remains unreleased, but ARP4754 became broadly recognized as an appropriate standard for aircraft system development and certification. The corresponding EASA Acceptable Means of Compliance AMC 25.1309 (included as a section of CS-25) does recognize ARP4754/ED–79.

The FAA and EASA have both subsequently recognized ARP4754/ED–79 as valid for certification of other aircraft categories, and for specific systems such as avionic databuses.

ARP4754A and ED79A were released by SAE and EUROCAE in December 2010. The document title has changed to Guidelines For Development Of Civil Aircraft and Systems. ARP4754A recognizes AMC 25.1309 (published in 2003) and AC 25.1309-1B-Arsenal draft. This revision expands the design assurance concept for application at the aircraft and system level and standardizes on the use of the term development assurance. As a consequence, Functional Development Assurance Level (FDAL) is introduced for aircraft and systems concerns and the term Design Assurance Level has been renamed Item Development Assurance Level (IDAL).[6] Furthermore, the addition of definitions for Error, Failure, and Failure Condition are acknowledge as derived from AMC 25.1309.[7] The qualitative and quantitative classification of failure conditions by severity and probability now used by ARP4754A[8] and ARP4761[9] are defined in AMC 25.1309/AC 25.1309–1B-Arsenal draft.

See also[edit]


  1. ^ Bill Potter. Complying with DO-178C and DO-331 using Model-Based Design (PDF). SAE 2012 Aerospace Electronics and Avionics Systems Conference (12AEAS). MathWorks, Inc. Retrieved 2019-02-13.
  2. ^ S–18 (2010). Guidelines for Development of Civil Aircraft and Systems. SAE International. ARP4754A.{{cite book}}: CS1 maint: multiple names: authors list (link) CS1 maint: numeric names: authors list (link)
  3. ^ ANM-110 (1988). System Design and Analysis (PDF). Federal Aviation Administration. Advisory Circular AC 25.1309-1A. Retrieved 2011-02-20.{{cite book}}: CS1 maint: numeric names: authors list (link)
  4. ^ ARP4754A, p. 7
  5. ^ ARAC Systems Design and Analysis Harmonization Working Group (2002). Task 2 – System Design and Analysis Harmonization and Technology Update (PDF). Federal Aviation Administration. Archived from the original (PDF) on 2006-10-05. Retrieved 2011-02-20.
  6. ^ ARP4754A, pp. 7-8
  7. ^ ARP4754A, pp. 11
  8. ^ ARP4754A, p. 34
  9. ^ S–18 (1996). Guidelines and methods for conducting the safety assessment process on civil airborne systems and equipment. Society of Automotive Engineers. p. 9. ARP4761.{{cite book}}: CS1 maint: multiple names: authors list (link) CS1 maint: numeric names: authors list (link)

External links[edit]