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 6-1

PDF page 36 of 75

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

CHAPTER 6. IDENTIFICATION OF FAILURE CONDITIONS AND CONSIDERATIONS WHEN ASSESSING THEIR EFFECTS

6.1 Identification of Failure Conditions. In order to identify the failure conditions regulated by § 25.1309, applicants should consider the potential effects of failures on the airplane and occupants. The applicant may also need to consider failure conditions that could present threats to persons on the ground, such as ground crew, or adjacent to the airplane during ground operations. Threats include electric shock threats to mechanics, atmospheric events, unwanted door or thrust reverser movement, and other similar situations. These should be considered from the following perspectives:

6.1.1 By Considering Failures of Functions at the Airplane Level. Failure conditions identified at this level are not dependent on the way the functions are implemented and the systems’ architectures.

6.1.2 By Considering Failures of Functions at the System Level. These failure conditions are identified through examination of the way the functions are implemented and the systems’ architectures. Part of this examination is a systematic method, such as failure mode and effects analysis (FMEA), to look for failures within the systems’ architectures that could result in their loss or partial loss, or malfunctions that are not limited by the failure condition evaluations (for example, to discover system behaviors that have unintended safety consequences when those systems fail).

Note: The analysis of complex, highly integrated systems, in particular, should be conducted in a methodical and structured manner to ensure all significant failure conditions that arise from multiple failures and combinations of failure conditions are properly identified and accounted for. The relevant combinations of failures and failure conditions should be determined by the whole safety assessment process that encompasses the airplane and system-level functional hazard assessments (FHAs), Particular Risk (PRA), Zonal Safety (ZSA), and Common Mode (CMA) analyses. The overall effect on the airplane due to a combination of individual system failure conditions occurring as a result of a common or cascade failure may be more severe than the effect of each individual system failure. For example, failure conditions classified individually as minor or major may have hazardous or catastrophic effects at the airplane level when considered in combination.

6.1.3 By Considering Failures at the Equipment Level. These failures may not affect a system’s functionality, but they could compromise safe operations or injure persons. These may include individual equipment with intrinsic hazards such as energy supply devices, chemical storage containers, or pressure storage bottles that are part of a system. The analysis should address the equipment’s normal operating conditions and failure conditions that could endanger the airplane or its occupants. Examples of intrinsic hazards to be evaluated include, but are not limited to, fires; explosions; release of toxic gases or fluids corrosive to surrounding structures;

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