ARP4754A is an aerospace recommended practice published by SAE International in 2010, titled ‘Guidelines for Development of Civil Aircraft and Systems,’ which provides a structured framework for the development and safety assessment of complex aircraft systems and functions. It establishes processes for identifying and mitigating failure conditions across the full aircraft system lifecycle, defining Development Assurance Levels (DAL A through E) that calibrate the rigour of development and verification activities to the severity of the failure conditions a system can contribute to. ARP4754A works in conjunction with related standards including ARP4761 for safety assessment and DO-178C for software development.
Content
- The original ARP4754 was published by the Society of Automotive Engineers (SAE) in 1996 to address the growing complexity of integrated modular avionics and fly-by-wire systems that defied prior system-level guidance. A major revision, ARP4754A, was published in December 2010 to align with contemporary development practices, address aircraft-level integration concerns, and better coordinate with DO-178C (released as a companion revision). The ‘A’ revision introduced an explicit aircraft-level safety assessment process and clarified the role of the System Safety Assessment (SSA) versus the Functional Hazard Assessment (FHA).
- ARP4754A’s central technical contribution is the cascading allocation of safety requirements from the aircraft-level Functional Hazard Assessment (FHA) through system-level FHAs to item-level design requirements. At the aircraft level, functions are assessed for their failure condition severity categories (catastrophic through no safety effect), which determines the maximum allowable probability of that failure condition per flight hour—typically 10^-9 for catastrophic failures. The resulting probability and deterministic requirements are then allocated to system components, driving hardware reliability and software assurance level requirements.
- In practice, programmes seeking FAA or EASA type certification must demonstrate compliance with ARP4754A through a planning document (the Plan for Software Aspects of Certification, extended to system planning), followed by evidence generation throughout development. Certification liaison officers from the relevant authority review compliance artefacts at agreed programme milestones. The standard has been adopted for non-aviation safety-critical domains including air traffic management systems and increasingly for autonomous vehicle system certification frameworks drawing on aerospace precedent.
- By 2024–2025, ARP4754A faces extension challenges posed by artificial intelligence and machine-learning-based avionics functions, for which deterministic development assurance evidence is difficult to generate using existing guidance. EASA and FAA have published roadmaps and guidance material on AI in aviation that reference ARP4754A as a baseline framework whilst acknowledging its limitations for learning-enabled system qualification. Working groups within SAE and EUROCAE are developing supplementary guidance specifically addressing machine learning components in safety-critical aviation systems.