Minimum Connecting Time (MCT) Guide: Amadeus, Galileo & Sabre

How to Check Minimum Connecting Time (MCT) in Amadeus, Galileo & Sabre

📅 Updated: October 2026 ⏱ 6 min read ✈️ GDS HUB Editorial

Amadeus DM1 command displaying minimum connecting time for segment 1 in a PNR

Minimum Connecting Time (MCT) is the minimum time required between two flights for a passenger to successfully connect at a specific airport. If the connection is below MCT, the itinerary is considered invalid and cannot be ticketed.

Whether you’re building a complex multi-city itinerary or validating a manually constructed connection, every GDS provides a dedicated command to check MCT. This guide covers the exact entries for Amadeus, Galileo, and Sabre with real-world examples.

Good to know: MCT is defined as the shortest time interval required to transfer a passenger and their luggage from one flight to a connecting flight. Each airline is responsible for updating the MCT table in the GDS.[reference:0]

Why MCT Matters

Ensures the passenger can transfer between flights — the connection is physically possible within the airport
Prevents missed connections — reduces the risk of stranded passengers and airline liability
Required check before ticketing — most GDS systems block ticketing if MCT is violated
Affects fare and routing validity — an invalid connection means the entire itinerary may be rejected

Important: MCT varies by airport, airline, terminal, and connection type (domestic-to-domestic, domestic-to-international, etc.). Always verify the MCT for the specific airline and airport combination before confirming a booking.

Amadeus MCT Commands

Check MCT with Existing Segments

If you already have segments in the PNR, use the following command:

AMADEUS · DM DM1 Displays MCT for segment 1

Example

Actual connecting time is 01:45 → This means the minimum required connection is 1 hour 30 minutes, and the current connection time is 1 hour and 45 minutes. The itinerary passes MCT validation.

Amadeus DM1 output showing MCT validation for segment 1 with connection time details

Amadeus DM1 output — MCT validation for segment 1

Check MCT at a Specific Airport

You can also display the MCT for a specific airport without an active PNR:

AMADEUS · DM DM BCN Displays the MCT at Barcelona airport, including between different terminals if applicable.[reference:1]

If No Segments in the PNR

If the PNR has no segments yet, first display availability, then check MCT:

AMADEUS · DM AN22MAYSHJASW/ASM DM1 Display availability first, then check MCT for segment 1

Check MCT Between Two Specific Segments

You can also check MCT between two specific segments in the PNR:

AMADEUS · DM DM2/3 Check MCT between segment 2 (arrival) and segment 3 (departure)[reference:2]

Galileo MCT Commands

Check MCT for an Itinerary

In Galileo (Travelport+), use @MT to validate MCT for an itinerary:

GALILEO · @MT @MT Validates MCT for all connections in the itinerary

Check MCT Between Specific Segments

GALILEO · @MT @MT1-2 Requests MCT for connection between segments 1 and 2[reference:3]

Example

Consider a three-segment itinerary: BLR → DEL (Dep: 06:10 / Arr: 08:55), then DEL → FRA (Dep: 13:40 / Arr: 18:40). The connection is valid (enough time).

Now add: FRA → LHR (Dep: 14:00 / Arr: 14:40 same day). The system returns an error:

GALILEO · ERROR CHECK DATE/TIME CONTINUITY AT SEGMENT 03 The connection is too short / invalid

Galileo @MT command output showing MCT validation error at segment 03

Galileo @MT output — MCT validation error for segment 03

Display MCT at a Specific Airport

To display the MCT at an airport without an active itinerary, use:

GALILEO · DCT DCTPDX-DD Displays MCT at Portland (PDX) for domestic-to-domestic connections[reference:4]

Connection type codes: DD = Domestic-to-Domestic, DI = Domestic-to-International, ID = International-to-Domestic, II = International-to-International.[reference:5]

Note: An MCT link displays automatically after you end transact a PNR that does not meet minimum connection requirements.[reference:6]

Sabre MCT Commands

Verify MCT for All Connections

In Sabre, use VCT* to verify the MCT for all connections in the PNR:

SABRE · VCT* VCT* Verifies MCT for all connections in the itinerary

Successful Response

If all connections meet the minimum required time, Sabre returns:

SABRE · VALID MINIMUM CONNECT TIME EDIT VALID FOR ALL CONNECTIONS All connections are valid[reference:7]

Invalid Connection Response

If a connection is below MCT, Sabre returns an error indicating which segments are affected and the minimum required time:

SABRE · INVALID INVALID CONNECT TIME SEGS 1 AND 2 – MINIMUM IS 50 MINUTES The connection is too short — minimum 50 minutes required[reference:8]

Check MCT Between Specific Segments

SABRE · VCT* VCT*1-2 Check MCT specifically between segments 1 and 2[reference:9]

Error handling: If Sabre returns “CONNECTION SUPPRESSED”, you must first verify the connection time with the carrier directly. The flights are considered suppressed at this point.[reference:10]

Quick Reference Table

Bookmark this table for quick access during your daily work.

GDS	Command	Purpose
Amadeus	DM1	Check MCT for segment 1 in a PNR
Amadeus	DM2/3	Check MCT between segments 2 and 3
Amadeus	DM BCN	Display MCT at a specific airport
Galileo	@MT	Validate MCT for all connections
Galileo	@MT1-2	Check MCT between segments 1 and 2
Galileo	DCTPDX-DD	Display MCT at airport for connection type
Sabre	VCT*	Verify MCT for all connections
Sabre	VCT*1-2	Check MCT between segments 1 and 2

Related reading: For a complete guide on flight availability commands, see Galileo for Beginners: Flight Availability Search. For fare shopping across GDS, read Amadeus FXD: Essential Commands and Galileo FS: Essential Commands.

Frequently Asked Questions

What is Minimum Connecting Time (MCT)?

Minimum Connecting Time (MCT) is the shortest time interval required to transfer a passenger and their luggage from one flight to a connecting flight at a specific airport. If the connection time is below the MCT, the itinerary is considered invalid and cannot be ticketed.

How do I check MCT in Amadeus?

In Amadeus, use DM followed by the airport code to display the MCT at that airport (DM BCN). If you have segments in a PNR, use DM1 to check the MCT for segment 1. You can also use DM2/3 to check between two specific segments.

How do I check MCT in Galileo?

In Galileo, use @MT to validate the MCT for an itinerary. To check a specific connection, use @MT1-2 for segments 1 and 2. The system returns either a valid confirmation or a CHECK DATE/TIME CONTINUITY error if the connection is too short.

How do I check MCT in Sabre?

In Sabre, use VCT* to verify the MCT for all connections in the PNR. A successful result shows MINIMUM CONNECT TIME EDIT VALID FOR ALL CONNECTIONS. If a connection is invalid, Sabre returns INVALID CONNECT TIME SEGS 1 AND 2 with the minimum required minutes.

What happens if the connection is below MCT?

If the connection time between two segments is below the minimum required, the itinerary is considered invalid. The GDS will either block the booking or return an error message. You must rebook with a longer connection or select a different flight.

Why is MCT important for travel agents?

MCT is crucial because it ensures the passenger can realistically transfer between flights, prevents missed connections, and is a required check before ticketing. Airlines and GDS systems enforce MCT to avoid liability for missed connections.

Can MCT vary by airline and airport?

Yes. MCT varies by airport, airline, terminal, and connection type (domestic-to-domestic, domestic-to-international, etc.). Each airline is responsible for updating the MCT table in the GDS. Always verify the MCT for the specific airline and airport combination.

📚 Related Guides

GDS Guide Minimum Connecting Time (MCT) – Quick Guide Galileo Galileo for Beginners: Flight Availability Search Amadeus Amadeus FXD: Essential Commands for Finding the Best Airfare Galileo Galileo FS: Essential Commands for Finding the Best Airfare Comparison Amadeus vs Sabre vs Galileo Reference The Ultimate Galileo Commands Guide

Practise MCT Checks in a Safe Simulator

Create a free GDS HUB account and practise DM, @MT and VCT* commands in a simulated Amadeus, Galileo or Sabre environment — no live data, no risk.

Start Practising Free →

🏷 Tags: blog

Minimum Connecting Time (MCT) – Quick Guide

Why MCT Matters

Amadeus MCT Commands

Check MCT with Existing Segments

Example

Check MCT at a Specific Airport

If No Segments in the PNR

Check MCT Between Two Specific Segments

Galileo MCT Commands

Check MCT for an Itinerary

Check MCT Between Specific Segments

Example

Display MCT at a Specific Airport

Sabre MCT Commands

Verify MCT for All Connections

Successful Response

Invalid Connection Response

Check MCT Between Specific Segments

Quick Reference Table

Frequently Asked Questions

Tags

📚 Related Guides

Practise MCT Checks in a Safe Simulator

Amadeus vs Sabre vs Galileo: Which GDS to Learn?

Follow Us