Airports Collect More Data Than Any App You Use. So Why Do Passengers Still Feel Blind?

A modern airport knows when a passenger checked in, whether their baggage was accepted, where that bag was last scanned, which gate their flight departs from, whether the gate has changed, how long the security queue is, how far they are from the gate, whether their connection is at risk, and whether their aircraft is delayed.

The passenger usually knows almost none of this in real time. They look at departure boards. They refresh airline apps. They ask staff. They stand at baggage reclaim wondering if their bag made the connection, or if it was left behind.

For a CTO, this is not a communication problem. It is a data product problem. The airport already has the intelligence. What is missing is the layer that transforms operational data into real-time decisions for the passenger.

01

The Airport Already Knows More Than the Passenger Does

A typical passenger journey generates dozens of operational signals even before security. The airline knows the reservation, check-in status, seat, connection, and boarding group. The airport knows terminal flows, security queue conditions, gate assignments, gate changes, baggage handling events, and disruption patterns. Baggage systems know when a bag has been accepted, loaded, transferred, and delivered. Passenger flow systems track dwell time, congestion, and movement patterns via Wi-Fi probes, Bluetooth, LiDAR, cameras, and boarding pass reads.

This is a richer real-time context than almost any consumer application can access. A retail app knows what you browsed. A banking app knows your transaction behaviour. A mobility app knows your route. But the airport ecosystem knows something more urgent: whether you will successfully complete a time-critical journey involving identity, baggage, security, gates, aircraft, connections, and border processes. That context is also temporary, expiring the moment you exit arrivals. And it is almost never given back to you while it is still useful.

The issue is not data collection. The issue is data activation.

02

Operational Intelligence Is Not the Same as Decision Intelligence

Most airport data is built around internal control: keeping aircraft moving, allocating gates, processing baggage, managing queues, and coordinating stakeholders. That is necessary. It is no longer sufficient.

The passenger does not need raw operational data. They need interpreted guidance.

They do not need to know that "queue density has increased in Zone C." They need: "Security is taking 14 minutes. You still have enough time, but you need to walk there now."

They do not need to know that a baggage event was logged. They need: "Your baggage has been loaded onto your connecting flight."

They do not need to know the gate changed from A12 to C27. They need: "Your gate has changed. It is now a 13-minute walk from your current location. Boarding starts in 18 minutes."

The airport must stop treating passenger information as announcements. It must start treating it as decision support.

The best navigation systems don't show you the entire road network. They show you the next instruction. The same principle applies to the airport journey, and it is the principle that most airport data products still fail to implement.

03

The Commercial Case: What the Data Says About Dwell Time and Revenue

Global passenger traffic grew 8.2% in 2024. Non-airline revenues, retail, food and beverage, parking, and advertising, account for 36.7% of total airport revenue globally and offset 48% of total airport costs. Despite the passenger recovery, those revenues remain approximately 9% below 2019 levels. Passengers have returned. Commercial performance has not fully followed. The explanation sits partly in the data experience.

A 2024 study published in the Journal of Air Transport Management found that a 10% increase in passenger dwell time is associated with a 5% increase in total non-aviation revenue, including an 8% increase in food and beverage revenue and a 6% increase in retail revenue. The mechanism is not complicated.

At the same time, 72% of airports anticipate increasing IT spend over the next two years, and airport IT investment was estimated at nearly $9 billion in 2024. The strategic question for every CTO reviewing that budget is whether the investment will modernise internal systems, or create a measurably better experience for the passenger generating the revenue those systems are meant to support.

04

What the Journey Should Actually Feel Like

The future airport experience should not be a sequence of disconnected touchpoints. It should behave like a single intelligent interface that follows the passenger from check-in to baggage reclaim. Most of the data to build this already exists. What follows is not a product vision, but a description of what becomes possible when operational systems are connected to passenger-facing channels.

This is not speculative. The data already exists across fragmented operational systems. What does not yet exist, in most airports, is the orchestration layer that connects those systems and translates their events into passenger-facing guidance in real time.

05

The Baggage Test: When Passengers Trust an AirTag More Than the Airport

Baggage is the most concentrated example of the data gap, and the most uncomfortable one for airport technology directors.

SITA reported that the global baggage mishandling rate fell to 6.3 bags per 1,000 passengers in 2024, down from 6.9 the year before. Progress. But 33.4 million bags were still mishandled globally. That is not just an operational problem. It is a trust problem that accumulates silently across millions of journeys where passengers received no information and assumed the worst.

IATA Resolution 753 mandates tracking at four key custody points: when the bag leaves the passenger, when it is loaded, when custody transfers during connection, and when it is returned. SITA's Bag Journey platform already provides end-to-end real-time tracking with APIs that allow that status to be surfaced in any passenger-facing application. The data infrastructure for full baggage visibility largely exists. The question is whether airports are choosing to activate it at the passenger layer.

06

The Missing Layer: A Passenger Data Orchestration Platform

Airports do not need a new standalone application. They need a passenger data orchestration layer: a platform that sits between operational systems and passenger-facing channels, translating live events into personalised, actionable guidance.

Its role is not to replace existing systems. It is to connect them, apply business rules, manage consent, and surface the right information to the right passenger at the right moment, whether through an app, SMS, WhatsApp, digital signage, or a kiosk.

A useful passenger data layer must answer four questions in real time: Who is the passenger? What is their current journey status? What risk or opportunity has just changed? What is the next best action? If the airport cannot answer these four questions, it is not delivering real-time UX. It is displaying information.

The integration stack that works in production: an API gateway normalising all sources into a common event schema using ACI ACRIS as the target standard, with Apache Kafka for larger deployments and MQTT for mid-sized airports. Read-only AODB access is non-negotiable, as requesting write access creates change management resistance that has derailed otherwise sound integration projects.

07

When Bad Data UX Becomes Operational Debt

In software, a poor user experience generates support calls, churn, and abandoned carts. In airports, poor data experience generates queues, repeated questions, missed connection anxiety, staff overload, and compressed commercial time. The mechanics are the same. The budget line is not.

The cost of a poor passenger data experience does not usually show up in a single budget line. It shows up across customer service, operations, baggage claims, retail performance, and reputation. Which is why it is consistently underestimated, and why it is rarely the thing that triggers the project budget conversation.

Every missed message becomes operational work. Every confusing instruction becomes passenger stress. Every fragmented system becomes a visible service failure. Real-time passenger data should not be treated as a marketing feature. It is operational cost reduction.

08

Privacy: The Line Between Assistance and Surveillance

Anonymous passenger flow analytics, counting people in zones, measuring queue density, and tracking dwell patterns without individual identification, sits under GDPR Article 6(1)(f) legitimate interest with a documented balancing test. No DPIA required. The moment you link a count to a boarding pass identity, you cross into Article 35 territory and need a stronger legal basis, explicit consent processes, and a full impact assessment before deployment.

The design principle that resolves this is simple: use the least amount of passenger data necessary to provide the next most useful action. Most of the highest-value use cases, queue guidance, gate alerts, and dwell optimisation, can be delivered on aggregated or voluntarily shared data. Personalised messaging should be opt-in, transparent, and clearly valuable to the passenger.

Privacy is not the enemy of personalisation. Poor governance is. A well-designed airport data experience should feel like assistance, not monitoring.

Passengers will share data when the value exchange is obvious, permission is transparent, and control is real. They will share location when it gets them faster processing. They will share identity signals when it surfaces their baggage status. The data contract that enables this is not a legal formality, but the UX foundation on which trust is built.

09

Three Principles Every Airport CTO Should Take Away

1. Stop treating data as information. Treat it as guidance.

Passengers do not need more data. They need fewer moments of uncertainty. The goal is not to surface every operational update, but to convert operational events into passenger decisions: walk now, wait here, use this checkpoint, your baggage is on board, your connection is at risk, your route has been recalculated. The best airport data products will look less like dashboards and more like navigation systems.

2. Build around the journey, not the stakeholder.

The passenger's journey crosses airlines, airport operations, ground handlers, security, border control, retail, and baggage teams. The passenger experiences it as one system. When each stakeholder communicates separately, the passenger feels that fragmentation as a single failure, regardless of which system caused it. The CTO's role is to create the integration layer that makes the experience coherent. This does not mean any party owns all the data. It means the passenger receives a reliable operational narrative from departure to arrival.

3. Measure the data experience in business outcomes, not in notification open rates.

Real-time passenger data should be evaluated against operational and commercial metrics: fewer calls to customer service, fewer baggage status enquiries, reduction in missed connections, better queue distribution, longer dwell time, higher retail and F&B conversion, fewer complaints during disruptions, lower cost per passenger served. If a data product does not change passenger behaviour or operational costs, it is not yet a commercial product. It is still a pilot.

Airports already have the data. The question is whether the passenger will have it in time.

They already know the flight. The gate. The queue. The baggage status. The connection risk. The distance to travel. They know when a journey is about to fail.

When passengers trust the system, they stop asking questions. When they stop asking, the team can focus on exceptions. When passengers stop worrying, they move better. When they move better, they stay longer. When they stay longer, they spend more. And when a disruption hits, they judge the airport not by what went wrong, but by how the system helped them recover.

The first airport to make its data genuinely accessible to passengers will not only improve the travel experience. It will change the economics of the terminal. For more on how information architecture shapes passenger behaviour at the gate level, and how infrastructure-level design decisions compound over time, the arguments connect.