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

PDF page 23 of 75

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

3.3 Quantitative Probability Terms.

3.3.1 When using quantitative analyses to help determine compliance with § 25.1309(b), the following descriptions of the probability terms used in this requirement and AC have become commonly accepted as aids to engineering judgment. They are expressed in terms of acceptable ranges for the average probability per flight hour. Those probability terms and ranges are as follows:

3.3.1.1 Probable Failure Condition. A failure condition having an average probability per flight hour on the order of 1 x 10-3 or less, but greater than the order of 1 x 10-5.

3.3.1.2 Remote Failure Condition. A failure condition having an average probability per flight hour on the order of 1 x 10-5 or less, but greater than the order of 1 x 10-7.

3.3.1.3 Extremely Remote Failure Condition. A failure condition having an average probability per flight hour on the order of 1 x 10-7 or less, but greater than the order of 1 x 10-9.

3.3.1.4 Extremely Improbable Failure Condition. A failure condition having an average probability per flight hour on the order of 1 x 10-9 or less.

In a quantitative assessment of a remote failure condition a factor of two could be considered as ‘on the order of’ to show compliance. For an extremely remote or extremely improbable failure condition, a factor of three could be considered as ‘on the order of’ to show compliance. Note that at the low end of the probability value, there may be many factors in the analysis methods that influence the top undesired event probability calculations, therefore a higher factor may be acceptable on a case-by-case basis. (See paragraph 7.6.4 of this AC.)

Note: When using quantitative analysis to show compliance with § 25.1309(b), a calculated probability lower than the specified range in this section is considered as compliant.

3.3.2 The above numerical values associated with the probabilistic terms in § 25.1309(b) are guidelines for acceptable risk when applicants use quantitative probability methods of analysis to examine the effect of system failures. A design that meets these guidelines provides some, but not necessarily sufficient, evidence to support a finding by the FAA as to whether the design complies with the rule.

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