Recover the connections.
One aircraft fault at dawn can strand hundreds of passengers by evening. Replay a regional airline's day on the map, see how the disruption spreads through aircraft rotations and hub connections, then apply a recovery plan found by searching tens of thousands of alternatives.
- Hub
- Sofia (SOF)
- Fleet
- 10 × A320
- Flights
- 60 legs · 20 cities
- Passengers
- 8,574
- Connecting
- 776
Hover an aircraft or a bar in the rotation chart for flight details.
Rotations, as flown.
Each row is one aircraft. Outlines mark the published schedule; filled bars are what the simulation flew. When a rotation moves to another aircraft, its new bar is ringed. Delays travel along a row, because an aircraft cannot leave before it has arrived and turned around, and they jump between rows through connecting passengers at the hub.
Three ways to recover.
The solver works from the moment the disruption is known. Flights already airborne are fixed. Everything else can change: rotations can be exchanged between aircraft at the hub, a round trip can be cancelled and its passengers re-booked, and a departure can be held for up to 45 minutes to protect a connection. Each candidate plan re-flies the whole day and re-books every passenger before it is scored.
What runs underneath.
Day propagation
Aircraft events are processed in time order. A departure waits for its schedule, the aircraft (35 min turn out-station, 40 min at the hub), any hold, an ATC slot and, during storms, a hub runway slot handed out first come, first served. One full day is evaluated in about a third of a millisecond.
Passenger re-accommodation
Every booking is checked against the flown day: a missed 45-minute connection or a cancelled flight is re-booked onto the next flight with free seats, splitting groups if needed. Anyone left without a seat flies the next morning and gets a hotel.
Objective
Search
Simulated annealing over four move types: exchange the remaining rotations of two aircraft, move or exchange a single rotation, cancel or reinstate a round trip, and set a hold. Around 24,000 complete days per option, with periodic restarts from the best plan and a clean-up pass that removes changes that no longer pay.
What this model leaves out
The airline, schedule and bookings are invented; airports and distances are real. Crew duty limits and crew pairings, maintenance slots, aircraft type differences, interline re-routing on other carriers, fares and spill are not modelled. EU261 is applied by distance band and arrival delay only, without extraordinary-circumstance exemptions. A production system would add crew recovery and read the live schedule and bookings.
Recover your network.
We build schedule recovery and disruption models around your fleet, crews and passengers, and connect them to the data your operations control centre already has.
The simulation could not be loaded. Reload the page to try again.