• DO-178C, Software Considerations in Airborne Systems and Equipment Certification
• DO-224C, Signal-In-Space Minimum Aviation System Performance Standards (MASPS) for Advanced VHF Digital Data Communications Including Compatibility with Digital Voice Techniques
• DO-248C, Supporting Information for DO-178C and DO-278A
• Corrigendum 1 to DO-260B, Minimum Operational Performance Standards for 1090 MHz Extended Squitter Automatic Dependent Surveillance – Broadcast (ADS-B) and Traffic Information Services – Broadcast (TIS-B)
• DO-260B with Corrigendum 1, Minimum Operational Performance Standards for 1090 MHz Extended Squitter Automatic Dependent Surveillance – Broadcast (ADS-B) and Traffic Information Services – Broadcast (TIS-B)
• DO-278A, Software Integrity Assurance Considerations for Communication, Navigation, Surveillance and Air Traffic Management (CNS/ATM) Systems
• Corrigendum 1 to DO-282B, Minimum Operational Performance Standards for Universal Access Transceiver (UAT) Automatic Dependent Surveillance – Broadcast (ADS-B)
• DO-282B with Corrigendum 1, Minimum Operational Performance Standards for Universal Access Transceiver (UAT) Automatic Dependent Surveillance – Broadcast (ADS-B)
• DO-317A, Minimum Operational Performance Standards (MOPS) for Aircraft Surveillance Applications (ASA) System
• Supplement to DO-317A, Minimum Operational Performance Standards (MOPS) for Aircraft Surveillance Applications (ASA) System
• DO-330, Software Tool Qualification Considerations
• DO-331, Model-Based Development and Verification Supplement to DO-178C and DO-278A
• DO-332, Object-Oriented Technology and Related Techniques Supplement to DO-178C and DO-278A
• DO-333, Formal Methods Supplement to DO-178C and DO-278A

DO-178C, Software Considerations in Airborne Systems and Equipment Certification

This document provides recommendations for the production of software for airborne systems and equipment that performs its intended function with a level of confidence in safety that complies with airworthiness requirements. Compliance with the objectives of DO-178C is the primary means of obtaining approval of software used in civil aviation products.

Order Now

DO-224C, Signal-in-Space Minimum Aviation System Performance Standards (MASPS) for Advanced VHF Digital Data Communications Including Compatibility with Digital Voice Techniques

This document provides the final planned version of the VDL Mode 2 and Mode 3 MASPS consolidated from previous documents. It is synchronized with ICAO SARPS and Technical Manuals for VDL Modes 2 and 3. Future updates to DO-281A, MOPS for VDL Mode 2, and DO-271C, MOPS for VDL Mode 3, will be synchronized with DO-224C.

DO-224C provides VDL Mode 2 refinements for operating/system parameters, technical descriptions and other considerations to be taken into account when determining compliance. The key improvements include separating frequency selection list (FSL) into airborne-FSL and ground-FSL, refining FSL-based handoff procedures, introducing “ground” bit usage in the Aviation VHF Link Control (AVLC) specific options parameter, refining frequency recovery and missing parameter handling. No refinements were made to VDL Mode 3.

Order Now

DO-248C, Supporting Information for DO-178C and DO-278A

Order Now

Corrigendum 1, DO-260B, Minimum Operational Performance Standards for 1090 MHz Extended Squitter Automatic Dependent Surveillance – Broadcast (ADS-B) and Traffic Information Services – Broadcast (TIS-B)

This document is a supplement to DO-260B. It contains corrections to typographical errors, corrections to test procedures and notes added to clarify existing text. These changes represent feedback from industry use of the published version of DO-260B. This supplement does not alter any existing requirements and does not affect the compliance of any equipment designed to meet the original published document.

Order Now

DO-260B, Minimum Operational Performance Standards for 1090 MHz Extended Squitter Automatic Dependent Surveillance – Broadcast (ADS-B) and Traffic Information Services – Broadcast (TIS-B)

This document contains Minimum Operational Performance Standards (MOPS) for airborne equipment for Automatic Dependent Surveillance-Broadcast (ADS-B) and Traffic Information Service- Broadcast (TIS-B) utilizing 1090 MHz Mode-S Extended Squitter (1090ES). Compliance with these standards by manufacturers, installers and users is recommended as one means of assuring that the equipment will satisfactorily perform its intended functions under conditions encountered in routine aeronautical operations.

This revision supersedes DO-260A and incorporates the earlier Changes 1 and 2. The document was developed in parallel with DO-282B. FAA Technical Standard Order (TSO) C-166b references this document.

RTCA's List of Available Documents provides more detail of the changes from the previous version of the document.

The document is available as an electronic download.

Order Now

DO-278A, Software Integrity Assurance Considerations for Communication, Navigation, Surveillance and Air Traffic Management (CNS/ATM) Systems

This document provides guidelines for the assurance of software contained in non-airborne CNS/ATM systems and provides recommendations for the production of that software commensurate with a level of confidence in safety. DO-278A defines a set of objec¬tives recommended to establish assurance that the developed CNS/ATM software has the integrity needed for use in a safety-related application.

Order Now

Corrigendum 1, DO-282B, Minimum Operational Performance Standards for Universal Access Transceiver (UAT) Automatic Dependent Surveillance - Broadcast

This document is a supplement to DO-282B. It contains corrections to typographical errors, corrections to test procedures and notes added to clarify existing text. These changes represent feedback from industry use of the published version of DO-282B. This supplement does not alter any existing requirements and does not affect the compliance of any equipment designed to meet the original published document. (Note: Those that have previously purchased DO-282B, issued December 2, 2009, need only this Corrigendum to have complete information.)

Order Now

DO-282B with Corrigendum 1, Minimum Operational Performance Standards for Universal Access Transceiver (UAT) Automatic Dependent Surveillance - Broadcast

This document is DO-282B issued December 2, 2009 with Corrigendum 1 (described above) issued December 13, 2011 included as Appendix T. The Corrigendum is also incorporated throughout the document.

The document contains Minimum Operational Performance Standards for airborne equipment to support Automatic Dependent Surveillance – Broadcast utilizing the Universal Access Transceiver (UAT). UAT is a multi-purpose aeronautical data link intended to support not only ADS-B, but also Flight Information Service – Broadcast (FIS-B), Traffic Information Service – Broadcast (TIS-B) and, if required in the future, supplementary ranging and positioning capabilities.

The document was developed in parallel with DO-260B.

Order Now

DO-317A, Minimum Operational Performance Standards (MOPS) for Aircraft Surveillance Applications (ASA) System

This document contains the recommended requirements for the processing and display of traffic Ownship information for use by the flight crew in processing airborne applications. The document considers functional requirements consisting of Airborne Surveillance and Separation Assurance Processing (ASSAP) and Cockpit Display of Traffic Information (CDTI) as described in DO-289, Minimum Aviation System Performance Standards (MASPS) for Aircraft Surveillance Applications (ASA). It includes requirements to support the initial five applications included in DO-289 - Enhanced Visual Acquisition (EVAcq), Conflict Detection (CD), Airport Surface Situational Awareness (ASSA), Final Approach and Runway Occupancy Awareness (FAROA) and Enhanced Visual Approach (EVApp). Operational performance standards for functions or components that exceed the stated minimum requirements are identified as optional features.

In order to provide more complete traffic situational awareness, the Traffic Alert and Collision Avoidance System (TCAS) display should be integrated with the CDTI on aircraft equipped with TCAS. This document provides requirements and guidance for integration of TCAS with ASAS.

DO-317A incorporates the following “prime” differences from DO-317:

• Incorporation of Airborne Surveillance Application requirements for the situational awareness applications ATSA-AIRB (ED-164/DO-319), ATSA-SURF (ED-165/DO-322), ATSA-VSA (ED-160/DO-314) and ATSA-ITP (ED-159/DO-312), jointly developed and published by EUROCAE WG-51 and RTCA SC-186 within the framework of the ADS-B Requirements Focus Group (RFG). This includes the related ADS-B data quality requirements for traffic and Ownship (including relevant qualification schemes thereof) and ASA system latency requirements. December 2011 RTCA List of Available Documents Page 23 of 118
• Harmonization of application transition requirements, in particular between the surface application and the airborne applications.
• Use of the 1090 MHz Extended Squitter MOPS (ED-102A/DO-260B) as the ADS-B data transmission and receipt baseline, in line with the European and US airspace regulations with respect to ADS-B Out.
• Refinement of expected regulatory ASA system design assurance requirements and the related definition of equipment classes.
• Integration of relevant VDL Mode 4 provisions.
• Maintenance of the RTCA-defined EVAcq application as the only application originally contained in DO-317, defining the minimum set of requirements ASA systems must meet for a minimum stand-alone traffic situation awareness application in smaller aircraft.
• Provision of additional updates, including:\
  • Traffic display prioritization;
  • Support of TIS-B and ADS-R services (as defined by FAA);
  • Data age requirements;
  • Test scenarios and procedures.

Order Now

Supplement to DO-317A, Minimum Operational Performance Standards (MOPS) for Aircraft Surveillance Applications (ASA) System

This supplement to DO-317A is a single zip file archive that contains test data scenarios described in Sections 2.5.7 through 2.5.9 and MATLAB implementations of sample algorithms for an airborne surveillance processor and In-Trail Procedure (ITP) application. Appendix I describes the test data generation processes. The data files for any particular scenario reflect all appropriate surveillance sources (e.g., ADS-B, ADS-R, TIS-B, and TCAS) and are provided separately for 1090ES, UAT, and VDL4 installations where necessary due to the differences in state vector construction for each. Test data files are provided in Comma Separated Value (CSV) format and content represents input to end user or manufacturer systems. The zip file archive will extract into two subdirectories: “ASSAP test data” which includes Application processing test data and Surveillance processing test data. Sample implementations include ASA sample 1090ES implementation and ITP sample implementation.

Order Now

DO-330, Software Tool Qualification Considerations

Software tools are widely used in multiple domains to assist in developing, verifying and controlling other software. In the context of this document a tool is a computer program or a functional part thereof, used to help develop, transform, test, analyze, produce or modify another program, its data or its documentation. Examples are automated code generators, compilers, test tools and modification management tools. This document explains the process and objectives for qualifying tools.

This document provides software tool qualification guidance. Additionally, clarification material is provided in the form of Frequently Asked Questions (FAQs). The document was developed for the following reasons:

• Tools are different from the software using the tools and form a unique domain; therefore, tool-specific guidance for both tool developers and tool users is needed.
• Tools are often developed by teams other than those who use the tools to develop software. These tool development teams frequently do not have software guidance background (examples of guidance include DO-178C or DO-278A). This tool-specific document benefits tool development teams and helps them avoid confusion and misinterpretation.
• It provides guidance for airborne and ground-based software. It may also be used by other domains, such as automotive, space, systems, electronic hardware, aeronautical databases and safety assessment processes.

Order Now

DO-331, Model-Based Development and Verification Supplement to DO-178C and DO-278A DO-278A

This supplement contains modifications and additions to DO-178C and DO-278A objectives, activities, explanatory text and software life cycle data that should be addressed when model-based development and verification are used as part of the software life cycle. This includes the artifacts that would be expressed using models and the verification evidence that could be derived from them. Therefore, this supplement also applies to the models developed in the system process that define software requirements or software architecture.

A model is an abstract representation of a set of software aspects of a system that is used to support the software development process or the software verification process. This supplement addresses model(s) that have the following characteristics:

• The model is completely described using an explicitly identified modeling notation. The modeling notation may be graphical and/or textual.
• The model contains software requirements and/or software architecture definition. December 2011 RTCA List of Available Documents Page 18 of 118
• The model is of a form and type that is used for direct analysis or behavioral evaluation as supported by the software development process or the software verification process.

Order Now

DO-332, Object-Oriented Technology and Related Techniques Supplement to DO-178C and DO-278A

This supplement identifies the additions, modifications and deletions to DO-178C and DO-278A objectives when object-oriented technology or related techniques are used as part of the software development life cycle and additional guidance is required. This supplement, in conjunction with DO-178C, is intended to provide a common framework for the evaluation and acceptance of object-oriented technology (OOT) and related techniques (RT)-based systems.

OOT has been widely adopted in non-critical software development projects. The use of this technology for critical software applications in avionics has increased, but there are a number of issues that need to be considered to ensure the safety and integrity goals are met. These issues are both directly related to language features and to complications encountered with meeting well-established safety objectives.

Order Now

DO-333, Formal Methods Supplement to DO-178C and DO-278A

This supplement identifies the additions, modifications and substitutions to DO-178C and DO-278A objectives when formal methods are used as part of a software life cycle, and the additional guidance required. It discusses those aspects of airworthiness certification that pertain to the production of software, using formal methods for systems approved using DO-178C.

Formal methods are mathematically-based techniques for the specification, development and verification of software aspects of digital systems. The mathematical basis of formal methods consists of formal logic, discrete mathematics and computer-readable languages. The use of formal methods is motivated by the expectation that, as in other engineering disciplines, performing appropriate mathematical analyses can contribute to establishing the correctness and robustness of a design.

Order Now