FAA / Advisory circular

AC 25.1309-1B

System Design and Analysis

System design, failure conditions, analysis and the evidence supporting a system safety assessment.

Start with the scope.

Guidance for showing compliance with §25.1309. Confirm the applicable amendment level and accepted means for the programme.

The source, within reach.

Search within this AC, jump to a source page, or download the complete saved publication.

Download saved FAA PDF ↓

Find your starting point

What are you looking into?

Go directly to a useful part of the document.

Read the source

The document, within reach.

FAA source document

Printed page 5-4

PDF page 30 of 75

FAA source text, reformatted for reading. Page boundaries and paragraph numbers are retained.

satisfying the objectives of this AC. However, these documents contain material and methods that an applicant may choose to use for performing the safety assessment. The FAA recognizes these methods, when correctly applied, as valid for showing compliance with § 25.1309(b). In addition, SAE ARP 4761 contains tutorial information on applying specific engineering methods (for example, Markov analysis and fault tree analysis) that an applicant may wish to use in whole or in part.

5.3.4 Acceptable Application of Development Assurance Methods.

5.3.4.1 Paragraph 5.3.1.3 of this AC states that any analysis necessary to show compliance with § 25.1309(b) should consider the possibility of errors in requirement, design, and implementation. Errors made during the design and development of systems have traditionally been detected and corrected by exhaustive tests conducted on the system and its components, by direct inspection, and by other direct verification methods capable of completely characterizing the performance of the system. These direct techniques may still be appropriate for simple systems, which perform a limited number of functions and are not highly integrated with other airplane systems.

5.3.4.2 For integrated systems, or systems that perform complex functions, exhaustive testing might be either impossible because all of the system states (within a particular system and within the interfacing systems) cannot be determined, or impractical because of the number of tests that must be accomplished. For these types of systems, the applicant may use development assurance techniques to minimize errors. The rigor of development assurance should be determined by the severity of potential effects on the airplane in case of system malfunctions or loss of functions. Acceptable guidelines for development assurance are described in—

• AC 20-174, which recognizes SAE ARP 4754 for aircraft and systems,

• AC 20-115D, which addresses the software aspects of certification, including the use of RTCA Document DO-178, supplements to DO- 178, and tool qualification, and

• AC 20-152A, which addresses airborne electronic hardware aspects of certification, including the use of RTCA Document DO-254.

5.3.4.3 Development assurance activities should define and identify all requirements, including any derived safety requirements needed to manage the many interactions between the systems. The activities should also validate that these requirements are complete and correct and verify that the system design meets those requirements. The development assurance activities should verify that the design provides for fault containment, so that the integrated systems are shown to be fail-safe.

AC 25.1309-1B · 5-4Open saved PDF here ↗

Saved from the FAA on November 16, 2026. All original pages are retained. Engineering explanations are presented separately below.

Aerospace Consulting / Engineering perspective

Connect the analysis
to the design.

A useful assessment explains why the architecture meets the safety objectives, what assumptions it relies on, and how those assumptions will be verified. We use the guidance to structure the questions and evidence around the actual system.

01 / Define the failure conditions

Begin with functions and effects.

Describe the operating context, affected functions, crew response and interactions with other systems. Carry the resulting safety objectives into the architecture and requirements.

FHA guidance · §6.2 →
02 / Examine the architecture

Make independence and exposure explicit.

Explain monitoring, fault containment and common causes. Examine significant latent failures and the assumptions about how long a failure can remain present.

Latent failures · §5.3.6 →Common cause · §7.4 →
Methods and editions need to be agreed.

Our practice uses ARP4761A and ARP4754B to organise safety assessment and systems development work. This AC refers to ARP 4761 and ARP 4754 without revision letters. Its references alone do not establish acceptance of a particular revision for a programme.

Source edition and reading coverage

75 original pages. 55 pages have reviewed text reflows. Original-first pages retain the source layout, with extracted text available for finding words.

Source SHA-256: 90e625593d472b74ec69fbcefe97649f97794410dbe844f7684b397121ac5a92

This is a dated source copy. Automatic source acquisition is not yet scheduled.

Original FAA PDF ↗

Working through a certification question?

Bring the aircraft, the basis and the issue your team needs to resolve.

Discuss your programme →