Loading

Aviation Certification

Airborne Software Assurance (DO-178C) Certification

Product certification
A moment from a certification audit

What Is the Certificate?

DO-178C (ED-12C in Europe) is the accepted guidance for the certification assurance of software in airborne systems and equipment. Aviation authorities (FAA, EASA) assess software assurance against this document during type certification. At its centre is the software level (DAL — Design Assurance Level): five levels from A to E, set by the effect a software failure would have on flight safety, which directly changes the number of objectives that must be satisfied.

Who Needs It?

  • Avionics software developers
  • Flight control, engine control and navigation system manufacturers
  • Developers of cabin systems and in-flight entertainment software
  • Developers of unmanned aircraft system software
  • Firms acting as a supplier for aerospace software

Is It Mandatory?

The document is not directly a legal text; it is recognised by aviation authorities as an acceptable means of compliance. It is practically mandatory for software within scope of airworthiness certification. The output is not a 'DO-178C certificate': the software is assessed as part of the certification of the system it belongs to, and evidence of conformity is presented to the certification authority.

Scope of the Standard

  • Deriving the software level (DAL A-E) from the system safety assessment
  • The planning process: the PSAC, the software development plan, the verification plan, the configuration management plan, the quality assurance plan
  • Software development processes: requirements definition, design, coding, integration
  • The verification process: requirements-based testing, low-level testing, integration testing
  • Structural coverage analysis: statement coverage for DAL C, decision coverage for DAL B, MC/DC for DAL A
  • Traceability: from system requirements through to code and test cases
  • Configuration management and problem reporting
  • Software quality assurance and conformity review (SOI audits)
  • Software development tool qualification (DO-330)
  • Supplement technologies: model-based development (DO-331), object-oriented technology (DO-332), formal methods (DO-333)
  • Certification liaison and the Software Accomplishment Summary (SAS)

Certification Process

  1. 1Application and Product DescriptionThe product family, model list, technical specifications and target market are determined. The applicable standard and certification route become clear at this step.
  2. 2Technical File ReviewDesign documents, the bill of materials, critical-component certificates and the instructions for use are examined.
  3. 3Product TestingThe tests the relevant standard requires are carried out. The test report is the fundamental basis for the certification decision.
  4. 4Factory AuditIf the scheme requires it, the continuity of manufacturing and factory production control (FPC) are verified on site.
  5. 5Issuing the Certificate and MarkingOnce conformity is verified, the certificate is issued; the marking rules for the product and packaging are applied.
  6. 6Follow-up AuditsDepending on the scheme, periodic factory audits and/or follow-up testing on samples taken from the market are carried out.

Period of Validity

The validity period varies by scheme: some product certificates are indefinite and rely on periodic factory audits, while some schemes (e.g. country market marks) require annual or per-shipment renewal. Every design change to the product requires the certificate to be reviewed.

Required Documents

  • The list of product models and variants
  • Technical drawings, diagrams and the bill of materials
  • Certificates for critical components
  • The instructions for use and a sample label
  • Existing test reports, if any
  • Production-site details
  • PSAC — Plan for Software Aspects of Certification
  • The software development, verification, configuration management and quality assurance plans
  • Software requirements and design descriptions
  • Traceability matrices
  • Test cases, procedures and results
  • Structural coverage analysis reports
  • Problem reports and the configuration index
  • SAS — Software Accomplishment Summary

Certification Cost

There is no fixed list price; the cost is calculated based on the following variables and provided in writing in the quote.

  • The number of models and variants in the product family
  • The test scope the applicable standard requires
  • Whether a factory audit is required
  • The number of target markets and whether each requires separate testing
  • Whether existing test reports can be accepted

Accreditation

Product certification is carried out under ISO/IEC 17065; The tests that form the basis for certification are carried out in laboratories with ISO/IEC 17025 accreditation. The two scopes are separate. Recognition between accreditation bodies is provided through IAF and ILAC agreements.

The scope under which this scheme can be offered varies according to your product and activity; it is confirmed in writing at the quote stage.

Scope and authorisations

Related Certifications

Frequently Asked Questions

Can I get a DO-178C certificate?

No certificate is issued in the classic sense. The software is assessed as part of the airworthiness certification of the system it belongs to. What can be obtained from an independent body is a conformity assessment or readiness-audit report; final acceptance rests with the authority.

What is MC/DC and why is it hard?

Modified Condition/Decision Coverage — the strictest structural coverage criterion required for DAL A. It requires testing that each condition in a decision independently affects the outcome. It is costly because it markedly increases the number of test cases.

Who determines the DAL level?

It is determined by the safety assessment carried out at system level. The worst possible effect of a software failure (catastrophic, hazardous, major, minor, no effect) gives the level; this is an output of the system safety team, not the software team.

We use cookies required for the site to work. With your permission we also add an analytics cookie to understand how pages are used. Cookie Policy