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 7-8

PDF page 48 of 75

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

7.8.2 Single failures in combination with operational or environmental conditions leading to catastrophic failure conditions are in general not acceptable. However, single failures do not need to be assumed in combination with operational events or environmental conditions that are extremely remote or that occur outside the normal flight envelope defined in AC 25.671-1. Other cases that are properly justified may be accepted on a case-by-case basis by the certifying authority. In limited cases where a non-redundant system provides protection against an operational or environmental condition (for example, a fire protection system in the cargo compartment comprised of detection and suppression functions) any single failure that results in the loss of the protection function should meet the criteria associated with the major failure condition classification, to ensure adequate system reliability and development assurance.

7.9 Justification of Assumptions, Data Sources, and Analytical Techniques.

7.9.1 Any analysis is only as accurate as the assumptions, data, and analytical techniques it uses. Therefore, to show compliance with the requirements, the underlying assumptions, data, and analytic techniques should be identified and justified to assure that the conclusions of the analysis are valid. Variability may be inherent in elements such as failure modes, failure effects, failure rates, failure probability distribution functions, failure exposure times, failure detection methods, fault independence, limitation of analytical methods, processes, and assumptions. The justification of the assumptions made with respect to the above items should be an integral part of the analysis and summarized in the safety analysis. Assumptions can be validated by using experience with identical or similar systems or components with due allowance made for differences of design, duty cycle, and environment. Where it is not possible to validate a safety analysis in which data or assumptions are critical to the acceptability of the failure condition, extra conservatism should be built into either the analysis or the design. Alternatively, any uncertainty in the data and assumptions should be evaluated to the degree necessary to show that the analysis conclusions are insensitive to that uncertainty.

7.9.2 Where adequate validation data is not available (for example, new or novel systems) and extra conservatism is built into the analysis, then the normal post-certification in-service follow-up may be performed to obtain the data necessary to alleviate any consequence of the extra conservatism. This data may be used, for example, to extend system check intervals.

AC 25.1309-1B · 7-8Open 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 →