eu-LISA compliance for charter airlines: why a backup strategy matters

As Europe advances the rollout of large-scale border management systems operated by eu-LISA (such as EES, ETIAS, and VIS), many charter airlines are reviewing how their passenger data queries are handled in practice.

For most charter operators, eu-LISA queries are processed by their Departure Control Systems (DCS). On paper, that seems sufficient. In reality, there might be some operational gaps worth noting.

Common challenges in standard DCS submissions

Charter airlines rely on Departure Control Systems to send eu-LISA queries for flights arriving from third countries into participating EU territories. However, there are some limitations to this approach, including:

1. No submission confirmation
   DCSs normally do not provide confirmation that the required data was successfully transmitted and accepted by the relevant eu-LISA system. This leaves airlines without proof that their obligation has been fulfilled.
   
   
2. Certification gaps at smaller airports
   Some smaller or regional airport DCS environments may not yet be certified for eu-LISA submissions. In such cases, airlines may need to quickly find alternative compliance pathways.
   
   
3. Ad-hoc routes
   Charter operations often include one-off or ad-hoc flights. If the local DCS is not formally declared by the airline as its authorised data provider for eu-LISA submissions, it cannot be used to transmit the required data—even if it is technically connected to the eu-LISA Carrier Interface. This creates a compliance gap when routes are added at short notice.
   
   
4. Occasional transmission delays or disruptions
   Ground handlers operating DCSs manage a broad range of responsibilities, and there may be instances where regulatory time windows for queries are challenging to meet. In addition, as with any technical interface, DCS connections may occasionally experience disruptions. When a submission is not completed as expected, airlines may need to rely on last-minute manual processes, which can be time-consuming and increase the likelihood of human error.
   

For charter carriers juggling seasonal programs, ad hoc routes, and mixed airport infrastructures, these small factors create an unnecessary compliance risk. As eu-LISA systems expand their application scope, using only one data transmission channel can become more and more challenging. Having a backup option provides additional reassurance and flexibility.

Practical eu-LISA compliance backups for charter airlines

PnrGo has developed two service models to suit different operational needs and budgets for charter airlines. As a certified eu-LISA service provider, PnrGo offers an option that complements existing DCS workflows, improving traceability and continuity for EES queries, and the next stages including ETIAS and VIS.

Both setups are backed by our support team that monitors workflows and provides technical assistance when needed:

1) FULL (fully automated safety net)

The FULL setup is designed for airlines that prefer full automation and continuous coverage.

It includes:

• Automatic queries for all flights from third countries to eu-LISA territories
• Compatibility with DCS submissions—since eu-LISA permits double queries, both systems can run in parallel
• A strong safety net—PnrGo provides a confirmation that queries were successfully sent

This model allows airlines to continue using their DCS while adding a verification and monitoring layer. It reduces uncertainty and creates documented confirmation — without disrupting existing workflows.

2) BACK-UP (cost-effective emergency solution)

For operators with occasional eu-LISA systems exposure or lower traffic volumes, a lighter solution may be sufficient.

The BACK-UP setup provides:

• A cost-effective model for irregular or seasonal operations
• Semi-automated submissions via PnrGo’s system—simply select the affected flight and click “SEND NOW” (no manual web portal or mobile app entries required)
• A fallback solution when a DCS is not certified or temporarily unable to transmit

This approach can serve as an emergency compliance procedure—making it suitable for smaller operators or airlines that need a contingency plan rather than continuous automation.

Why a backup strategy matters

Whether it’s a fully automated data flow or a simple backup plan, having an extra eu-LISA submission pathway strengthens your compliance process and protects your business from unnecessary disruptions. With legal deadlines fast approaching, you can rest assured that your team is fully prepared for the new digital border ecosystem taking shape across Europe.

In this context, duplication is not redundancy—it’s smart risk management.

To learn more about our passenger and crew data compliance solutions, schedule a call with one of PnrGo Sales Representatives.