Skip to content
Use case 025

Air Traffic Controller Workstations

A deployment concept for air navigation service providers, aviation authorities and control-centre integrators.

Deployment concept · Suitability unverified
Rail, Aviation, Maritime and Logistics

Why this environment matters

For air traffic controller workstations, the system presents surveillance, flight-plan, weather and communications information to controllers. The risk extends beyond a conventional endpoint: malware, data corruption or interface failure can degrade situational awareness during time-critical traffic management. A NØNOS deployment concept would treat every software component, data source and device interface as separately authorised rather than assuming that anything running on the host should be broadly trusted.

The security challenge

Transport systems often operate continuously, depend on specialised protocols and must preserve safe fallback behaviour while interacting with many operators, contractors and external data sources. In air traffic controller workstations, the decisive risk is that malware, data corruption or interface failure can degrade situational awareness during time-critical traffic management. Even strong perimeter controls may not help once authorised software, a vendor tool or a valid user session has been compromised. Internal permission boundaries must remain enforceable after initial access.

How the capsule model could help

For this system, NØNOS could provide a hardened operator environment with signed display and communications capsules, controlled peripherals and rapid restoration to a known state. The design would combine signed operational software, compartmentalised protocol handlers, attested operator sessions and least-privilege device access. The intended result would be a set of small trust boundaries instead of one large operating environment where every service inherits broad ambient access.

Separate address spaces and capability checks can limit cross-process reach. They cannot stop harmful use of legitimate permissions, prove AI decisions correct or substitute for domain-specific safety controls.

Deployment requirements

NØNOS would need to sit beside, or be engineered into, existing certified systems without weakening deterministic behaviour, fail-safe modes, independent protection or operator procedures.

Current public-beta limitations, hardware support and application availability must be assessed before any pilot. Neither this use case nor an industry source establishes NONOS certification or a current customer deployment.

Who could buy or integrate it?

  • Air navigation service providers purchasing controller environments
  • ATM vendors integrating workstation platforms
  • Control-centre integrators delivering operational system upgrades

Industry examples: Thales, Indra. These are research prospects, not represented as NONOS customers, partners or endorsers.

Opportunity research

Separate the market from the model.

Published industry benchmark
US$8.64 billion

Air traffic management

Global · 2023 · annual market estimate

Air traffic management systems and services, including equipment beyond controller workstations.

Modelled global devices
10K–240K

Candidate OS endpoints

Hypothetical planning range · 2025

Low, hypothetical planning assumptions. Hardware eligibility, procurement and adoption remain unverified.

Illustrative annual licensing
$1.5M–$144M

USD / year at full model coverage

Device scenario × assumed US$150–$600 per device / year.

Not a revenue forecast, announced price or measured serviceable market.

Device calculation

Hypothetical global planning range, 2025 scenario: assume 1,000–4,000 air traffic towers, approach units and en-route centers × 10–60 candidate OS endpoints per site/asset = 10,000–240,000 endpoints. Counting unit: controller position and supporting operational workstations. Site/asset counts and endpoint densities are author assumptions, not a measured installed base. Coverage is limited to the defined equipped subset; includes all candidate endpoints within that assumed subset. Hardware eligibility, certification, adoption and achievable NØNOS share are unverified; overlaps other cases.

Air traffic management market report ↗

Context only, inherited market research; not a device/site denominator. Original monetary-market scope and geography are preserved in benchmark. This source does not establish the assumed worldwide site count or endpoint density.

How to interpret the figures

Adjacent or broader commercial market benchmark; not the NØNOS OS market, licensable-device count or revenue forecast.

Modelled candidate endpoints × assumed annual USD per-endpoint price. Price is an author assumption, not a vendor quote. Full-range mathematical scenario only: not a revenue forecast or TAM; excludes adoption timing, procurement, certification, support costs, channel economics and attainable market share. Case totals overlap and must not be added.

Inherited research compiled 13 Sep 2026; publisher estimates, not independently audited.

Read the full methodology

Explore NONOS

Choose your
NONOS experience.

Discover the platform for your organisation or explore the software.

You can reopen this chooser from the footer at any time.