What Makes a Cockpit Display System ARINC 661 Compliant?

For avionics engineers and procurement managers selecting display solutions for commercial aviation platforms, ARINC 661 compliance is not a marketing credential - it is a fundamental architectural requirement. The standard defines the interface between a cockpit display system (CDS) and the user application (UA) software layer, and its correct implementation directly determines whether a display system can be integrated into a modern glass cockpit without bespoke software development work for each new aircraft program.

The ARINC 661 Standard: Core Concepts

ARINC 661, formally titled "Cockpit Display System Interfaces to User Systems," was developed by Airlines Electronic Engineering Committee (AEEC) to standardize the communication protocol between the CDS hardware/software layer and the avionics applications that generate display content. Prior to ARINC 661, each avionics supplier used proprietary protocols, making it extremely difficult to substitute or upgrade display hardware without re-writing application software - a time-consuming and expensive undertaking for aircraft manufacturers and airlines alike.

The standard defines two primary elements: a data model specifying the graphical widget types (symbols, text fields, buttons, dials, maps) that the CDS must be able to render, and a communication protocol specifying how the UA transmits display content requests and how the CDS acknowledges and reports interaction events back. This clean separation of presentation from application logic is the architectural innovation that makes ARINC 661 valuable for platform manufacturers integrating displays across multiple aircraft types.

Compliance Requirements for the CDS Layer

An ARINC 661-compliant cockpit display system must implement the full widget library defined in the relevant supplement level - ARINC 661 Supplement 6 being the current baseline for most new commercial programs. Key compliance requirements include:

•      Widget rendering fidelity: All graphical objects must be rendered with the geometry, color, and interactive behavior defined by the standard, without proprietary extensions that would create CDS-specific application dependencies.

•      Communication protocol conformance: The binary communication protocol between UA and CDS must conform precisely to the defined message formats, timing constraints, and error handling behaviors.

•      Interaction event reporting: Touch and cursor events on CDS-rendered widgets must be reported back to the UA in the standardized event format, with timing precision that meets the display's qualified update rate.

•      Definition file processing: The CDS must correctly parse and render display definitions transmitted by the UA in the ARINC 661 DF (Definition File) format without requiring pre-compilation or offline preparation steps.

Supplement Levels and Forward Compatibility

ARINC 661 has been extended through multiple supplements that add new widget types, interactive behaviors, and communication features. A display system qualified to Supplement 3 can render the widget set defined at that supplement level, but cannot process Supplement 6 features without hardware or firmware upgrade. For platform manufacturers planning long-service-life aircraft - where the display hardware may remain in service for 25-30 years while avionics software is updated multiple times - specifying the highest available supplement level at platform entry into service provides maximum forward compatibility headroom.

Interaction with DO-178C Software Qualification

ARINC 661 compliance addresses the interface standard; it does not by itself constitute a complete avionics software certification. The CDS software that implements the ARINC 661 widget rendering engine must be developed and qualified to DO-178C at the appropriate Design Assurance Level (DAL) - typically DAL B or DAL A for primary flight display functions. System integrators evaluating cockpit display system suppliers must verify both ARINC 661 conformance testing evidence and the DO-178C qualification level of the CDS software, as these are distinct and complementary requirements.

About AEROMAOZ

With more than 45 years of experience developing cockpit display systems for commercial and military aviation, AEROMAOZ produces ARINC 661-compliant display hardware and software that is fully qualified to applicable DO-178C and DO-254 levels. AEROMAOZ engineering teams support system integrators including Thales, Honeywell, and Rockwell Collins in integrating standardized display solutions across multiple aircraft platforms, reducing non-recurring integration costs and schedule risk for new program entries.

Conclusion

ARINC 661 compliance represents a fundamental shift in how cockpit display systems are specified, procured, and integrated. By standardizing the CDS-to-UA interface, it enables platform manufacturers and system integrators to treat display hardware as a conformant commodity layer rather than a program-unique bespoke system. For procurement managers and design engineers, verifying supplement-level compliance, DO-178C qualification evidence, and conformance test documentation should be non-negotiable elements of any CDS source selection process.