_Part three of No Blank Screens, a series on FIDS resilience: what happens to airport displays when something fails, and how to keep passengers correctly informed anyway._

TL;DR

• A power cut is the one failure display software cannot survive. Fault isolation and local failover keep FIDS screens accurate when systems break. Neither helps when the screens have no electricity.
• The passenger's phone is the only screen in the terminal with its own power and its own connection. Pocket Flights uses it, reached by scanning a QR code, with no app to install and no account to create.
• Passengers keep seeing the same information the boards were showing. Pocket Flights follows the airport's own FIDS business rules, so the phone and the screens never tell two different stories.
• For the airport, that means fewer people crowding a dead board, fewer staff answering the same question over and over, and fewer passengers missing flights during a disruption.
• It only works if passengers scanned in before the outage. QR codes have to be visible, the link has to be in pre-flight emails, and notifications are opt-in. This is a channel you establish in advance, not one you switch on during an incident.

The first two parts of this series dealt with problems VisionAir FIDS could still work through: FIDS resilience, keeping one fault from becoming every fault, and FIDS offline mode, keeping the screens accurate when the data behind them stops arriving. This third part is about the one failure it cannot, and about Pocket Flights, which exists precisely because that failure has nothing to do with software.

The power goes out, and the screens themselves have nothing to run on. Not frozen, not stale - gone. However good the architecture behind them, a display with no electricity is not a display.

This is the scenario every other answer in this series has quietly assumed away. It is also exactly the one that produces the photograph that ends up on social media: a dark terminal, a crowd of passengers with nowhere to look for information, and a gate agent answering the same question a hundred times over.

At this point, resilience stops being a software problem. No amount of architecture fixes a screen with no power, so the answer has to come from somewhere other than the screen.

Why the fix for a dead screen isn't a better screen

Pocket Flights puts a passenger's flight information directly on their own phone, the one thing in that dark terminal that still has power and its own connection to the outside world. A QR code, a scan, and it is there. No app to install, no account to create, and no personal data to hand over.

The same information that would normally be on the screen above their head is now in their hand instead. Passengers can opt in to notifications for gate changes, delays, and boarding, and those run only for the duration of their flight, so nobody is signing up to be marketed to later.

And it is not a separate system telling a separate story. Pocket Flights follows the same business rules as the airport's FIDS. If the airport shows the gate one hour before departure on its screens, the phone does the same. Same rules, same information, different surface.

That is the whole idea. The screen was never the point. The information was. Move the information somewhere that does not depend on the terminal having power, and the outage stops being a communication failure while remaining very much a power failure.

What a dark terminal looks like with no other channel

Picture the alternative. A few hundred passengers, no screens, one gate agent, and a growing queue of people asking the same three questions. That is what happens by default when a terminal loses power, and there is nowhere else to look. Stressful for passengers and exhausting for staff trying to manage a crowd with information they cannot easily broadcast.

With Pocket Flights already in passengers' hands before the outage happens, that scene does not play out the same way. People are not clustering around a dead screen because there is nothing else to check. They are looking at their own phone, which is still telling them what they need to know. Staff are not answering the same question over and over, so they are free to manage the situation rather than narrate it.

And fewer passengers miss a flight for the simple reason that nobody could tell them anything.

Worth being straight about the condition attached to that. It only works for passengers who have already scanned the code, which means the code needs to be visible somewhere other than on the screens themselves. A QR code that only lives on a FIDS display goes dark with everything else. It is a channel you establish in advance, not one you switch on during an incident.

Three failures, three answers

This series has been about one question asked three times: when something breaks, do the screens keep telling passengers the truth? Three failures, three answers.

An architecture that keeps one fault from becoming everyone's fault. Tools that let a person keep information flowing when a feed cannot. And a channel that does not care whether the terminal has power at all.

None of this promises that nothing will ever go wrong. It promises that a bad day for your infrastructure does not have to become a bad day for your passengers, or for your reputation.

A blank screen is not an outage. It is a decision: the decision not to have a backup. VisionAir FIDS and Pocket Flights are built so that decision never has to be made.

Want to know what your passengers would see if your terminal lost power tomorrow? Talk to us about VisionAir FIDS and Pocket Flights.

No Blank Screens: A Practical Guide to FIDS Resilience

1. FIDS Resilience: What Happens When One Component Fails

2. FIDS Offline Mode: What Happens When the Flight Data Stops

3. When the Screens Lose Power: Reaching Passengers Without a Display _(you are here)_

About AirportLabs

AirportLabs builds cloud native software for airport operations. Our products span the core operational stack, including SkyCore AODB, Allegra RMS, VisionAir FIDS, and AirportLabs Billing, as well as ground handling and airport collaboration tools. They are designed to work as separate systems or as a connected suite, which is why a FIDS conversation at AirportLabs usually ends up being a conversation about the data underneath it.

Written by Bianca Făgăraș, Product Manager, VisionAir FIDS & Pocket Flights.