Aerospace / Defence / Avionics / Space-Systems DSLs Family Index
type: language-family-index family: aerospace-defence languages_catalogued: 32 tags: [language-reference, family-index, aerospace-defence, arinc, stanag, ccsds, dds, mil-std, face, sosa, link-16, asterix, aixm]
Aerospace / Defence / Avionics / Space-Systems — Family Index
Family overview
Aerospace, defence, and space systems are dominated less by general-purpose programming languages than by a thicket of textual interface specifications, message-format DSLs, and standardised data-exchange schemas maintained by industry bodies (ARINC, SAE, RTCA, OMG, EUROCONTROL, ICAO) and military/civil-government agencies (NATO via STANAG, DoD via MIL-STD, ESA/NASA/JAXA via CCSDS, FAA via AIXM/FIXM). The dividing lines are tribal: civil aviation uses ARINC + EUROCONTROL + ICAO standards, the US military uses MIL-STD + SAE AS series, NATO uses STANAG, and space uses CCSDS — but in practice the same hardware vendors implement all of them simultaneously, and the lines blur (FACE and SOSA are DoD-driven but coordinated through The Open Group; AIXM was a EUROCONTROL/FAA joint product).
The civil-avionics bus lineage runs ARINC 429 (1977, simplex broadcast, 12.5 / 100 kbps) → ARINC 629 (limited adoption, mostly Boeing 777) → ARINC 664 / AFDX (Avionics Full-DupleX Switched Ethernet, ~2002+, deterministic switched Ethernet, used on A380, A350, A400M, B787, A220). The military-bus lineage is shorter: MIL-STD-1553 (1973) and its weapons-interface companion MIL-STD-1760 dominate, and despite being 50+ years old, 1553 remains the default databus on US military aircraft because re-certifying replacements is not worth the cost on legacy airframes. The modern distributed-real-time middleware story is OMG’s DDS (Data Distribution Service, currently v1.4 from April 2015, with the DDSI-RTPS wire protocol at v2.5 and DDS-Security at v1.2), used in both civil and defence systems as the pub/sub layer above the buses.
The space-data ecosystem is CCSDS’s: the Space Packet Protocol (CCSDS 133.0-B-2), CFDP (CCSDS File Delivery Protocol), TM/TC (Telemetry/Telecommand), SLE (Space Link Extension for ground-to-spacecraft links), and the Mission Operations service framework. CCSDS is a quietly successful international standardisation effort — NASA, ESA, JAXA, Roscosmos, CSA, ASI, CNES, DLR, UKSA, ISRO and others all align on the same wire formats, which is why a JAXA ground station can downlink an ESA spacecraft. STANAG is NATO’s parallel umbrella, but unlike CCSDS it is not a single technical family — it is hundreds of disparate agreements ranging from fuel specs to data formats. The DSL-relevant ones include STANAG 4586 (UAV control), STANAG 4609 (motion-imagery metadata, layered over MISB-extended MPEG-2 TS / KLV), STANAG 4607 (GMTI — Ground Moving Target Indicator), STANAG 4670, STANAG 5066 (HF radio data link), STANAG 7075 (digital geographic data).
A fourth thread is the modular-open-architecture wave: FACE (Future Airborne Capability Environment, currently Technical Standard Edition 3.2, with Editions 1.x and 2.0.x sunsetting through June 2026), SOSA (Sensor Open Systems Architecture, currently Edition 2.0 Snapshot 3 released June 2025), MOSA (Modular Open Systems Approach, DoD policy framework), VICTORY (Vehicular Integration for C4ISR/EW Interoperability, US Army), OMS/UCI (Open Mission Systems / Universal Command and Control Interface, USAF). All emerged 2010+ as DoD reactions against closed proprietary stacks: the goal is software portability across vendors, common data models, and standardised service interfaces over Ethernet + DDS or similar middleware. Tactical data links (Link 16 / J-Series, Link 22, VMF / MIL-STD-6017, legacy Link 11) are the radio-side cousin — message-set DSLs encoded for transmission over time-slot-allocated TDMA radio networks rather than buses.
In our deep library
Most aerospace-defence DSLs do not have standalone deep-library notes — they live in vendor toolchains and standards-body PDFs rather than in general programming-language documentation. Cross-reference the siblings that share infrastructure:
- automotive-onvehicle — sibling family; CAN/LIN/FlexRay/CAN-FD and DBC/ARXML are the automotive parallel to MIL-STD-1553 + ARINC 429 + ARINC 664. SOME/IP and DDS overlap as middlewares.
- industrial-automation — sibling fieldbus DSLs (Modbus, PROFIBUS/PROFINET, EtherCAT, OPC UA). OPC UA is sometimes used in ground-support equipment for aerospace and converges with DDS in some open-architecture proposals.
- robotics-control — sibling; ROS / ROS 2 uses DDS under the hood, and JAUS overlaps in the UAV / unmanned-ground-vehicle domain.
- network-protocol-dsls — DDS, RTPS, ARINC 664 sit over UDP/IP; the underlying wire protocols are catalogued there.
- api-description — OMG IDL 4.2 is the type-definition layer for DDS topics and CORBA; it is the closest aerospace cousin to Protobuf/Avro/Thrift schemas.
- geospatial — NITF (National Imagery Transmission Format) and STANAG 4609 motion-imagery metadata are dual-classified there. AIXM is GML-compliant and overlaps with geospatial XML.
- notation-spec — AADL (SAE AS5506C), EAST-ADL, and Simulink/Stateflow are formal architecture-description languages that sit at the boundary of “DSL” and “modelling notation”.
- embedded-firmware — ARINC 653 APEX, SPARK Ada, and the Ada/C/C++ subsets that compile to DO-178C/DO-254-certified targets share infrastructure.
Tier 3 family table — Avionics buses & systems
| Format | First appeared | Origin | Type | Status (2026) | URL |
|---|---|---|---|---|---|
| MIL-STD-1553B | 1973 (1553), 1978 (1553B) | US DoD (USAF) | 1 Mbps dual-redundant serial command/response bus; ICD message/signal layout conventions | Active, still ubiquitous on US military airframes despite being >50 years old; re-certifying replacements not cost-justified on legacy fleets | https://everyspec.com/MIL-STD/MIL-STD-1500-1599/MIL-STD-1553B_8025/ |
| MIL-STD-1760 | 1981 | US DoD | Aircraft–weapons electrical interconnection standard (Store interface); layers above 1553 | Active, the canonical weapons-pylon interface | https://everyspec.com/MIL-STD/MIL-STD-1700-1799/MIL-STD-1760E_55988/ |
| ARINC 429 | 1977 | ARINC / AEEC | 12.5/100 kbps simplex serial broadcast; 32-bit word DSL with labels and BCD/BNR encodings | Active, still the default civil-avionics bus on older airframes | https://www.aviation-ia.com/product/arinc-specification-429-mark-33-digital-information-transfer-system-dits |
| ARINC 629 | 1995 | ARINC | Multi-transmitter 2 Mbps bus, intended 1553 replacement | Legacy, only widely used on Boeing 777 | https://www.aviation-ia.com/product/arinc-specification-629 |
| ARINC 664 / AFDX | 2002+ (ARINC 664 Part 7 most relevant) | Airbus, then ARINC standardised | Avionics Full-DupleX Switched Ethernet; deterministic 100 Mbps / 1 Gbps switched Ethernet with Virtual Links and bounded latency | Active, the modern civil-avionics backbone (A380, A350, A400M, B787, A220, KC-46) | https://www.aviation-ia.com/product/arinc-specification-664p7 |
| ARINC 653 (APEX) | 1996, current Supplement 5 (2019) | ARINC / AEEC | RTOS partitioning DSL — XML configuration for IMA (Integrated Modular Avionics) time/space partitioning and inter-partition channels | Active, the foundation for FACE OSS partitioning | https://www.aviation-ia.com/product/arinc-specification-653p1-5 |
| ARINC 661 | 2002, currently Supplement 8 (2022); Part 2 markup-language extension under development, Supplement 2 expected Oct 2026 | ARINC / AEEC | Cockpit Display System (CDS) interface DSL; widget-tree definition language for certified cockpit GUIs; Part 2 adds a UI markup language | Active, used across most new commercial aircraft and many military programmes since A380 | https://www.aviation-ia.com/product/arinc-specification-661 |
Tier 3 family table — Tactical data links & messaging
| Format | First appeared | Origin | Type | Status (2026) | URL |
|---|---|---|---|---|---|
| Link 16 (MIL-STD-6016, J-Series) | 1975 (concept), MIDS terminals 1990s+, MIL-STD-6016G (2018) | US DoD / NATO | TDMA tactical data link; J-Series fixed-format binary message DSL over time-slot-allocated radio | Very active, the NATO joint TDL standard; J-series catalog continues to grow | https://www.public.navy.mil/jit/Pages/default.aspx |
| Link 22 (NILE) | Initial fielding 2010s, broader rollout 2020s | NATO Improved Link Eleven (NILE) consortium | Successor to Link 11; F-series messages over multi-frequency HF/UHF networks | Active, fielded by 26 nations as of 2025; major French Navy operational milestone Feb–Apr 2025 (Charles de Gaulle Carrier Strike Group, Clemenceau 25 mission) | https://www.link22.org/ |
| VMF / MIL-STD-6017 | 1990s | US DoD | Variable Message Format for situational awareness; bit-oriented variable-length K-series messages | Active, the situational-awareness counterpart to Link 16 | https://everyspec.com/MIL-STD/MIL-STD-6000-6099/MIL-STD-6017C_55812/ |
| Link 11 / TADIL-A / Link 11B | 1960s | US Navy / NATO | M-series messages over HF/UHF; CLEW (Conventional Link Eleven Waveform) | Legacy, being retired in favour of Link 22 but still operational | (NATO STANAG 5511, restricted) |
| MIL-STD-2525 (current 2525E) | 1994 (2525A), 2525E published recent years | US DoD | Map-symbol DSL for C2 systems; SIDC (Symbol Identification Code) string encoding; harmonised with NATO APP-6(E) | Active, the joint US/NATO symbology standard | https://standards.globalspec.com/std/14616887/mil-std-2525e |
| NITF | 1987 (NITF 1.0), 2.1 widely deployed | US DoD / Intelligence Community | National Imagery Transmission Format; file container for geospatial imagery + metadata; supports JPEG/JPEG 2000 payloads | Active, still the IC/DoD imagery interchange standard | https://gwg.nga.mil/ntb/ |
| STANAG 4586 | 2002 (Edition 1), Edition 4 current | NATO | Standard interfaces of UAV Control System (UCS); message DSL for UAV-vehicle/payload/sensor control | Active, the NATO UAV-control interoperability standard | https://nso.nato.int/nso/ |
| STANAG 4609 | 2007+ | NATO / MISB | Motion-imagery metadata; layered over MPEG-2 TS + KLV (SMPTE 336M); MISB extensions for full-motion-video | Active, the FMV standard for UAV/ISR | https://nsgreg.nga.mil/misb.jsp |
| STANAG 4607 | 2005+ | NATO | GMTI (Ground Moving Target Indicator) radar data format | Active, used across NATO ISR | https://nso.nato.int/nso/ |
Tier 3 family table — Space data systems (CCSDS family)
| Format | First appeared | Origin | Type | Status (2026) | URL |
|---|---|---|---|---|---|
| CCSDS Space Packet Protocol | 1994 (133.0-B-1), 133.0-B-2 current | CCSDS (NASA/ESA/JAXA/Roscosmos/CSA/ASI/CNES/DLR/UKSA et al.) | 6-byte header + up to 65,536-byte data unit; APID-addressed; the foundational space transport DSL | Active, CCSDS 133.0-B-2 the current Blue Book | https://ccsds.org/Pubs/133x0b2e2.pdf |
| CCSDS CFDP (File Delivery Protocol) | 2002 (727.0-B-1), 727.0-B-5 current | CCSDS | File-delivery DSL over store-and-forward space links; handles long delay/disruption | Active, used by NASA Deep Space Network and ESA missions | https://ccsds.org/publications/bluebooks/ |
| CCSDS TM/TC (Telemetry / Telecommand) | TM (132.0-B), TC (231.0-B) packet protocols | CCSDS | Frame-level and packet-level DSLs for spacecraft telemetry downlink and command uplink | Active | https://ccsds.org/publications/bluebooks/ |
| CCSDS SLE (Space Link Extension) | 2000s onwards | CCSDS | Ground-network service DSL; standardised interface for cross-agency ground-station services | Active, enables NASA DSN ↔ ESA ESTRACK ↔ JAXA UDSC interoperability | https://ccsds.org/publications/bluebooks/ |
| CCSDS Mission Operations services | 2010s onwards | CCSDS | Service-oriented framework for spacecraft monitoring & control; aligned with ECSS | Active, gradual adoption | https://ccsds.org/publications/bluebooks/ |
Tier 3 family table — Modular open architectures
| Format | First appeared | Origin | Type | Status (2026) | URL |
|---|---|---|---|---|---|
| FACE Technical Standard | Edition 1.0 (2012), currently Edition 3.2; Editions 1.x/2.0.x final conformance window ends 14 June 2026 | The Open Group FACE Consortium (US Tri-Service) | Software architecture standard for airborne mission-systems; defines Operating System Segment, Transport Services, Portable Components, Platform-Specific Services; relies on ARINC 653 partitioning, POSIX, DDS | Active, mandated on most new US Army aviation and Navy programmes; Edition 3.2 latest | https://www.opengroup.org/face |
| SOSA Reference Architecture | Edition 1.0 (2021), Edition 2.0 Snapshot 3 (June 2025) | The Open Group SOSA Consortium (US Tri-Service) | Hardware/software interface standard for sensor systems (radar, EO/IR, EW, SIGINT); VPX/OpenVPX backplane + standardised software interfaces | Active, drafted for mandate alongside FACE | https://www.opengroup.org/sosa |
| MOSA (Modular Open Systems Approach) | Established as DoD policy 2019 (NDAA Section 805) | US DoD policy framework | Not a single DSL — a procurement framework requiring open standards and interface specifications across major defence acquisitions | Active, codified policy | https://ac.cto.mil/mosa/ |
| VICTORY | 2010 onwards; specification currently V1.10 (MORA appendix 2023) | US Army (TARDEC / CCDC GVSC) | Vehicular Integration for C4ISR/EW Interoperability; SOAP-over-Ethernet “VICTORY Databus” with prescribed services for combat-vehicle electronics | Active, Army programme of record | https://victory-standards.org/ |
| OMS / UCI | OMS 2010s (USAF), UCI parallel | USAF (AFLCMC) | Open Mission Systems / Universal Command and Control Interface; XML-schema-based service-interface DSLs for ISR and C2 | Active, USAF programmes | (DoD distribution-controlled; AFLCMC published) |
| JAUS (SAE AS-4) | 1998 (DoD JAUGS), SAE AS-4 family ongoing (AS5669 Transport, AS5710 Core Services, AS6060 Environment Sensing, etc.) | DoD → SAE AS-4 Unmanned Systems Steering Committee | Message-set DSL for unmanned systems (UGV, UAV, USV, UUV); transport spec + service-set specs | Active, but partly eclipsed by ROS 2 / DDS in non-DoD robotics | https://www.sae.org/works/committeeHome.do?comtID=TEAAS4JAUS |
| OMG DDS | DDS 1.0 (2004), DDS 1.4 (April 2015 current) | OMG (RTI, Twin Oaks, ADLINK, eProsima, ZettaScale et al.) | Data-centric publish-subscribe middleware; QoS-rich; DDS-IDL topic-type schemas via OMG IDL | Active, the de facto distributed-real-time pub/sub for aerospace + defence; powers ROS 2 by default | https://www.omg.org/spec/DDS/1.4/About-DDS |
| DDS-RTPS (Real-Time Publish-Subscribe wire protocol) | DDSI-RTPS, currently v2.5 | OMG | DDS interoperability wire protocol; UDP/IP-based | Active | https://www.omg.org/spec/DDSI-RTPS/2.5 |
| DDS Security | v1.0 (2016), v1.2 current | OMG | Pluggable authentication / access-control / cryptography for DDS | Active | https://www.omg.org/spec/DDS-SECURITY/1.2/About-DDS-SECURITY |
| DDS-XTypes | v1.3 current | OMG | Extensible types and dynamic-type evolution for DDS | Active | https://www.omg.org/spec/DDS-XTypes |
| OMG IDL | v4.2 (March 2018) | OMG | Interface Definition Language; type-definition DSL used by DDS, CORBA, and others; v4.2 added 8-bit integers and size-explicit integer keywords | Active, the schema layer for DDS topics | https://www.omg.org/spec/IDL/4.2/About-IDL |
| STEP AP242 | Edition 1 (2014), Edition 2 (April 2020), Edition 3 (2025 — corrective maintenance), Edition 4 in development | ISO TC 184/SC 4 (ISO 10303-242) | Managed Model-Based 3D Engineering; aerospace + automotive MBE exchange schema with electrical-harness extensions and SysML-aligned implementation | Active, ISO 10303-242:2025 the current published edition | https://www.iso.org/standard/84300.html |
| AADL (SAE AS5506C) | AS5506 (2004), AS5506C (Jan 2017, documents AADL v2.2); AADL v3 in development | SAE Embedded Computing Committee, CMU/SEI | Architecture Analysis & Design Language — textual + graphical DSL for safety-critical real-time architecture; supports formal analysis of timing, schedulability, fault propagation | Active, AS5506C current; v3 in progress with CMU SEI Open Source AADL Tool Environment (OSATE) tooling | https://www.sei.cmu.edu/projects/architecture-analysis-and-design-language-aadl/ |
| EAST-ADL | 2010s, M2.1.12 current | ATESST/MAENAD/EAST-ADL Association | Automotive-focused architecture-description DSL; AADL cousin, AUTOSAR-aligned | Active but narrow community | https://www.east-adl.info/ |
Tier 3 family table — Aviation information exchange
| Format | First appeared | Origin | Type | Status (2026) | URL |
|---|---|---|---|---|---|
| AIXM | AIXM 4.5 (legacy), 5.1 (2010+), 5.1.1, AIXM 5.2 (January 2025) | EUROCONTROL + FAA | Aeronautical Information Exchange Model; GML-compliant XML schema for AIP, airports, navaids, airspace, NOTAM, IFR procedures; ICAO AIP/AMD/Obstacles datasets still coded against AIXM 5.1.1 | Active, AIXM 5.2 latest; 5.1.1 still the basis for current ICAO data-coding specs | https://aixm.aero/ |
| WXXM | 1.0 (2011), 2.0 (2017+) | EUROCONTROL + FAA + WMO | Weather Information Exchange Model; aviation weather XML schema; aligned with WMO METCE/IWXXM | Active | https://www.wxxm.aero/ |
| FIXM | 1.0 (2011), 4.3.0 current | FAA + EUROCONTROL + ICAO | Flight Information Exchange Model; XML schemas for flight plans + FF-ICE messaging; FF-ICE/R1 implementation Jan 2026 (Europe) and Q3 2026 (Asia-Pacific) | Active, FIXM 4.3 the FF-ICE/R1 standard format | https://www.fixm.aero/ |
| DAFIF / DAFIFT | DAFIF since 1970s, DAFIFT (DAFIF Tools) | NGA (US National Geospatial-Intelligence Agency) | Digital Aeronautical Flight Information File; military aviation database; binary + text record formats | Active for DoD distribution, public release discontinued in 2006; AIXM has largely superseded externally | https://www.nga.mil/ |
| EUROCONTROL ASTERIX | 1986 onwards | EUROCONTROL | All Purpose Structured EUROCONTROL Surveillance Information Exchange; binary record DSL for surveillance data; many categories (CAT 001, 002, 008, 010, 011, 019, 020, 021, 023, 030, 048, 062, 063, 065, …); CAT 062 Edition 1.21 (June 2025) and CAT 021 Edition 2.7 (July 2025) latest | Active, the dominant ATC radar/track data DSL in Europe and many non-US ANSPs | https://www.eurocontrol.int/asterix |
| Cursor on Target (CoT) | 2002, MITRE / USAF | MITRE | Lightweight XML schema for position + identity events; used by TAK (Tactical Assault Kit / ATAK / WinTAK) | Very active, the de facto SA exchange for tactical edge applications | https://www.mitre.org/sites/default/files/pdf/09_4937.pdf |
Notable threads
-
ARINC 429 → ARINC 664/AFDX modernisation in civil aviation. ARINC 429’s simplex 12.5/100 kbps point-to-point broadcast bus was elegant for the 1977 problem (federated avionics, hard-real-time, transmitter authority for each label) but couldn’t scale to hundreds of nodes and gigabit-class data. AFDX (ARINC 664 Part 7) replaced it with switched Ethernet + Virtual Links + bounded-latency QoS guarantees, first on the A380 (entry-into-service 2007) and then on A350, A400M, B787, A220, KC-46. The transition was painful: most modern airliners actually run both — AFDX for the high-bandwidth backbone, ARINC 429 for legacy line-replaceable units that haven’t been requalified. ARINC 429 will still be flying in 2050.
-
MIL-STD-1553 remains the default on 50-year-old fleets despite newer alternatives. Fibre Channel-AE (FC-AE), TTP/C, AFDX, and even DDS-over-1553 gateways have all been proposed as 1553 replacements. None have displaced it on production US military aircraft because the recurring cost of re-certifying a databus on a B-52, F-15, F-16, AH-64 etc. exceeds the value. New programmes (F-35, V-280, MQ-25) layer Ethernet + DDS on top, but the 1553 backbone is still there for legacy LRUs. The 1553 ICD discipline — formal interface definitions, signal-layout tables, BC/RT/BM roles — is itself a kind of DSL, and tooling (UEI, GE Intelligent Platforms / Abaco, Data Device Corp ddcWeb) treats ICDs as first-class artefacts.
-
OMG DDS as the de facto distributed pub/sub for both aerospace and defence. DDS 1.4 (April 2015) is unusual for a 10-year-old spec in that it has not been superseded — instead the ecosystem evolved by adding companion specs (DDS-Security v1.2, DDS-XTypes v1.3, DDSI-RTPS v2.5, DDS-Web). DDS is mandatory or recommended by FACE, SOSA, and large swathes of NATO C4ISR open-architecture work, and it is the default RMW (ROS Middleware) for ROS 2, which folds the robotics ecosystem into the same standard. Vendors include RTI Connext, eProsima Fast DDS, ZettaScale Cyclone DDS (formerly ADLINK), Twin Oaks CoreDX, OpenSplice DDS. The IDL topic-type layer (OMG IDL 4.2, March 2018) is what gives DDS its schema discipline and lets a C++ publisher talk to a Rust subscriber.
-
CCSDS as a quietly successful international standardisation effort. CCSDS is not as famous as IETF or W3C, but functionally it is the IETF of space — and NASA, ESA, JAXA, Roscosmos, CNES, DLR, ASI, UKSA, CSA, ISRO and others actually align on it. A consequence: ground stations are nearly fungible across agencies via SLE, and small-sat constellations can buy off-the-shelf protocol stacks (Cesium Astro, libcsp adapters, OpenC3 COSMOS). The Blue Book / Magenta Book / Green Book / Orange Book classification (recommended standard / recommended practice / informational / experimental) mirrors IETF’s RFC tracks. Most current spec PDFs are at https://ccsds.org/publications/bluebooks/.
-
FACE / SOSA / MOSA driving software-portability mandates in DoD. FACE Technical Standard Edition 3.2 (with Editions 1.x and 2.0.x in their final-conformance sunset window ending 14 June 2026), SOSA Edition 2.0 Snapshot 3 (June 2025), and MOSA (NDAA 2019 Section 805 policy) collectively mean US DoD aviation and sensor procurement now contractually demands interface-portable, multi-vendor software stacks. The technical foundations are ARINC 653 partitioning + POSIX + DDS + standardised data models. The hard part is not the technology but the cultural shift from “stack-vendor-lock-in” to “portable Units of Conformance”; the FACE Library (the catalogue of conformant components) is the visible evidence of how far this has gotten.
-
Link 16 evolution and Link 22 succession. Link 16 (J-series messages, MIL-STD-6016G, MIDS terminals) is still the joint NATO TDL workhorse, and remains active under continuous J-series catalogue expansion. Link 22 (NILE — NATO Improved Link Eleven) is the designated successor to Link 11 (the older HF/UHF link), and as of 2025 is fielded by 26 nations, with significant operational milestones during the French Charles de Gaulle Carrier Strike Group’s Clemenceau 25 deployment (Feb–Apr 2025) and a January 2025 seven-nation NATO interoperability demonstration. Link 22 is not a Link 16 replacement — they are complementary, with Link 22 focused on the over-the-horizon HF/UHF role and Link 16 on the line-of-sight TDMA role.
-
ASTERIX as the dominant ATC radar-data DSL. EUROCONTROL ASTERIX (All Purpose Structured EUROCONTROL Surveillance Information Exchange) is what almost every European and many non-European ANSPs use to move surveillance data between radars, multilateration systems, ADS-B receivers, and ATC centres. Each category (CAT 001/002 monoradar, CAT 008 weather, CAT 011 SMR, CAT 019/020 multilateration, CAT 021 ADS-B target reports, CAT 023 surveillance service, CAT 048 monoradar target reports, CAT 062 system track, etc.) is its own bit-packed binary record format with fixed and variable fields. EUROCONTROL maintains current editions actively — CAT 062 Edition 1.21 was released in June 2025 and CAT 021 Edition 2.7 in July 2025 — and tooling like Wireshark dissectors, asterix-specs (zoranbosnjak), and several commercial products are widely deployed.
-
The certification chain (DO-178C / DO-254 / DO-330) constrains what languages can ship in safety-critical aerospace. DO-178C (2011/2012, no DO-178D in active circulation) is the software certification standard for airborne systems, with companion documents DO-278A (ground systems), DO-248C (rationale), DO-330 (tool qualification), DO-331 (modelling — Simulink/Stateflow), DO-332 (object-oriented programming), and DO-333 (formal methods — Frama-C, SPARK Ada, Astrée). DO-254 is the hardware analogue. The practical effect: certifiable code on a DAL-A avionics target is typically Ada/SPARK or a constrained C subset, compiled with a qualified toolchain (Green Hills, AdaCore GNAT Pro for DO-178, IAR for some platforms), running on an ARINC 653-partitioned RTOS (LynxOS-178, INTEGRITY-178, VxWorks 653, PikeOS, Deos). MATLAB Simulink + Stateflow + Embedded Coder via the DO-331 modelling supplement is the dominant model-based-development pathway. This certification gravity is why mainstream languages (Rust, modern C++, Python) take so long to penetrate flight-critical avionics — the tool-qualification burden is enormous, though Rust is now seeing real DO-178C-track activity (Ferrous Systems Ferrocene, AdaCore GNAT/Rust integration).
Citations
- ARINC standards portal (SAE-ITC): https://www.aviation-ia.com/standards
- ARINC 661: https://www.aviation-ia.com/product/arinc-specification-661
- ARINC 664P7 (AFDX): https://www.aviation-ia.com/product/arinc-specification-664p7
- ARINC 653: https://www.aviation-ia.com/product/arinc-specification-653p1-5
- MIL-STD-1553B (EverySpec): https://everyspec.com/MIL-STD/MIL-STD-1500-1599/MIL-STD-1553B_8025/
- MIL-STD-2525E (GlobalSpec): https://standards.globalspec.com/std/14616887/mil-std-2525e
- CCSDS Blue Books: https://ccsds.org/publications/bluebooks/
- CCSDS Space Packet Protocol 133.0-B-2: https://ccsds.org/Pubs/133x0b2e2.pdf
- OMG DDS 1.4: https://www.omg.org/spec/DDS/1.4/About-DDS
- OMG IDL 4.2: https://www.omg.org/spec/IDL/4.2/About-IDL
- OMG DDS-Security 1.2: https://www.omg.org/spec/DDS-SECURITY/1.2/About-DDS-SECURITY
- OMG DDSI-RTPS 2.5: https://www.omg.org/spec/DDSI-RTPS/2.5
- NATO Standardization Office (STANAGs): https://nso.nato.int/nso/
- FACE Consortium: https://www.opengroup.org/face
- FACE Edition 3.2 sunset note (Edition 1.x/2.0.x): https://www.opengroup.org/face/docsandtools
- SOSA Consortium: https://www.opengroup.org/sosa
- SOSA Edition 2.0 Snapshot 3 (June 2025): https://militaryembedded.com/radar-ew/sensors/sosa-consortium-releases-the-technical-standard-for-sosa-reference-architecture-edition-20-snapshot-3
- VICTORY Standards: https://victory-standards.org/
- JAUS / SAE AS-4: https://www.sae.org/works/committeeHome.do?comtID=TEAAS4JAUS
- AADL (SEI / SAE AS5506C): https://www.sei.cmu.edu/projects/architecture-analysis-and-design-language-aadl/
- ISO 10303-242 (STEP AP242, 2025 edition): https://www.iso.org/standard/84300.html
- AIXM (5.2 January 2025): https://aixm.aero/page/aixm-52
- FIXM 4.3: https://www.fixm.aero/
- EUROCONTROL ASTERIX (CAT 062 Ed. 1.21, June 2025): https://www.eurocontrol.int/publication/cat062-eurocontrol-specification-surveillance-data-exchange-asterix-part-9-category-062
- EUROCONTROL ASTERIX (CAT 021 Ed. 2.7, July 2025): https://www.eurocontrol.int/publication/cat021-eurocontrol-specification-surveillance-data-exchange-asterix-part-12-category-21
- DO-178C overview (RTCA): https://www.rtca.org/do-178/
- Link 22 / NILE: https://www.link22.org/