Connection simulator
Model disruption before it occurs.
Scheduled connection time is not usable connection time. Account for delay and airport processes to reveal the buffer that actually remains.
26% modeled catch probability.
The expected path is 18 minutes longer than the scheduled connection.
The connection is protected as one ticket, but protection does not make the transfer comfortable. Look for a later backup departure.
The estimate treats your likely delay as the center of a distribution and “delay uncertainty” as its spread. It is a scenario model, not live flight tracking or an official airport minimum connection time.
A timeline, not a magic score.
- A
Consume the schedule
Expected arrival delay and the selected airport processes are subtracted from the published layover.
- B
Expose the surviving buffer
The output shows minutes that remain before a practical gate-close allowance.
- C
Price protection separately
A through ticket may offer rebooking protection; a separate ticket usually shifts the exposure to the traveler.
Start from a real question.
Explore the Answer Lab ↗Is 75 minutes enough for a Frankfurt connection?
Fragile when border processing and a concourse change both apply.
41% MODELED CATCH PROBABILITYOpen scenario ↗IST / 060Is a 60-minute Istanbul connection defensible?
Only plausible when the bag is through-checked and no border process is added.
36% MODELED CATCH PROBABILITYOpen scenario ↗JFK → EWRHow risky is a JFK to Newark flight connection?
High-friction unless the layover is deliberately long or overnight.
5H+ DEFENSIBLE MODELED BUFFEROpen scenario ↗FlyPolicy is a decision aid, not a travel agency, airline or legal adviser. Prices and conditions can change before purchase. Verify the final fare and operating carrier on the seller's checkout page.