When the airspace closes, silence is the one thing passengers will not forgive

When tensions between Israel and Iran escalated and airspace across parts of the Middle East started closing to commercial traffic, one thing became clear within hours. This was not going to be a story about which airline handled the operations best. It was going to be a story about which airline handled the silence best, or didn't.

I was working with an airline client at the time, and the operational side of the disruption was, in a strange way, the easier problem. Routes get replanned. Fuel gets recalculated. Ops teams are built for exactly this kind of thing. What ops teams are not always built for is a passenger sitting in a departure lounge at midnight, watching news alerts about missile strikes a few hundred kilometers from where their connecting flight is supposed to fly, refreshing the airline's app for an update that isn't coming.

That gap, between what the airline actually knew and what it had told anyone, is where reputations get made or lost. Not in the delay itself. In the silence around it.

Our job in that window was almost entirely about closing that gap, as fast and as honestly as we could. A few things mattered more than anything else. Speed over polish, since a short, plain update sent within the hour beats a beautifully worded one sent the next morning, every single time. Consistency across channels, so a passenger checking the app, checking Twitter, and calling the support line all heard the same thing, worded the same way, because a mismatch between channels reads as either incompetence or dishonesty, and neither is something you can afford when people are already anxious. And plain language over corporate language, because nobody in a departure lounge at midnight wants to read that the situation is being monitored, they want to read what it actually means for their flight.

We also had to be honest about the limits of what we could say. There were real moments where the airline genuinely did not have a firm answer yet, routes were still being assessed, safety clearances were still coming in, and the temptation in those moments is to go quiet until there's good news. We pushed the opposite way. Say what you know. Say clearly what you don't know yet. Say when the next update is coming, and then actually send it on time. A passenger can forgive uncertainty. What they remember, and what they write reviews about later, is being left in the dark.

There's a version of crisis communication that treats it as damage control, something you do to protect the brand after the fact. That was never how we approached this one. The actual goal was simpler than that: treat every passenger the way you'd want your own family treated if they were the ones stuck in that lounge. The reputation outcome follows from that, it isn't the starting point.

What stuck with me afterward wasn't a metric, though the sentiment numbers did hold up well through the disruption. It was how many people specifically called out the communication itself, not the outcome, as the reason they'd fly the airline again. Nobody was upset that a war closed some airspace. Airlines don't control that. What people remember is whether someone was honest with them while it was happening.

That's the part of crisis communication that's easy to forget when you're deep in the operational details. The crisis itself is rarely the thing that damages a brand. The silence around it usually is.