FAA / Advisory circular

AC 20-115D

Airborne Software Development Assurance Using EUROCAE ED-12( ) and RTCA DO-178( )

Software development assurance, recognised standards and the treatment of new development and previously approved software.

Start with the scope.

This AC recognises DO-178C/ED-12C, DO-330/ED-215 and the model-based, object-oriented and formal-methods supplements. Apply the relevant provisions to the software and certification context.

The source, within reach.

Search within this AC, jump to a source page, or download the complete saved publication.

Download saved FAA PDF ↓

Read the source

The document, within reach.

FAA source document

Printed page 13

PDF page 13 of 15

Enlarge original ↗

Original FAA page; extracted words support search. Text reflow has not been reviewed.

Original FAA AC 20-115D, PDF page 13
AC 20-115D · 13Open saved PDF here ↗
Extracted text for finding words

This extraction supports search. Read the original page for complete notation and layout.

7/21/17                                                AC 20-115D


        (5) AC 23.1309-1, System Safety Analysis and Assessment for Part 23 Airplanes.

        (6) AC 25.1309-1, System Design and Analysis.

        (7) AC 27-1309, Equipment, Systems, and Installations, (included in AC 27-1,
Certification of Normal Category Rotorcraft).

        (8) AC 29-1309, Equipment, Systems, and Installations, (included in AC 29-2,
Certification of Transport Category Rotorcraft).

        (9) AC 33.28-1, Compliance Criteria for 14 CFR § 33.28, Aircraft Engines, Electrical
and Electronic Engine Control Systems.

       (10) AC 33.28-2, Guidance Material for 14 CFR 33.28, Reciprocating Engines,
Electrical and Electronic Engine Control Systems.

       (11) AC33.28-3, Guidance Material For 14 CFR § 33.28, Engine Control Systems.

       (12) AC 35.23-1, Guidance Material for 14 CFR 35.23, Propeller Control Systems.

    c.  Industry Documents.

        (1) RTCA DO-178, Software Considerations in Airborne Systems and Equipment
Certification, dated January 1982 (no longer in print).

        (2) RTCA DO-178A, Software Considerations in Airborne Systems and Equipment
Certification, dated March 1985 (no longer in print).

        (3) RTCA DO-178B, Software Considerations in Airborne Systems and Equipment
Certification, dated December 1, 1992.

        (4) RTCA DO-178C, Software Considerations in Airborne Systems and Equipment
Certification, dated December 13, 2011.

        (5) RTCA DO-248C, Supporting Information for DO-178C and DO-278A, dated
December 13, 2011.

        (6) RTCA DO-297, Integrated Modular Avionics (IMA) Development Guidance and
Certification Considerations, dated November 8, 2005.

        (7) RTCA DO-330, Software Tool Qualification Considerations, dated December 13,
2011.

        (8) RTCA DO-331, Model-Based Development and Verification Supplement to DO-
178C and DO-278A, dated December 13, 2011.

        (9) RTCA DO-332, Object-Oriented Technology and Related Techniques Supplement to
DO-178C and DO-278A, dated December 13, 2011.



                                  13

Saved from the FAA on November 17, 2026. All original pages are retained. Engineering explanations are presented separately below.

Aerospace Consulting / Engineering perspective

Keep software assurance connected to the system.

Make the software level, allocated requirements, interface assumptions and verification responsibilities explicit. Plan the evidence and review points early, and trace changes back to the system safety and certification assumptions.

Explore our development assurance approach →
Source edition and reading coverage

15 original pages. 0 pages have reviewed text reflows. Original-first pages retain the source layout, with extracted text available for finding words.

Source SHA-256: 5597a1af49c872a1a843c05601742ddcc8e8a190642f31e3cb9ce8e0dc63d91e

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 →