EASA Draft Sets V2X Air Control Interoperability Rule

On June 5, 2026, EASA released a draft interoperability certification framework for V2X Air Control systems that would make certification mandatory from Q2 2027 for eVTOL aircraft, unmanned traffic management platforms, and ground V2X base stations entering EU UAM airspace. For manufacturers, platform providers, test and certification service participants, procurement teams, and export-facing suppliers, the development is worth close attention because it signals a possible shift from technical compatibility being a design preference to becoming an access condition tied to market entry, delivery readiness, and compliance documentation.

What the draft framework explicitly sets out

EASA published the draft document titled V2X Air Control System Interoperability Certification Framework with reference EASA.NPA.2026-07 on June 5, 2026. According to the draft, mandatory interoperability certification is proposed to apply from Q2 2027 to all eVTOL aircraft, unmanned traffic management platforms, and ground V2X base stations entering EU UAM airspace. The draft specifically requires support for the ETSI TS 103 675 V1.2.1 protocol stack. It also states that China’s GB/T 42793-2023 is accepted as one of the equivalent testing bases.

Where the operational impact is most likely to appear

For aircraft and hardware manufacturers, technical compliance may move closer to market access

Analysis shows that eVTOL makers and suppliers of ground V2X equipment may be among the first directly affected if the draft proceeds in its proposed form. The reason is straightforward: the draft links interoperability certification to entry into EU UAM airspace. In practical terms, this could affect product configuration, protocol support, verification planning, technical file preparation, and pre-delivery acceptance work. What deserves closer attention is whether existing designs already support ETSI TS 103 675 V1.2.1, and how internal test evidence aligns with certification expectations.

For UTM platform providers, software architecture and validation records become more exposed

Providers of unmanned traffic management platforms may face impact not only at the product level but also in software integration, interface management, and documentation control. From an industry perspective, interoperability requirements in this type of framework usually place attention on how systems communicate, how protocol support is demonstrated, and how test results are presented for review. Even though the draft summary does not provide detailed execution procedures, platform operators and developers should already recognize that system updates, interface compatibility checks, and version control records may become part of future compliance preparation.

For exporters and cross-border suppliers, certification status may affect bidding and delivery timing

For export-oriented companies supplying aircraft systems, communication modules, base-station equipment, or related integration services into the EU UAM chain, the main issue is not only technical adaptation but also transaction timing. Analysis shows that once interoperability certification becomes a formal access condition, buyers may begin to reflect that requirement earlier in procurement specifications, qualification reviews, and delivery terms. This could influence contract negotiations, tender document responses, conformity statements, test report preparation, and shipment scheduling, especially for products intended for projects with fixed launch windows.

For testing and certification-related service participants, equivalent testing language creates a practical reference point

The draft’s acceptance of GB/T 42793-2023 as one of the equivalent testing bases is notable for testing-related participants and suppliers already working with that standard. Observably, this does not remove the need for further verification of certification pathways, but it does suggest that some existing technical testing work may have relevance in future compliance preparation. For companies serving multiple markets, this may matter in test planning, evidence reuse, and discussions with customers over whether current reports and technical records can support later certification workflows.

What companies should watch before the rule hardens

Review protocol support at product and subsystem level

Companies with products intended for EU UAM applications should closely review whether current aircraft, platform, or ground-station designs support ETSI TS 103 675 V1.2.1 as specified in the draft. If support is partial, under development, or dependent on optional modules, that gap may later affect conformity assessment, integration testing, or customer acceptance.

Check whether existing test evidence can be mapped to future certification needs

Because the draft accepts GB/T 42793-2023 as one of the equivalent testing bases, companies that already use that standard should assess whether their existing reports, laboratory records, interface verification results, and technical descriptions are organized in a way that can support future certification review. This is not the same as confirmed acceptance for all use cases, but it is a practical document-control issue worth addressing early.

Prepare for procurement and tender language to change ahead of formal enforcement

What deserves closer attention is that market documents often move before final enforcement dates. Procurement teams, sales teams, and bid managers should watch for updates in customer specifications, supplier qualification forms, compliance declarations, and delivery conditions referencing interoperability certification, the ETSI protocol stack, or equivalent test standards. Even while the framework remains in draft form, commercial documents may begin to reflect the expected direction of compliance.

Track official wording as the draft moves toward execution

The current information does not provide final implementation details, detailed procedures, or final certification interpretation. For that reason, companies should keep monitoring later official wording, execution guidance, and any clarification on how certification applies across equipment categories, software platforms, and installed base upgrades. This is especially important for businesses making design freeze, sourcing, or shipment commitments tied to 2027 schedules.

Why this should be read as a compliance signal, not yet a closed outcome

Observably, this development is more important as a rule-direction signal than as a fully settled compliance endpoint. The draft clearly points to a future model in which interoperability is treated as a certifiable condition for access to EU UAM airspace, and it identifies a named protocol stack plus an equivalent testing reference. At the same time, analysis shows that the market still needs to watch how the draft is finalized, how certification scope is interpreted in practice, and how procurement and project documentation begin to incorporate the requirement.

How to read the current stage of the change

At this stage, it is more appropriate to understand the draft as an early but concrete execution signal. It does not yet confirm every operational detail, but it is specific enough to affect compliance planning, technical review, and customer communication for companies tied to eVTOL systems, unmanned traffic management platforms, and ground V2X infrastructure. A rational reading is that businesses should neither treat it as a finalized result nor ignore it as a distant policy discussion.

Basis of this article and what still needs verification

This article is generated based on the user-provided news title, event date, and event summary. For developments of this kind, commonly relevant source types include official regulatory announcements, publications from supervisory authorities, standards organization documents, industry association updates, trade authority information, and reporting by authoritative media. No specific official source link was provided in the input, so the exact official publication link still needs to be verified on an ongoing basis. Further observation is also needed on follow-up policy details, certification interpretation, tender document changes, industry feedback, and how companies implement the requirement in practice.