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

PDF page 39 of 75

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

6.3.3 The applicant should classify the severity of each effect as no safety effect, minor, major, hazardous, or catastrophic. These terms are defined in chapter 3 of this AC (and in § 25.4).

6.3.3.1 The classification of failure conditions does not depend on whether a system or function is the subject of a specific requirement or regulation. Some required systems, such as transponders, position lights, and public address systems, may have the potential for only minor failure conditions. Conversely, other systems that are not required, such as autoflight systems, may have the potential for major, hazardous, or catastrophic failure conditions.

6.3.3.2 Regardless of the types of assessment used, the classification of failure conditions should always be accomplished with consideration of all relevant factors, internal and external; for example, system, crew, performance, operational, and environmental. It is particularly important to consider factors that would alleviate or intensify the severity of a failure condition. Where flight duration, flight phase, or maximum length diversion time can adversely affect the FHA outcome, they must be considered as intensifying factors. Other intensifying factors include conditions (not related to the failure, such as weather or adverse operational or environmental conditions), which reduce the capability of the airplane, or the ability of the flightcrew to cope with a failure condition. An example of an alleviating factor is the continued performance of identical or operationally similar functions by other systems not affected by the failure condition. Another example of an alleviating factor is the flightcrew’s ability to recognize the failure condition and take action to temper its effects. (Note that such flightcrew action can in some cases be used to alleviate a failure condition, but it should not be used in lieu of appropriate system design, integrity, and availability requirements.) Whenever this is taken into account, attention to the detection means should be given to ensure the flightcrew’s ability (including physical and timeliness) to detect and take corrective action is sufficient. To correlate with the flightcrew’s annunciation requirements in § 25.1309(c), consider the case of the flightcrew taking action and also the effects if they do not act or their response is delayed. If their inaction or delayed response results in a severe effect, it may be considered an unsafe system operating condition that carries certain considerations for flightcrew annunciations and evaluation of flightcrew responses. If flightcrew action is used to alleviate the effects of a failure condition, the associated information provided to the flightcrew should comply with § 25.1309(c). See paragraph 5.4 of this AC for more detailed guidance on those considerations. Combinations of intensifying or alleviating factors only need to be considered if they are anticipated to occur together.

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