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

PDF page 57 of 75

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

APPENDIX C. OVERVIEW OF THE SAFETY ASSESSMENT PROCESS

C.1 Purpose. In showing compliance with § 25.1309(b), the applicant should address the considerations covered in this AC in a methodical and systematic manner, which ensures that the process and its findings are visible and readily assimilated into compliance-showing documents. The FAA has provided this appendix primarily for applicants who are unfamiliar with the various methods and procedures typically used in the industry to conduct safety assessments. This guide and figures C-1 and C-2 are not certification checklists, and they do not include all the information provided in this AC. There is no necessity for an applicant to use them or for the FAA to accept them, in whole or in part, to show compliance with any regulation. The sole purpose of this guidance is to assist applicants by illustrating a systematic approach to safety assessments, to enhance understanding and communication by summarizing some of the information provided in this AC, and to provide some suggestions on documentation. You can find more detailed guidance in SAE ARP 4761. SAE ARP 4754 includes additional guidance on how the safety assessment process relates to the system development process.

C.2 Safety Assessment Process.

C.2.1 Define the system and its interfaces and identify the functions that the system is to perform. The safety assessment process may identify additional safety requirements for the functions during the system development life cycle.

C.2.2 Determine whether the system is complex, similar to systems used on other airplanes, or conventional. Where multiple systems and functions should be evaluated, consider the relationships between multiple safety assessments.

C.2.3 Identify and classify failure conditions. All relevant applicant engineering organizations, such as systems, structures, propulsion, and flight test, should be involved in this process. This identification and classification may be done by conducting an FHA, which is usually based on one of the following methods, as appropriate:

C.2.3.1 If the system is not complex and its relevant attributes are similar to those of systems used on other airplanes, the identification and classification may be derived from design and installation appraisals and the service experience of the comparable, previously approved systems.

C.2.3.2 If the system is complex, it is necessary to postulate systematically the effects on the safety of the airplane and its occupants resulting from any possible failures, considered both individually and in combination with other failures or events.

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