Close Menu

    Subscribe to Updates

    Get the latest news on Baggage and Handling Trends around Aviation

    What's Hot

    IATA Resolution 751 – Use of the 10-Digit License Plate

    March 10, 2022

    IATA Resolution 752 – Electronic Baggage Claim Receipt

    March 10, 2022

    IATA Resolution 753 – Baggage Tracking

    March 10, 2022
    Facebook X (Twitter) Instagram
    Facebook X (Twitter) Instagram
    Baggage LogisticsBaggage Logistics
    Subscribe
    • Home
    • Baggage Operations
      1. Passenger Services
      2. Interline & Passenger Communications
      3. Airline Systems
      4. View All

      IATA Resolution 752 – Electronic Baggage Claim Receipt

      March 10, 2022

      IATA Resolution 754 – Baggage Proration Profiles

      March 10, 2022

      Recommended Practice 1717 – Teletype Passenger Manifest (TPM)

      January 16, 2021
      8.9

      Recommended Practice 1717a – PAXLST Message

      January 15, 2021

      Recommended Practice 1719a – Frequent Traveller List (FTL)

      January 22, 2021

      Recommended Practice 1719b – Passenger Reconcile List (PRL)

      January 17, 2021

      My Mother Curses Me Every Day; What to Do?

      January 17, 2021

      Recommended Practice 1718 – Passenger Transfer Message (PTM)

      January 15, 2021

      IATA Resolution 753 – Baggage Tracking

      March 10, 2022

      Amadeus Altéa Departure Control

      January 17, 2021

      SabreSonic Departure Control

      January 17, 2021

      IATA Recommended Practice 1690b – Baggage Reference Manual Standards

      January 15, 2021

      IATA Resolution 751 – Use of the 10-Digit License Plate

      March 10, 2022

      IATA Resolution 763 – Location Identifiers

      January 22, 2021

      IATA Resolution 769 – Baggage Tag Issuer Codes (BTIC)

      January 19, 2021

      Radixx Res

      January 17, 2021
    Baggage LogisticsBaggage Logistics
    Home»Baggage Operations»Baggage Handling»IATA Resolution 765 – Interline Connecting Time Intervals
    Baggage Handling

    IATA Resolution 765 – Interline Connecting Time Intervals

    Standardizing minimum connection times to ensure passengers and their checked baggage can make interline connections safely, efficiently, and consistently across the global airline network.
    yousuccessBy yousuccessJanuary 13, 2021Updated:July 13, 2026No Comments25 Mins Read4 Views
    Facebook Twitter Pinterest LinkedIn Tumblr Email
    Share
    Facebook Twitter LinkedIn Pinterest WhatsApp Email

    Introduction

    Every day, millions of passengers travel on journeys involving connections between two or more flights. Many of these itineraries also involve multiple airlines operating under interline agreements, where one carrier delivers a passenger and checked baggage to another carrier for onward transportation. Although these connections appear seamless from the passenger’s perspective, they depend upon careful operational planning to ensure that both the traveller and their baggage can successfully transfer between flights within the available time.

    Connection times are influenced by numerous operational factors, including aircraft disembarkation, walking distances between gates or terminals, security screening, immigration and customs procedures, baggage unloading, baggage sortation, transfer loading, boarding deadlines, and airport layout. If insufficient time is allowed, passengers may miss onward flights, baggage may fail to transfer, and airlines incur significant operational costs associated with rebooking, baggage tracing, accommodation, and customer compensation.

    To address these challenges, the International Air Transport Association (IATA) established Resolution 765 – Interline Connecting Time Intervals, which defines the international framework for determining and publishing Minimum Connecting Times (MCTs) for interline passenger journeys. The Resolution defines the Minimum Connecting Time as the shortest time interval required to transfer both a passenger and their checked baggage from one flight to a connecting flight at a specific location.

    Unlike scheduling guidelines that merely recommend connection times, Resolution 765 establishes mandatory procedures requiring airlines serving the same airport to cooperate in determining realistic transfer times. These agreed values become the official Minimum Connecting Times used throughout the aviation industry when constructing passenger itineraries, validating reservations, and building schedules.

    The Resolution serves two complementary purposes. First, it protects passengers by preventing airlines and reservation systems from selling connections that are operationally unrealistic. Second, it protects participating airlines by ensuring that both the delivering carrier and the receiving carrier can reasonably expect passengers and their checked baggage to complete the transfer successfully. The Resolution therefore balances customer service, operational reliability, and commercial fairness across the interline network.

    Resolution 765 recognizes that connection times cannot be standardized globally because every airport presents different operational characteristics. A domestic transfer within a small regional airport may require only a short walking distance and minimal baggage handling, while an international transfer at a major hub may involve immigration formalities, security screening, terminal transfers, customs inspection, and complex baggage sorting systems. Consequently, the Resolution establishes a structured local governance process through which airlines jointly determine airport-specific Minimum Connecting Times based on actual operational conditions.

    At the centre of this process is the Local Minimum Connecting Time Group (LMCTG). Resolution 765 requires airlines operating at airports served by multiple carriers to participate in these local committees, where representatives evaluate airport infrastructure, baggage handling capabilities, passenger processing times, and operational performance before agreeing on standardized connection intervals. These locally determined values are subsequently published through IATA’s scheduling standards and become mandatory for reservation systems, ticketing platforms, and itinerary construction worldwide.

    The Resolution also plays an important role in baggage operations. Because the Minimum Connecting Time applies to both passengers and checked baggage, it ensures that baggage transfer systems have sufficient time to unload, sort, transport, screen, and reload baggage before the onward flight departs. This close relationship between passenger transfer times and baggage transfer capability significantly reduces baggage misconnects while supporting broader IATA baggage standards governing baggage identification, tracking, and reconciliation.

    Today, Resolution 765 forms one of the most important operational standards supporting global airline interoperability. Every Global Distribution System (GDS), Computer Reservation System (CRS), Departure Control System (DCS), scheduling application, and airline booking engine relies upon the Minimum Connecting Times established under this Resolution when determining whether a proposed itinerary can be sold. By ensuring that connection times reflect actual airport capabilities, Resolution 765 contributes directly to operational reliability, passenger satisfaction, baggage performance, and the efficient functioning of the worldwide interline network.



    Origin and Publication

    The Need for Standardized Minimum Connection Times

    As commercial aviation expanded and interline agreements became increasingly common, airlines faced a growing operational challenge. Passengers could purchase a single itinerary involving multiple carriers, yet each airline often applied its own assumptions regarding the time required to transfer passengers and baggage between flights.

    Without standardized Minimum Connecting Times, reservation systems could construct itineraries that appeared feasible on paper but were operationally unrealistic. A passenger might have only a few minutes to disembark, change terminals, clear security or immigration, while simultaneously expecting checked baggage to be unloaded, transported across the airport, sorted, screened, and loaded onto another aircraft.

    These unrealistic connections resulted in:

    • missed onward flights;
    • delayed or misconnected baggage;
    • increased baggage tracing;
    • passenger rebooking costs;
    • hotel and meal expenses;
    • customer dissatisfaction; and
    • operational disputes between interline partners.

    Recognizing that connection reliability depended upon both passenger movement and baggage transfer capability, IATA introduced Resolution 765 to establish a globally coordinated methodology for determining airport-specific Minimum Connecting Times.


    Passenger Services Conference

    Resolution 765 was developed under the authority of the IATA Passenger Services Conference (PSC), the international body responsible for establishing standards governing passenger services, baggage operations, reservations, schedules, ticketing, and interline cooperation.

    The Passenger Services Conference develops operational standards through formal Resolutions and Recommended Practices that enable airlines worldwide to cooperate using common procedures.

    Within this framework, Resolution 765 specifically governs:

    • Minimum Connecting Times (MCTs);
    • interline passenger transfers;
    • interline baggage transfer intervals;
    • local coordination procedures;
    • publication of connection times; and
    • implementation within airline scheduling systems.

    Adoption and Publication

    Resolution 765 was first adopted during the 36th IATA Passenger Services Conference (PSC) and subsequently published in the Passenger Services Conference Resolutions Manual. Since its original adoption, the Resolution has remained an ongoing standard, maintained through Passenger Services Conference amendment procedures and periodic updates published within the official IATA documentation. Recent Passenger Services Conference cycles have reaffirmed the Resolution without introducing changes to its fundamental operational principles.

    Unlike many technical standards that prescribe equipment or messaging formats, Resolution 765 establishes governance procedures requiring airlines serving the same airport to collaborate in determining realistic transfer intervals based upon local operational conditions.


    Local Minimum Connecting Time Groups (LMCTGs)

    The defining feature of Resolution 765 is the establishment of the Local Minimum Connecting Time Group (LMCTG).

    Every airport served by multiple passenger carriers is required to establish a local committee responsible for reviewing, determining, and maintaining Minimum Connecting Times.

    Membership typically includes:

    • scheduled airlines;
    • non-IATA airlines operating at the airport;
    • intermodal transport providers using airline designators;
    • airport representatives; and
    • other eligible operational stakeholders.

    Where an official LMCTG does not exist, an Airport Operators Committee (AOC) may assume equivalent responsibilities. In exceptional circumstances where neither body exists, the airport authority may submit Minimum Connecting Time proposals to IATA following consultation with affected airlines.


    Defining the Minimum Connecting Time

    Resolution 765 formally defines the Minimum Connecting Time (MCT) as:

    “The shortest time interval required in order to transfer a passenger and their checked baggage, in a specific location.”

    This definition highlights one of the Resolution’s most important principles.

    The MCT does not apply solely to passenger movement.

    It also ensures that:

    • checked baggage can be unloaded;
    • baggage can be sorted correctly;
    • security procedures can be completed;
    • baggage can be transported between terminals if required; and
    • baggage can be loaded onto the connecting flight.

    Consequently, Resolution 765 closely links passenger service standards with baggage handling performance.


    Factors Considered by LMCTGs

    Rather than prescribing fixed connection times, Resolution 765 requires Local Minimum Connecting Time Groups to evaluate numerous operational factors before determining airport-specific values.

    Typical considerations include:

    • airport layout;
    • walking distances;
    • inter-terminal transport;
    • baggage unloading times;
    • baggage sortation capability;
    • baggage loading times;
    • security screening duration;
    • immigration processing;
    • customs inspection;
    • passenger boarding deadlines;
    • aircraft turnaround procedures; and
    • historical operational performance.

    Each factor is assigned an appropriate time allocation, and the total becomes the published Minimum Connecting Time for that connection type. The Resolution further requires that all MCT values be standardized in five-minute increments, promoting consistency across scheduling and reservation systems.


    Publication Through IATA Scheduling Standards

    Once a Local Minimum Connecting Time Group reaches agreement, the approved values are communicated through designated MCT Coordinators and submitted to IATA for publication.

    The published values become part of the industry’s scheduling standards and are incorporated into airline scheduling databases, reservation systems, and Global Distribution Systems.

    Resolution 765 further requires that all automated reservation systems construct and display itineraries using these published Minimum Connecting Times. Where no locally established MCT exists, the systems must apply the default values specified within the Standard Schedules Information Manual (SSIM).


    Purpose

    Protecting Passenger Connections

    The primary purpose of Resolution 765 is to ensure that passengers have sufficient time to complete flight connections safely and reliably.

    By establishing realistic transfer intervals based upon actual airport conditions, the Resolution reduces missed connections while improving the overall passenger experience.


    Protecting Checked Baggage Transfers

    Unlike many scheduling standards, Resolution 765 explicitly recognizes that baggage requires time to transfer between flights.

    Minimum Connecting Times therefore account for both passenger movement and baggage handling operations, helping reduce baggage misconnects and delayed baggage claims.


    Supporting Fair Interline Operations

    Resolution 765 protects both the delivering airline and the receiving airline by establishing mutually agreed transfer standards.

    This minimizes disputes between interline partners while promoting operational cooperation across shared airport environments.


    Standardizing Reservation and Scheduling Systems

    The Resolution ensures that all participating airlines, reservation systems, and Global Distribution Systems use identical Minimum Connecting Times when constructing itineraries.

    This prevents unrealistic connections from being offered while promoting consistent scheduling practices throughout the global aviation industry.


    Supporting Operational Reliability

    Ultimately, Resolution 765 exists to improve the reliability of airline operations by aligning published schedules with the actual capabilities of airports, baggage systems, passenger processing facilities, and operational procedures. By integrating passenger movement and baggage transfer requirements into one coordinated standard, the Resolution contributes directly to safer, more predictable, and more efficient interline travel.

    Operational Importance

    Resolution 765 is one of the aviation industry’s most influential operational standards because it directly affects the reliability of passenger journeys and baggage transfers across the global airline network. Every published interline itinerary depends upon Minimum Connecting Times (MCTs) that realistically reflect the time required for passengers and checked baggage to move between flights.

    Unlike scheduling standards that focus solely on aircraft movements, Resolution 765 recognizes that successful connections involve an entire operational ecosystem. Aircraft must arrive on time, passengers must disembark and navigate the airport, baggage must be unloaded and transferred, security and immigration formalities may need to be completed, and the receiving flight must still be available for boarding.

    By ensuring that all these processes are considered when establishing Minimum Connecting Times, the Resolution significantly improves the reliability of interline travel while reducing missed connections and baggage misconnects.


    Protecting Passenger Connections

    Passengers purchasing a through itinerary reasonably expect that every published connection is achievable under normal operating conditions.

    Resolution 765 protects this expectation by preventing reservation systems from offering connections shorter than the agreed Minimum Connecting Time.

    Rather than allowing individual airlines to publish unrealistic itineraries, the Resolution requires all participating carriers serving an airport to use the same locally approved connection standards.

    This improves passenger confidence while reducing:

    • missed onward flights;
    • involuntary rebookings;
    • overnight accommodation costs;
    • customer complaints; and
    • schedule disruptions.

    Improving Baggage Transfer Performance

    One of the Resolution’s distinguishing features is its explicit inclusion of checked baggage within the Minimum Connecting Time definition.

    A passenger may be capable of reaching the departure gate quickly, yet baggage requires additional operational processes, including:

    • aircraft unloading;
    • baggage identification;
    • transfer screening;
    • automated sortation;
    • transport across baggage systems;
    • loading onto the receiving aircraft.

    Resolution 765 ensures that Minimum Connecting Times provide sufficient time for these baggage processes to occur, thereby reducing delayed baggage and transfer failures.


    Supporting Interline Cooperation

    Interline travel depends upon cooperation between independent airlines.

    Resolution 765 protects both the delivering carrier and the receiving carrier by establishing mutually agreed transfer standards.

    The delivering airline gains confidence that passengers and baggage have sufficient time to complete the transfer.

    The receiving airline gains assurance that unrealistic connections will not generate avoidable disruptions within its own operation.

    This shared framework strengthens operational trust across the interline network.


    Improving Schedule Integrity

    Without standardized Minimum Connecting Times, reservation systems could create itineraries that satisfy timetable logic but fail operationally.

    Resolution 765 ensures that published schedules reflect:

    • airport infrastructure;
    • passenger processing capability;
    • baggage handling performance;
    • operational constraints; and
    • local transfer procedures.

    As a result, airline schedules become more realistic and operationally sustainable.


    Supporting Airport Operations

    Airport operators also benefit from standardized connection intervals.

    Because Minimum Connecting Times are based upon actual airport capabilities, infrastructure planners can use them when evaluating:

    • terminal capacity;
    • passenger flows;
    • baggage system performance;
    • transfer facilities;
    • expansion projects.

    This enables airports to improve operational efficiency while maintaining realistic passenger expectations.


    Technical Structure

    Resolution 765 establishes a comprehensive governance framework rather than prescribing fixed connection times.

    Its technical architecture consists of several integrated components:

    • Local Minimum Connecting Time Groups (LMCTGs);
    • standardized Minimum Connecting Time calculations;
    • operational assessment criteria;
    • publication procedures;
    • communication through designated coordinators; and
    • implementation within airline scheduling systems.

    Local Minimum Connecting Time Group (LMCTG)

    The Local Minimum Connecting Time Group forms the operational foundation of Resolution 765.

    Each airport served by more than one passenger carrier is required to establish an LMCTG responsible for determining Minimum Connecting Times appropriate to local operating conditions.

    Typical membership includes:

    • scheduled airlines;
    • non-IATA airlines;
    • A4A member airlines where applicable;
    • approved intermodal operators;
    • airport representatives.

    Where no formal LMCTG exists, an Airport Operators Committee (AOC) may perform the same responsibilities.

    In exceptional circumstances, the airport authority may coordinate proposals directly with IATA following consultation with affected carriers.


    Responsibilities of the LMCTG

    The Local Minimum Connecting Time Group is responsible for:

    • reviewing airport transfer procedures;
    • analysing operational performance;
    • evaluating infrastructure changes;
    • proposing new Minimum Connecting Times;
    • reviewing existing MCTs;
    • documenting operational assumptions;
    • publishing agreed time allocations locally.

    The committee normally elects a Chair who coordinates meetings and communicates agreed decisions to airline MCT Coordinators.


    Minimum Connecting Time Calculation

    Resolution 765 requires LMCTGs to determine connection times by analysing the operational activities necessary for both passengers and baggage.

    Typical elements include:

    Operational FactorPurpose
    Passenger disembarkationTime to leave arriving aircraft
    Walking distanceTerminal movement
    Inter-terminal transportShuttle or train transfers
    Security screeningPassenger security checks
    Immigration processingBorder control clearance
    Customs proceduresArrival formalities where applicable
    Baggage unloadingRemoval from arriving aircraft
    Baggage sortationTransfer through baggage handling systems
    Baggage loadingLoading onto connecting aircraft
    Boarding deadlineReceiving carrier’s gate closure

    Each component contributes to the final published Minimum Connecting Time.

    Rather than relying on estimates, LMCTGs base these values on actual airport operating conditions and historical performance.


    Standardized Time Increments

    To promote consistency across scheduling systems, Resolution 765 requires Minimum Connecting Times to be published using five-minute increments.

    Typical values include:

    • 30 minutes
    • 35 minutes
    • 40 minutes
    • 45 minutes
    • 60 minutes
    • 75 minutes
    • 90 minutes

    Standardized increments simplify implementation within reservation and scheduling systems while ensuring consistent interpretation across airlines.


    Local Publication

    Following agreement, the LMCTG documents:

    • approved MCT values;
    • operational assumptions;
    • factor allocations;
    • applicable connection categories;
    • any supporting local guidance.

    Publishing these values locally ensures that airlines understand how individual connection times were established.


    Communication Through MCT Coordinators

    Each participating airline appoints an MCT Coordinator, whose responsibilities include:

    • receiving LMCTG decisions;
    • reviewing proposed changes;
    • coordinating airline approval;
    • communicating with IATA;
    • supporting SSIM implementation.

    Resolution 765 specifies formal communication timelines to ensure industry-wide synchronization before new Minimum Connecting Times become effective.


    Default Minimum Connecting Times

    Not every airport establishes local MCT values.

    Where no approved local Minimum Connecting Time exists, Resolution 765 requires reservation systems to apply the default values specified within the Standard Schedules Information Manual (SSIM).

    This guarantees worldwide operational consistency even where local committees have not established airport-specific standards.


    Bilateral Exceptions

    Although Resolution 765 establishes common standards, it also permits airlines to negotiate approved bilateral exceptions.

    Examples include:

    • dedicated transfer facilities;
    • private baggage systems;
    • coordinated hub operations;
    • premium passenger transfer services.

    Such exceptions must be filed according to SSIM procedures and become valid only after formal publication.

    This flexibility allows airlines to improve operational efficiency without compromising overall system integrity.



    Implementation Guidelines

    Implementation of Resolution 765 requires close coordination between airlines, airports, IATA, and technology providers.

    Unlike many operational standards, implementation focuses primarily on governance and systems synchronization rather than physical equipment.


    Airline Responsibilities

    Each airline is responsible for:

    • appointing an MCT Coordinator;
    • participating in LMCTG activities;
    • reviewing proposed connection times;
    • updating scheduling systems;
    • implementing published MCT values;
    • ensuring reservation systems reject invalid connections.

    Airlines must also ensure that operational departments understand locally approved Minimum Connecting Times.


    Airport Responsibilities

    Airport operators support the Resolution by providing operational information concerning:

    • terminal layouts;
    • baggage handling capability;
    • security procedures;
    • passenger flows;
    • infrastructure changes;
    • construction projects.

    This information enables LMCTGs to establish realistic transfer times.


    Local Committee Review

    Resolution 765 requires LMCTGs to review Minimum Connecting Times at least annually.

    Additional reviews occur whenever significant operational changes arise, including:

    • new terminals;
    • security changes;
    • baggage system upgrades;
    • terminal relocations;
    • major schedule revisions.

    Regular reviews ensure published MCT values remain operationally realistic.


    Systems Implementation

    Following publication by IATA:

    1. Airlines receive updated MCT information.
    2. Scheduling databases are updated.
    3. Global Distribution Systems synchronize.
    4. Reservation systems implement revised values.
    5. Ticketing applications validate itineraries.
    6. Departure Control Systems reference current connection standards.

    This coordinated implementation ensures consistent behaviour across all participating airline systems.


    Operational Workflow

    The operational sequence established by Resolution 765 typically follows these steps:

    1. Airlines and airport representatives identify the need to review Minimum Connecting Times.
    2. The Local Minimum Connecting Time Group convenes.
    3. Airport infrastructure and operational performance are evaluated.
    4. Passenger processing and baggage handling activities are analysed.
    5. Appropriate Minimum Connecting Times are calculated.
    6. The LMCTG approves the proposed values.
    7. MCT Coordinators communicate the approved values to participating airlines and IATA.
    8. IATA publishes the updated values through the Standard Schedules Information Manual (SSIM).
    9. Reservation systems, Global Distribution Systems, and airline scheduling applications synchronize with the published MCTs.
    10. Future passenger itineraries are validated automatically using the updated Minimum Connecting Times.

    System Integration

    Resolution 765 integrates with numerous airline operational systems.

    Standard Schedules Information Manual (SSIM)

    SSIM serves as the industry’s authoritative publication mechanism for approved Minimum Connecting Times and distributes updated values throughout airline scheduling systems.

    Global Distribution Systems (GDS)

    GDS platforms use published MCT values when constructing and validating passenger itineraries, ensuring that only operationally feasible connections are offered.

    Computer Reservation Systems (CRS)

    Reservation systems automatically compare proposed flight connections against published Minimum Connecting Times before confirming bookings.

    Departure Control Systems (DCS)

    DCS platforms reference approved MCT values when managing passenger transfers, re-accommodation, and irregular operations.

    Baggage Handling Systems (BHS)

    Because Minimum Connecting Times explicitly include baggage transfer requirements, baggage handling systems benefit from realistic transfer intervals that support successful baggage sortation and loading.

    Airport Operational Systems

    Airport Operational Databases (AODB), transfer management systems, passenger flow monitoring applications, and resource management platforms use published MCT values when planning airport operations and evaluating infrastructure performance.

    Benefits for Airlines

    Resolution 765 provides significant operational, commercial, and customer service benefits by ensuring that published flight connections are based on realistic airport capabilities rather than optimistic scheduling assumptions. By standardizing Minimum Connecting Times (MCTs), airlines can construct more reliable itineraries, reduce operational disruption, and improve coordination across interline networks.

    Improved Schedule Reliability

    One of the Resolution’s principal benefits is the improvement of schedule integrity.

    Reservation systems validate every interline itinerary against approved Minimum Connecting Times before a booking is confirmed. This prevents the sale of connections that are unlikely to succeed under normal operating conditions.

    Consequently, airlines experience fewer:

    • missed passenger connections;
    • baggage transfer failures;
    • involuntary rebookings;
    • operational delays; and
    • passenger complaints.

    The result is a more dependable schedule that better reflects actual airport performance.

    Reduced Misconnected Baggage

    Because Resolution 765 defines the Minimum Connecting Time as the interval required for both passengers and their checked baggage, baggage transfer capability becomes an integral part of schedule planning.

    Realistic transfer intervals provide sufficient time for baggage to be:

    • unloaded from the arriving aircraft;
    • transported through the baggage handling system;
    • sorted to the correct departure flight;
    • security screened where required; and
    • loaded onto the connecting aircraft.

    This significantly reduces delayed baggage and transfer failures while complementing the objectives of Resolution 753 on baggage tracking.

    Lower Irregular Operations Costs

    Every missed connection generates operational expenses, including:

    • passenger rebooking;
    • hotel accommodation;
    • meal vouchers;
    • baggage tracing;
    • baggage forwarding;
    • customer compensation.

    By reducing unrealistic connections, Resolution 765 helps airlines minimize these avoidable costs while improving operational efficiency.

    Better Interline Relationships

    Standardized Minimum Connecting Times reduce disagreements between participating carriers.

    Since all airlines serving the airport use the same approved transfer standards, disputes regarding unrealistic schedules or failed transfers become far less frequent.

    This strengthens cooperation within airline alliances and interline partnerships.


    Benefits for Airports

    Airport operators benefit because Resolution 765 aligns airline schedules with the airport’s actual processing capability.

    Better Infrastructure Utilization

    Minimum Connecting Times are determined using actual airport characteristics, including:

    • terminal configuration;
    • passenger flows;
    • baggage system capacity;
    • security facilities;
    • immigration processing;
    • transport between terminals.

    These evaluations help airports understand operational constraints while identifying opportunities for improvement.

    Improved Passenger Flow

    Appropriate connection intervals distribute passenger movements more evenly throughout terminals.

    This reduces congestion at:

    • security checkpoints;
    • immigration facilities;
    • transfer corridors;
    • boarding gates.

    Better passenger flow improves both operational efficiency and the passenger experience.

    Enhanced Baggage Performance

    Airport baggage handling systems operate more efficiently when transfer times accurately reflect baggage processing capability.

    Adequate transfer intervals reduce:

    • rushed baggage handling;
    • transfer congestion;
    • baggage misconnects;
    • manual baggage intervention.

    Benefits for Ground Handlers

    Ground handling organizations play a central role in achieving successful passenger and baggage transfers.

    Resolution 765 supports their operations by providing realistic operational timeframes.

    Predictable Transfer Workloads

    Published Minimum Connecting Times enable handlers to plan staffing and equipment requirements according to expected transfer volumes.

    This supports:

    • baggage loading;
    • baggage unloading;
    • transfer sortation;
    • aircraft turnaround;
    • passenger assistance.

    Reduced Last-Minute Pressure

    Unrealistically short connections often force ground handlers to prioritize certain baggage or passengers at the expense of overall efficiency.

    By providing realistic connection intervals, Resolution 765 reduces operational pressure while improving handling quality.

    Improved Service Performance

    Ground handling companies benefit from:

    • fewer missed baggage transfers;
    • fewer passenger connection failures;
    • improved on-time performance;
    • clearer operational expectations.

    Auditability and Compliance

    Resolution 765 establishes a structured governance process that supports both operational auditing and continuous improvement.

    Local Governance

    Each Local Minimum Connecting Time Group (LMCTG) is responsible for maintaining documented records supporting every approved Minimum Connecting Time.

    Typical documentation includes:

    • meeting minutes;
    • operational assessments;
    • airport infrastructure reviews;
    • approved MCT values;
    • supporting calculations.

    This documentation provides transparency regarding how connection times were established.

    Operational Note

    Minimum Connecting Times are not arbitrary scheduling values. Under Resolution 765 they are evidence-based operational standards derived from airport infrastructure, passenger processing capability, baggage handling performance, and agreed local procedures.

    Regular Reviews

    Resolution 765 requires Local Minimum Connecting Time Groups to review published values at least once each year.

    Additional reviews are conducted whenever operational changes occur, including:

    • terminal expansions;
    • baggage handling upgrades;
    • security process changes;
    • airport redevelopment;
    • significant traffic growth.

    These periodic reviews ensure that published connection times remain operationally valid.

    Reservation System Compliance

    Airline reservation systems must validate itineraries against the published Minimum Connecting Times.

    Audits typically verify that:

    • current MCT databases have been implemented;
    • obsolete values have been removed;
    • connection validation functions operate correctly;
    • published itineraries comply with approved standards.

    Relationship to Other IATA Standards

    Resolution 765 operates alongside numerous IATA standards governing passenger services, scheduling, and baggage operations.

    StandardRelationship to Resolution 765
    Resolution 751 – Use of the 10-Digit License PlateSuccessful baggage transfers depend upon correct baggage identification using the License Plate Number, while Resolution 765 ensures sufficient transfer time exists for baggage processing.
    Resolution 752 – Electronic Baggage Claim ReceiptPassenger baggage receipts reflect itineraries built using valid Minimum Connecting Times established under Resolution 765.
    Resolution 753 – Baggage TrackingResolution 753 records baggage custody during transfer operations, while Resolution 765 provides the time required for those transfers to be completed successfully.
    Resolution 763 – Location IdentifiersAirport location identifiers published under Resolution 763 identify the airports where Minimum Connecting Times apply.
    Standard Schedules Information Manual (SSIM)Resolution 765 publishes approved Minimum Connecting Times through SSIM, allowing airlines and reservation systems to synchronize scheduling data.
    Passenger Reservations StandardsReservation systems rely on published MCT values when validating interline itineraries and preventing unrealistic flight connections.

    Together these standards ensure that passenger itineraries, baggage transfers, operational scheduling, and airport processing function as one coordinated system.


    Real-World Use Cases

    Major International Hub

    A passenger travels from Johannesburg to Frankfurt via Doha.

    The connecting itinerary has been validated using the Doha airport’s published Minimum Connecting Time.

    Because the transfer interval reflects actual terminal layout, immigration requirements, and baggage handling capability, both the passenger and checked baggage complete the connection successfully.


    Domestic-to-International Transfer

    A passenger connects from a domestic flight to an international departure.

    The Local Minimum Connecting Time accounts for:

    • domestic arrival procedures;
    • international security screening;
    • passport control;
    • baggage transfer.

    Reservation systems therefore prevent itineraries that cannot realistically be completed.


    Airport Terminal Change

    An airport opens a new satellite terminal requiring passengers to travel by automated people mover.

    Following operational evaluation, the Local Minimum Connecting Time Group increases the published MCT.

    The updated values are distributed through SSIM and automatically implemented within reservation systems worldwide.


    Interline Airline Connection

    A passenger arrives on Airline A and departs on Airline B.

    Both airlines use the same locally approved Minimum Connecting Time.

    Ground handlers transfer baggage within the published interval while passengers complete transfer formalities, allowing the connection to proceed smoothly.


    Airport Infrastructure Improvement

    Installation of a high-speed baggage handling system reduces baggage transfer times significantly.

    Following operational testing, the LMCTG reviews the airport’s MCT values and approves revised, shorter connection intervals.

    The updated values enable airlines to offer more competitive itineraries without compromising operational reliability.


    Irregular Operations Recovery

    Weather delays cause arriving flights to operate behind schedule.

    Although some passengers miss onward connections, the standardized MCT framework enables airlines to identify which itineraries remained operationally feasible and which require re-accommodation, simplifying disruption management.


    Industry Challenges

    Although Resolution 765 provides an effective operational framework, implementation presents several ongoing challenges.

    Airport Complexity

    Large international airports continually evolve through:

    • terminal expansions;
    • infrastructure upgrades;
    • new security procedures;
    • changing passenger volumes.

    Minimum Connecting Times must therefore be reviewed regularly to remain accurate.

    Balancing Commercial and Operational Interests

    Airlines naturally seek shorter connection times to increase itinerary attractiveness.

    However, overly aggressive reductions may increase:

    • missed connections;
    • baggage misconnects;
    • operational disruption.

    Local Minimum Connecting Time Groups must balance commercial competitiveness with operational realism.

    Infrastructure Limitations

    Some airports face constraints that cannot be resolved through scheduling alone.

    Examples include:

    • limited baggage system capacity;
    • long walking distances;
    • insufficient transfer facilities;
    • congestion during peak periods.

    In such cases, Minimum Connecting Times may remain relatively long until infrastructure improvements are completed.

    Global Coordination

    Because MCT changes affect reservation systems worldwide, updates must be synchronized carefully across airlines, Global Distribution Systems, airport systems, and technology providers.


    Future Outlook

    Resolution 765 will continue supporting increasingly sophisticated passenger and baggage transfer operations.

    Digital Airport Operations

    Future airports will use real-time operational data to monitor passenger and baggage transfer performance continuously.

    While published Minimum Connecting Times will remain standardized, airports may supplement them with predictive operational analytics to identify emerging bottlenecks.

    Artificial Intelligence

    Artificial intelligence is expected to assist Local Minimum Connecting Time Groups by analysing:

    • passenger movement patterns;
    • baggage transfer performance;
    • security processing times;
    • historical delay trends.

    These insights will support more evidence-based MCT reviews.

    Smarter Baggage Systems

    Advanced baggage handling systems using RFID, robotics, and automated sortation may reduce transfer times while improving reliability.

    Future MCT reviews may reflect these technological improvements.

    Growing Intermodal Integration

    As airlines expand partnerships with rail and other transport providers, Resolution 765 will increasingly support multimodal transfer planning, ensuring realistic connection intervals between different modes of transport while preserving operational consistency.


    Amendment Status

    Resolution 765 remains an active Passenger Services Conference standard governing the establishment and publication of Minimum Connecting Times. Recent Passenger Services Conference reviews have reaffirmed its core governance framework, including the responsibilities of Local Minimum Connecting Time Groups, the use of five-minute time increments, annual reviews, and publication through the Standard Schedules Information Manual (SSIM). While procedural refinements have accompanied changes in airport operations and technology, the Resolution’s fundamental objective—establishing realistic connection times for both passengers and checked baggage—remains unchanged.


    Key Takeaways

    • Resolution 765 defines the Minimum Connecting Time (MCT) as the shortest interval required to transfer both a passenger and their checked baggage at a specific location.
    • Minimum Connecting Times are determined locally through Local Minimum Connecting Time Groups (LMCTGs).
    • MCTs are based on airport infrastructure, passenger processing, baggage handling capability, security, immigration, and operational performance.
    • Approved values are published through the Standard Schedules Information Manual (SSIM) and implemented globally.
    • Reservation systems use published MCTs to prevent unrealistic flight connections.
    • The Resolution improves passenger connectivity and reduces baggage misconnects.
    • Annual reviews ensure MCTs remain aligned with changing airport operations.
    • Resolution 765 supports interline cooperation by providing mutually agreed transfer standards.
    • It complements IATA baggage standards by ensuring sufficient time for baggage transfer operations.
    • The Resolution continues to underpin reliable, efficient, and globally interoperable airline scheduling.

    Conclusion

    IATA Resolution 765 establishes the operational foundation for reliable interline passenger and baggage connections by ensuring that every published itinerary respects the actual capabilities of the airport through which it passes. By defining the Minimum Connecting Time as the shortest interval required to transfer both passengers and checked baggage, the Resolution integrates scheduling, passenger services, and baggage operations into a single coordinated framework.

    Its collaborative governance model, centred on Local Minimum Connecting Time Groups, enables airlines and airports to develop connection standards tailored to local infrastructure while maintaining global consistency through publication in the Standard Schedules Information Manual. This approach reduces missed connections, improves baggage transfer performance, strengthens interline cooperation, and enhances the passenger experience.

    As airports adopt advanced baggage handling systems, predictive analytics, automation, and increasingly integrated multimodal transport networks, Resolution 765 will remain a critical operational standard. Its emphasis on realistic, evidence-based connection intervals ensures that the global airline industry can continue delivering dependable passenger journeys and efficient baggage transfers in an increasingly complex aviation environment

    Share. Facebook Twitter Pinterest LinkedIn Tumblr Email
    Previous ArticleIATA RP 1740a–1740e: Ensuring Reliable Baggage Identification and Sortation Across the Global Network
    Next Article The Hidden Risk in Airline Pricing Algorithms: When Machines Learn to Keep Fares High
    yousuccess
    • Website

    Related Posts

    IATA RP 1740a–1740e: Ensuring Reliable Baggage Identification and Sortation Across the Global Network

    January 13, 2021

    IATA Resolution 741: Passenger Name and Address Label – The Enduring Fail-Safe for Lost Baggage Recovery

    January 13, 2021

    IATA RP 1743b: Tracing Unchecked Baggage and Handling Damage to Checked and Unchecked Baggage

    January 13, 2021
    Demo
    Latest Posts

    IATA Resolution 751 – Use of the 10-Digit License Plate

    March 10, 202213 Views

    IATA Resolution 752 – Electronic Baggage Claim Receipt

    March 10, 202213 Views

    IATA Resolution 753 – Baggage Tracking

    March 10, 20224 Views

    IATA Resolution 754 – Baggage Proration Profiles

    March 10, 20222 Views
    Stay In Touch
    • Facebook
    • Twitter
    • Pinterest
    • Instagram
    • YouTube
    • Reddit
    Don't Miss

    Radixx Res

    By yousuccessJanuary 17, 2021

    Market Position and Product Profile Radixx Res is the reservations and passenger-service core of the…

    IATA Resolution 743c – On‑Hand Baggage Summary Tag

    January 10, 2020

    IATA Resolution 751 – Use of the 10-Digit License Plate

    March 10, 2022

    Subscribe to Updates

    Get the latest news about Baggage and Trends to keep pace with aviation.

    Demo
    About Us
    About Us

    The aviation industry's trusted baggage resource. Discover expert articles, technical guidance, IATA baggage standards, operational best practices, baggage systems, and professional training designed to help airlines, airports, and ground handlers improve baggage performance, compliance, and the passenger experience.

    Need baggage expertise? We're available for consulting, training, operational audits, baggage system implementation support, and strategic partnerships.

    Email: info@baggagelogistics.com


    WhatsApp Us

    Facebook X (Twitter) Instagram Pinterest YouTube WhatsApp
    Our Picks

    IATA Resolution 751 – Use of the 10-Digit License Plate

    March 10, 2022

    IATA Resolution 752 – Electronic Baggage Claim Receipt

    March 10, 2022

    IATA Resolution 753 – Baggage Tracking

    March 10, 2022
    Most Popular

    Radixx Res

    January 17, 202118 Views

    IATA Resolution 743c – On‑Hand Baggage Summary Tag

    January 10, 202014 Views

    IATA Resolution 751 – Use of the 10-Digit License Plate

    March 10, 202213 Views
    © 2026 Baggage Logistics. Designed by Baggage Logistics.
    • Home
    • Passenger Services
    • Interline & Passenger Communications
    • Baggage Operations
    • Buy Now

    Type above and press Enter to search. Press Esc to cancel.