The conversation around software airworthiness in defense aviation has grown sharply more complex — and more important to program success. As the Department of War (DoW) accelerates the adoption of commercial certification standards across its aviation programs, defense OEMs and integrators are navigating a terrain where the rules of commercial aviation increasingly intersect with the realities of the battlefield. At the center of that intersection is DO-178C.
Understanding what DO-178C demands and where it diverges from military-specific requirements is critical to delivering a successful program.
What is DO178C?
DO-178C — Software Considerations in Airborne Systems and Equipment Certification — is the global industry standard for developing and certifying safety-critical airborne software. Published by Radio Technical Commission for Aeronautics (RTCA) and recognized by the Federal Aviation Administration (FAA), European Union Aviation Safety Agency (EASA), and airworthiness authorities worldwide, it defines the processes, objectives, and evidence required to demonstrate that software will perform reliably across all operating conditions.
The standard governs the entire software lifecycle, from planning and requirements through design, coding, integration, and verification. Its rigor scales to the criticality of the software through five Design Assurance Levels (DAL A through E), corresponding to failure conditions ranging from minor to catastrophic.
Considerations for Defense Programs
Originally developed for commercial aviation, DO-178C is now widely applied in defense programs—though not formally mandated. Unlike commercial aviation, where it is required for certification, its use in military platforms is typically driven by airworthiness authorities, program requirements, and the need to align with civil standards—particularly for systems operating in shared or civil airspace.
That reality is shaped by how military airworthiness is defined in guidance such as MIL-HDBK-516C. This framework defines the certification criteria applied across manned and unmanned, fixed and rotary wing air vehicle systems — and it points to DO-178C as one of the recognized approaches for demonstrating software airworthiness. Alongside it, a legacy framework of military software standards has historically guided how defense programs approach development, documentation, and verification. Standards such as MIL-STD-2167A and MIL-STD-498 established a disciplined foundation, but were not built for today’s commercially integrated, software-intensive platforms—where the limits of purely military-specific frameworks are now increasingly apparent.
The relationship between the military standards ecosystem and DO-178C is therefore complementary rather than competitive. Military airworthiness guidance defines the criteria used to assess overall system airworthiness, while DO-178C provides the objective-based, lifecycle framework for software development and verification that those guidance documents reference but do not fully prescribe. In practice, programs must navigate both simultaneously—mapping DO-178C planning, requirements, and verification objectives to military airworthiness criteria and ensuring the resulting evidence supports the overall airworthiness of the aircraft.
The practical pull toward DO-178C is also a workforce and supply chain calculation. Military aircraft integrators frequently rely on suppliers drawn from the civil market, where familiarity with DO-178C is already embedded in engineering practice. Adopting the standard reduces the friction of that relationship considerably. The alternative — requiring suppliers to work to purely military-specific standards — narrows the competitive field and drives up cost.
What the standard does not do, however, is eliminate the need for defense-specific expertise. Applying DO-178C to a military platform requires understanding where it maps cleanly to military requirements, where gaps exist that must be addressed through supplemental criteria or additional considerations, and how the approval authority — a military agency rather than the FAA — will evaluate the resulting evidence package.
Choosing the Right Certification Partner
Defense programs facing DO-178C requirements need a partner who has been there before — across DAL A through E systems, across programs of every scale and complexity, across the full software lifecycle from planning to sustainment.
At Performance, DO-178C is at the core of what we do. With nearly 30 years and more than 500 programs completed, we have built deep technical expertise across all avionics domains. That breadth means we integrate seamlessly into programs of any architecture, at any stage, without the learning curve that costs programs time they don’t have.
Our end-to-end execution model covers every phase of the DO-178C lifecycle: planning and certification strategy, requirements development and traceability, software design and coding, integration, verification, and long-term sustainment. Our engineers work as an extension of customer teams, navigating complex requirements, maintaining schedule discipline, and reducing certification risk at every stage.
We also bring the relationship infrastructure that makes certification work in practice. Established partnerships with FAA Designated Engineering Representatives (DER) and close collaboration with FAA representatives ensure that programs meet certification authority expectations from day one
And where AI-assisted engineering can be applied without compromising certification compliance, we are already deploying it — under strict safeguards and governance — across dozens of active customer programs to improve requirements analysis, accelerate verification, surface coverage gaps earlier, and bring greater consistency to documentation-intensive processes. This is not an experimental capability. It is operational, governed, and delivering results on programs today.
