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

PDF page 37 of 75

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

and thermal runaway or excessive temperatures that could damage adjacent structures or systems.

Note: Identify any necessary mitigation means including, but not limited to, containment of resultant effects; pressure and temperature relief including venting provisions, if present; and indication or fault annunciation, where applicable. The testing necessary to verify the mitigation effectiveness is equally significant and should also be determined.

6.2 Identification of Failure Conditions Using a Functional Hazard Assessment.

6.2.1 Before an applicant proceeds with a detailed safety assessment, an FHA of the airplane and system functions to determine the need for, and scope of, subsequent analysis should be prepared. This assessment may be conducted using service experience; engineering and operational judgment; and/or a top-down deductive qualitative examination of each function. An FHA is a systematic, comprehensive examination of airplane and system functions to identify potential no safety effect, minor, major, hazardous, and catastrophic failure conditions that may arise as a result of malfunctions or failures to function as intended. The assessment should take into consideration normal system responses to unusual and abnormal external factors. The assessment involves the operational vulnerabilities of systems rather than a detailed analysis of the actual implementation.

6.2.2 Each system function should be examined with respect to the other functions performed by the system, because the loss or malfunction of multiple functions performed by the system could result in a more severe failure condition than the failure of a single function. In addition, each system function should be examined with respect to functions performed by other airplane systems because the loss or malfunction of different but related functions, provided by separate systems, may affect the severity of failure conditions postulated for a particular system.

6.2.3 The FHA should be performed early in the design of the project and updated as necessary as the design develops. It is used to define the airplane-level or system-level safety objectives that must be considered in the proposed airplane or system architectures. Some systems may need only a simple review of the system design to determine the hazard classification. The FHA should also be used to determine the function development assurance levels. An FHA requires experienced engineering judgment to ensure completeness of failure condition identification, and early coordination between the applicant and certification authority.

6.2.4 Depending on the relationship between functions and the systems that perform them, different approaches to an FHA may be taken. Where there is a clear correlation between functions and systems, and where interactions are relatively simple, it may be feasible to conduct separate FHAs for each system, provided that any interface aspects are properly considered and are easily understood. However, where systems and functional relationships are complex or integrated, a top-down approach, from an airplane-level perspective, should be considered when planning and conducting FHAs.

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