How layovering works out your time.

A plain account of how the planner gets from two flight times to a plan, and what it checks along the way.

Connection Intelligence

What we are building

What it does
The decision layer that checks airside demand against the real window and routes only what fits.

Schedules
A live schedule reading uses a named source and check time; manually entered times remain manual.
Allowances
The planner holds back about 45 minutes for arrival and about 60 to be back.
Changes
A change of terminal or airport, or an overnight stay, is shown when the schedule data has it.
Unknowns
When something is not known, such as a gate, the plan says so and suggests what to check.

These times are Sample, not a live schedule or a checked terminal. A real reading needs its own source and check time.

01
Start from the schedule
Use returned flight times when a schedule source supplies them. Manually entered times remain manual.
02
Hold time back
About 45 minutes for arrival and about 60 to be back, shown as about.
03
Show what changes
Terminal, airport and overnight changes appear when the schedule data has them.
04
Keep the unknowns visible
When something is not known, such as a gate, the plan says so and suggests what to check.

Sample connection

Arrival and the way back are held back. The rest is yours. Flight times are local times.

Every figure in a plan shows how it was reached.

Is this live?
Not yet. Atlanta is our first airport, and what you see here is a sample plan.
Can I try it?
Yes, with your own flight times in the planner. Anything you see here is a sample.

45 minutes

held back for arrival by default, and about 60 to be back, until an airport's own times are used.

Source: layovering default planning allowances.

We are early, and Atlanta is our first airport. Anything marked Sample is illustrative. Partner operations