Multi-Airport City IROPS: Why Your Contingency Plan Needs to Account for More Than One Runway

The hidden complexity of operating in multi-airport cities

Most IROPS contingency plans are designed with a single station in mind. One airport, one hotel pool, one ground transport arrangement, one operations contact. That logic is clean and manageable until a disruption occurs in a city where your airline operates across more than one airport.

Multi-airport cities are not unusual in Europe. London, Paris, Milan, Stockholm, Madrid and several others have two or more commercial airports serving distinct catchment areas, handling different route mixes, and operated by separate airport authorities. When weather, ATC restrictions, or a technical event affects the region, all of those airports can be impacted at the same time. And the IROPS response that works at a single station can collapse quickly when the problem spans the whole city.

Why single-station planning fails at scale

The structural problem is straightforward. Hotels near any one airport are a finite resource. When disruption hits multiple airports simultaneously, airlines and handlers at each site start drawing from overlapping hotel markets without any coordination between them. What looks like adequate capacity at a single station becomes a shortage across the city within hours.

Ground transport adds a second layer of difficulty. Coach and taxi availability that is sufficient for one airport operation gets absorbed quickly when drivers and vehicles are being called from multiple directions at once. Response times stretch. Transfer windows close. Passengers who should have reached accommodation by midnight are still waiting at 2am.

On the communication side, the problem is ownership. In a well-prepared single-station plan, it is usually clear which team handles passenger notifications, which contact manages hotel allocation, and which person is accountable for crew positioning. Across two airports in the same city, those lines blur. Stations that normally operate independently suddenly need to coordinate in real time, often without a pre-agreed protocol for doing it.

The specific risks operations managers need to plan for

Before the next multi-airport disruption, there are several failure points worth examining explicitly in your contingency planning.

• Hotel pool overlap: Do your station teams know which hotels are shared across airports in the same city? If both teams call the same property at the same time, one of them will be left without rooms at the worst possible moment.
• Ground transport routing conflicts: Coaches dispatched from different airports to hotels in the same city centre can end up in direct competition for the same vehicles and drivers. Without a single point of coordination, this is nearly impossible to manage reactively.
• Crew compliance across stations: Crew rest requirements do not pause because two airports happen to be in the same metropolitan area. If crew members are stranded at different sites, tracking duty hours and ensuring compliant rest becomes significantly more complex. The operational risk this creates is one airlines routinely underestimate.
• Passenger information inconsistency: When two stations are managing independently, passengers from the same disrupted service who have been diverted or rebooked across airports often receive different information. That inconsistency drives complaint volume and erodes trust faster than the disruption itself.
• Regulatory exposure: EU261 obligations do not vary based on the complexity of your network. Duty of care applies from the moment the disruption is confirmed, regardless of whether your station teams are overwhelmed coordinating across sites.

What a workable multi-airport plan actually looks like

Planning for multi-airport disruption is not fundamentally different from other IROPS preparation. It requires the same structured thinking applied to a more complex geography.

The starting point is mapping the resource landscape honestly. Which hotels in each city are accessible to passengers from both airports? What is the realistic transport time from each airport to those properties? Which ground transport suppliers have the fleet and flexibility to cover multiple pickup points in the same metropolitan area? These are questions that need answers before an event, not during one.

Coordination protocols need to be explicit and tested. If a city-wide disruption happens overnight, who is the single decision-maker with authority across all affected stations? How do the two or more station teams share information in real time? What triggers escalation to central operations? Airlines that leave these questions open tend to find their teams improvising in conflicting directions under pressure.

Pre-negotiated agreements with accommodation and transport suppliers should reflect the multi-airport reality. A supplier contract that covers one airport in a city may not obligate that supplier to respond across the market. Passenger accommodation arrangements that work well for isolated events often need different terms to be reliable at city-wide scale.

Finally, scenario testing matters. Running a tabletop exercise for a single-station cancellation is useful. Running one that simulates a weather event closing or severely disrupting two airports in the same city on the same night is more revealing. The gaps in your plan tend to show up in that second scenario in ways that the first one never surfaces.

Where an experienced IROPS partner makes the difference

One of the practical advantages of working with a provider that operates across multiple countries and markets is that the hotel and transport network already exists at city level rather than airport level. A supplier with established relationships across a metropolitan area can respond to a multi-airport event from a single point of coordination rather than requiring your station teams to manage competing calls to the same properties.

For airlines operating across European cities with complex airport structures, this kind of coverage is not a luxury. It is the operational infrastructure that makes a city-wide disruption manageable rather than chaotic. Duerming’s end-to-end IROPS management is built around exactly this kind of multi-site coordination, with local presence and pre-arranged capacity that covers disruptions wherever they land in the network.

The airlines that handle multi-airport events well share one common characteristic. They thought about the coordination problem before it became active. The ones that struggle are usually the ones whose plan was written for a simpler geography and never updated to reflect where they actually fly.