ANSP Revenue Recovery: The 2% Leakage Every Air Navigation Authority Is Missing

Executive Summary

ANSPs globally bill approximately US$30 billion annually in route charges. Eurocontrol alone collects around US$14 billion. The remainder flows through a patchwork of regional systems, bilateral agreements, and the IATA Clearing House.

Behind these headline figures sits a quieter problem: between 2.5% and 6% of billable revenue is never captured. Not because operators refuse to pay — but because the systems ANSPs rely on to identify, calculate, and invoice chargeable movements were never designed to be revenue systems at all.

This whitepaper quantifies that gap, explains why it persists, and outlines a non-invasive, cloud-based alternative that recovers revenue without touching the ATM system, without capital expenditure, and without operational risk.

Airports face the identical structural gap one layer down — landing, parking, and terminal navigation charges reconciled against systems built to manage stands and slots, not to bill anyone. Everything in this whitepaper applies equally to both.

1. The Structural Problem

An ANSP's Air Traffic Management system exists for one purpose: safely separating aircraft. It is a safety-of-life system, subject to the most rigorous certification and change-control regimes in civil aviation.

It was never designed to:

• Calculate distance-based charges across FIR boundaries using great-circle or Vincenty geometry
• Apply differentiated tariff structures to airlines, general aviation, and exempt categories
• Validate tail-level Maximum Take-Off Weight against a certified aircraft registry
• Maintain a current register of aircraft owners, lessors, and billing entities
• Issue invoices within the billing window
• Manage the lifecycle of a disputed invoice
• Chase 500+ operator accounts for late payment
• Integrate natively with a financial ERP

These are finance functions. They belong in a finance system. But in most ANSPs, they are bolted onto the ATM system as a post-hoc module — or worse, managed across spreadsheets and institutional memory.

The result: the operational system is asked to do a job it was never designed for, and the finance team carries the consequences.

Airbnb doesn't own a single hotel room. Amazon doesn't own most of what it sells. What they own is the customer relationship and the data pipeline that turns activity into revenue — the same asset every ANSP already has, and has never been asked to treat as one.

2. Why "Breaking Into the ATM System" Is Not the Answer

When ANSP CFOs raise billing accuracy with their ATM vendors, the conversation follows a predictable pattern. The vendor proposes a custom billing module. The cost runs into seven figures. The timeline runs into years. Every change requires extensive regression testing and safety certification, because the system being modified is safety-critical.

What the ANSP receives at the end of that process is a module that handles basic invoicing. It does not deliver:

• A CRM workflow for managing customer relationships
• A self-service portal for operators
• Dispute resolution tooling
• ERP integration
• What-if analysis for tariff and capacity planning
• CANSO-aligned KPI reporting

The category error is structural. You cannot retrofit a finance system onto a safety system — not economically, not operationally, and not without exposing the ANSP to ongoing certification risk every time the billing logic needs to change.

3. The Anatomy of Revenue Leakage

The fliteX proprietary revenue recovery model quantifies where revenue is lost, and how it can be recovered.

4. The Industry Benchmark Framework — and Its Blind Spot

CANSO's Global Air Navigation Services Performance Report provides the industry-standard framework for measuring ANSP performance. Its core KPIs are cost-efficiency and productivity measures — the metrics boards, regulators, and finance teams already know.

These metrics measure the efficiency of the operation and the yield of the revenue you do book. They are the right framework for boards, regulators, and comparative benchmarking.

But they do not measure revenue that never reaches the P&L. Missed flights, MTOW errors, and operator identification failures occur before the revenue is recorded. They are invisible in the CANSO framework.

A modern revenue management platform must report against both frameworks: the CANSO KPIs your board expects, and a proprietary model that quantifies what the industry standard cannot see.

5. Case Studies: What ANSPs Have Achieved

The following case studies are documented deployments of the Flightyield system — a joint CANSO / SITA initiative — and represent the closest real-world analogue to the fliteREV model.

What every deployment had in common: missed flights · incorrectly applied policies · delays in invoicing · disputes · long delays in payment — and in many cases, no payment at all.

The pattern is consistent across geographies and ANSP sizes: when billing moves from manual to automated, revenue capture improves, disputes fall, and cash conversion accelerates.

6. The fliteREV Model: Non-Invasive, Cloud-Native, Opex-Only

The methodology behind this model — identifying, validating, and calculating chargeable events across route, terminal, and ancillary charge types, end to end, from raw operational data through to invoice — is the subject of a pending fliteX patent application.

Core Capabilities

Automated Flight Processing — Seamless integration with any ATC/ATM provider. Automated data collection and validation of all chargeable events.

Intelligent Billing Engine — Handles any tariff, discount, or incentive model. Accurate MTOW validation and weight factor calculations.

Advanced Analytics & AI — Predictive analytics, revenue forecasting, business intelligence dashboards, and what-if modelling for traffic, capacity, and sector staffing.

Customer Relationship Management — Operator self-service portals, dispute management, and proactive customer communication tools.

CANSO KPI Reporting — Board-ready and regulator-ready metrics, out of the box.

ERP Integration — Clean, structured data delivered to your finance system — every time.

The Commercial Model

No capital expenditure. You don't buy software. You don't buy licenses. You don't buy hardware. No three-year capital project. No vendor lock-in.

Pay-as-you-use. A simple data handling fee per flight processed, plus a revenue recovery reward tied to the additional revenue we recover for you.

Aligned incentives. If we don't recover revenue for you, you don't pay for the recovery.

Cloud-based and secure. Accessible from anywhere, with enterprise-grade security.

Non-invasive. We do not touch your ATM. We sit alongside.

7. The Small ANSP Alternative to the IATA ICH Shortcut

Smaller ANSPs frequently rely on the IATA Clearing House (ICH) Enhancement & Financing (E&F) Service to settle route charges. The model is simple: submit a billing spreadsheet, pay an administrative fee (typically 2–5%), and receive settlement within a week — without chasing individual IATA member airlines and without facing disputes.

This is a legitimate and effective model for what it does. But it comes with three structural limitations:

First, the fee is a permanent revenue deduction. Two to five percent of billable revenue leaves the ANSP every month, forever.

Second, the ICH settles what you submit. It does not validate whether your submission is complete or correct.

Third, the hard work still sits with the ANSP. Spatial calculations, tail-to-owner mapping, MTOW validation, and exemption handling all happen before the spreadsheet reaches IATA.

For smaller ANSPs, fliteREV offers a lower-cost, no-risk alternative. By connecting directly to raw AMHS and FDPS data, fliteREV treats operational data as truth data — not a spreadsheet, not a manual extraction.

The result: not a single flight is missed, every chargeable movement is captured, every MTOW is validated, every operator is correctly identified, and the 2–5% IATA fee is retained by the ANSP.

For a small ANSP, this is not just cost savings — it is revenue recovered that was never being captured at all.

8. What-If Analysis: Finance as a Strategic Function

Once revenue data is decoupled from the ATM system and living in the cloud, it becomes queryable and modellable. This enables a capability that has not previously existed in ANSP finance: AI-driven what-if analysis.

Typical questions the platform is built to answer:

• What happens to revenue if traffic grows 8% in the summer season?
• What is the revenue impact of a new charging formula for overflights?
• How does staffing cost per sector change under a different shift pattern?
• What is the revenue recovery from tightening MTOW validation on a specific fleet?
• What is the breakeven traffic volume for a new sector configuration?

For the first time, the CFO has the same quality of business intelligence the COO has always had in the operations room.

9. Operational Resilience: Why Non-Invasive Matters

The Swanwick Air Traffic Control Centre crisis of 2023 — and the same fault class resurfacing in September 2026 — demonstrated a structural vulnerability that affects every ANSP and airport, on every continent: when billing depends on the operational system, an operational failure becomes a revenue failure.

In a non-invasive, cloud-based CRRM model:

• Operational data is mirrored securely in the cloud
• Billing continues even if the ATM system is disrupted
• Customer communication is decoupled from the operational system
• Finance retains an independent view of the business

For an organisation with a single income stream, this is not a nice-to-have. It is existential.

10. The Ask

We are not asking ANSPs to replace their ATM system. We are not asking for a capital commitment. We are asking for a conversation about the revenue cycle.

If your billing data is your most valuable asset, why is it still trapped behind the one system in your organization you can never afford to touch?

These are the questions that keep CFOs awake at night. They are the questions fliteREV was built to answer.

Appendix A — The fliteX Revenue Recovery Model

Appendix B — CANSO Performance KPI Framework

Appendix C — Documented Case Study Outcomes

© 2026 fliteX. All rights reserved. fliteREV is a trademark of fliteX.