01 / Trunk route
Select a trunk route
Pick the leg the network is built around. Here EY 0099 / EY 0100, Abu Dhabi to Lisbon, five days a week. It is the spine every connection is measured against.
Connection Designer
Test a schedule change before you publish it.
Connection Designer reads a sample week, applies your connection rules, and shows which markets a schedule connects, what an alternative gains or loses, and which timings work best. Below, one real case: one Abu Dhabi to Lisbon retime, seven markets gained.
For airline and airport network planning, schedule planning, partnership teams, and aviation consultancies.
AUH → LIS
Trunk route
Connections at AUH
Window 1:00 to 4:00
Mon to Thu, Sun
+5′
was 02:05 → 07:25
Mon to Thu, Sun
−15′
was 09:15 → 19:45
MarketInboundOutbound
+ 22 further markets in the sample week
MarketsBaselineOptimised
Two-way markets2429
Gained+7
Lost−2
Net vs baseline+5
+ BAHBahrain1:055×
+ KWIKuwait City1:055×
+ MELMelbourne1:104×
+ 4 further markets gained
− KHIKarachi4:105×
− ISBIslamabad4:055×
Optimised: +5 markets against baseline
Trunk route
Two-way market
Gained by retime
Gained vs baseline
Lost vs baseline
Grow a network from a single trunk route
One leg, Abu Dhabi to Lisbon. Connection Designer reads every onward flight at the hub, then shifts the trunk within operational tolerance to turn near-misses into sellable markets.
or scroll to step through
Analyse existing connections
02 / Analysis
Every onward flight at Abu Dhabi is tested against the 1:00 to 4:00 connect window, both directions. Twenty-four markets already clear it on the baseline schedule.
Optimise times
03 / Optimisation
EY 0100 lands fifteen minutes earlier, EY 0099 leaves five minutes later. Seven markets that missed the window by minutes now clear it; two long connections slip past four hours.
Compare baseline and optimised
04 / Comparison
Only the differences are drawn. Green marks the seven markets the retime opens: Bahrain, Kuwait, Dammam, Chennai, Kolkata, Phnom Penh, Melbourne. Red marks Karachi and Islamabad, whose connections now exceed four hours. Everything both schedules share stays a dot.
One calculation path from schedule input to a reviewable result.
Every result is produced the same way: a composed sample week plus explicit connection rules, evaluated by one calculation, traceable down to individual flight rows. Click a stage to see how it works in detail.
Load data, compose the sample week.
A published schedule feed, your own schedule by SSIM, SFTP or an agreed integration, and optionally market sizes and fares. Filters set which carriers and regions stay in. Sources can be self-service or set up and run by Leitmotif.
Calculate what a proposed flight connects to.
Select or enter flights, then set the hub, the connection window, the MCT source, filters and circuity limits. The result is every valid OD connection, grouped by flight, with the inbound and outbound service behind each one. The optimizer can generate or retime a rotation and recalculate.
Compare two to five options against one baseline.
Option 1 is the baseline. Each alternative shows the markets gained, lost, improved and declined, with the flight combinations behind every difference. An optimized option can sit beside the baseline, judged by the same measures.
Test a trunk schedule at both ends of a partnership.
Two hubs joined by trunk rotations, each with its own schedule version and connection rules. Every variant shows what it connects on both sides. The optimizer can favour one hub, the other, or a balance.
Bring one schedule question.
A first session needs one sample week and one concrete case: a new route, a bank retime, an added frequency, or a trunk partnership. We apply the connection rules your team already uses and show the result down to the flight combination.