DO-178C/DO-254 software & hardware qualification

No commercial aircraft can carry software into the sky without a paperwork trail that proves it will not fail. As of 2026, India cannot produce that proof to international standards on its own — its dependence on foreign certification services stands at 100 per cent.

The standard in question is DO-178C, jointly published by RTCA in the United States and EUROCAE in Europe, and completed in November 2011. Together with its hardware counterpart DO-254 — which governs circuit boards, ASICs and FPGAs — it is the framework by which the FAA, EASA and Transport Canada accept the software and electronics inside airborne systems. Only a handful of jurisdictions operate it as a recognised means of compliance: the United States, the European Union, Canada, China and Japan.

The difficulty is not coding; it is discipline at scale. DO-178C is a process standard, not a tool. It demands bidirectional traceability linking every requirement to its source code, test cases and test results — difficult enough on first attempt that a global training and consulting market exists solely to teach it. A Design Assurance Level A project, the tier for flight-control software, requires 71 objectives to be satisfied. Verification must be independent of development, and every verification tool must itself be qualified under DO-330, which defines five tool qualification levels. Five certification plans — PSAC, SDP, SVP, SCMP, SQAP — anchor each project, and verification alone consumes a large proportion of total cost.

India's activity is real but partial. CEMILAC, the DRDO's Centre for Military Airworthiness and Certification, runs a Software and E-Certification Directorate that certifies flight-safety-critical avionics for military fighters, helicopters and UAVs — but under its own DDPMAS/IMTAR-21 framework, not DO-178C. On the commercial side, Cyient offers avionics software verification and certification support including DO-178C compliance work; Tata Advanced Systems develops avionics and embedded systems for Indian programmes; and Unical Systems trains engineers through an 80-hour instructor-led DO-178C course. What is missing is an indigenous certification authority.

The gap persists because the foundations are thin. The system safety assessment capability that must precede software development, drawn from ARP4754/ARP4761, is only emerging. Independent verification resources are emerging. The airborne software process framework, DO-254 hardware assurance, and a pool of engineers able to liaise with the FAA and EASA across a full lifecycle are, in the facts, absent.

Closing it means building those layers in sequence — the safety analyses first, the process and tool qualification next, and the liaison expertise that turns compliant work into recognised certification.