When
You build a connection by hand, the client asks whether a transfer is long enough, or you change one flight of a connection.
Steps
| # | Entry | What it does | Why |
|---|---|---|---|
| 1 | @MT | Checks the MCT for the flights in the booking file. | Every connection at once. |
| 2 | @MT1*3 | Checks confirmed segments 1 and 3. | One connection only. |
| 3 | DCTVIE | MCT at Vienna, with its exceptions. | Before you sell. |
| 4 | DCTVIE-II | MCT at Vienna including the international-to-international exceptions. | The type of connection changes the minimum. |
| 5 | DCTFRA*LH · DCTVIE*OSOS | With LH's exceptions · with OS-to-OS exceptions. | Airlines publish their own minimums. |
| 6 | DCTFRA*LHOU-II | LH-to-OU international-to-international exceptions at FRA. | Connections between two airlines. |
| 7 | DCT | Opens the MCT fill-in mask. | When you are unsure of the format. |
Check it worked
The response gives the minimum per type of connection, and your connection is at least that long.
Traps
- An MCT is a minimum, not a comfortable connection time. Allow for a late arrival, a terminal change or passport control.
- A change of airport in the same city needs far more time —
.CXin availability keeps you at one airport (Narrow availability by airline, stops, connection point, time or class). - Airline-only availability can offer connections of up to 23 h 59 min.
DCT*OU·DCT*LHOUlist the airline partnerships used to build connections — background, rarely needed.