SAE ARP4754B / EUROCAE ED-79B — Guidelines for Development of Civil Aircraft and Systems
Issuing body: SAE International (jointly with EUROCAE as ED-79B). Recognised by: FAA via AC 20-174; EASA via AMC 20-174. Invoked through applicant certification plans as the means of compliance with 14 CFR 25.1309 / CS-25.1309. Jurisdiction: International.
Edition note: the catalogue record names ARP4754A (2010). The current edition is ARP4754B / ED-79B, released December 2023 (jointly with ARP4761A). This brief covers the current B revision, which supersedes A; where A-vs-B differences matter they are called out. The manifest maps the record to this brief.
What it is
ARP4754B is the top-level development-assurance standard for civil aircraft and their systems. Where DO-178C governs software and DO-254 governs hardware, ARP4754B governs the aircraft and system level: how functions are allocated, how requirements flow from aircraft to systems to items, and how development rigour is scaled to the severity of failure conditions. It is the process backbone of every modern transport-airplane certification — the document that tells an OEM how to organise a development program so the safety assessment (ARP4761A) and the item-level standards (DO-178C, DO-254) connect into one coherent, auditable whole.
Scope: who it applies to
Aircraft and system developers on any program invoking 25.1309/CS-25.1309-class safety objectives — in practice every transport-category airplane, and increasingly Part 23 airplanes, rotorcraft, and eVTOL programs. Triggers: new aircraft development, major system-level changes, and integration of complex systems (fly-by-wire, integrated modular avionics, electric propulsion).
Key requirements and compliance obligations
- Development process structure. ARP4754B defines the aircraft/system development life cycle: requirements capture and validation, architecture development and allocation, detailed design, implementation, integration, and verification/validation — with planning documents (development plan, validation/verification plans, configuration management and process assurance plans) agreed with the authority early.
- Functional Development Assurance Levels (FDAL) and Item DALs (IDAL). The system safety assessment assigns severity to failure conditions; ARP4754B translates that into development rigour levels applied to functions (FDAL) and then to the hardware/software items implementing them (IDAL). DAL A functions demand the most rigorous process assurance, independence, and verification.
- Requirements management. Aircraft-level requirements flow down to systems, and system requirements to items; validation (are the requirements correct and complete?) is distinguished from verification (does the implementation satisfy them?). Traceability is required throughout.
- Architecture and allocation. Redundancy, partitioning, dissimilarity, and segregation strategies must be justified against the safety objectives — this is where common-cause and common-mode considerations enter.
- Integral processes. Safety assessment (ARP4761A), requirements validation, configuration management, process assurance, and certification liaison run across the whole life cycle.
- B-revision changes (2023): ARP4754B was developed in coordination with ARP4761A — FDAL/IDAL assignment guidance was clarified and aligned, aircraft-level processes made explicit, and the document harmonised with ED-79B. Organisations with ARP4754A-based processes need a gap assessment against B, particularly around assurance-level assignment and validation activities.
Penalties and consequences of non-compliance
Enforced through the certification gate: an inadequate development-assurance process means no compliance finding for 25.1309, which blocks type certification. In-service, systematic development errors discovered later drive airworthiness directives. Falsified process-assurance evidence is certification fraud.
Version / edition status and live changes (verified 2026-09-30)
- Current: ARP4754B / ED-79B (December 2023). Supersedes ARP4754A (2010). FAA AC 20-174 recognises the ARP4754A lineage; practitioners should confirm with their certification office whether AC 20-174 or project-specific issue papers reference the B revision — industry practice is migrating to B, and EASA's AMC 20-174/ED-79B alignment is the European path.
- Flag (verify per program): the exact FAA advisory-circular recognition status of the B revision for new programs was not individually verified for this brief; confirm via the project certification plan.
Related certifications (from the engineering catalogue)
Aerospace flagship/license certifications (A&P, CEng via RAeS) do not test ARP4754B. Development-assurance competence is demonstrated through employer processes and designated roles. Flagged honestly.
Honest flags
- ARP4754B is guidance invoked by certification plans, not a regulation — obligations attach via the certification basis, not the document alone.
Original ETS reference writing, verified against public sources on 2026-09-30. Thin sourcing is flagged inline. Not legal advice — confirm current editions with the issuing body.