This tool is available for
Fligence Planning offers a specialized tool designed for network planners to identify and assess the impact of missed connections within your current flight schedules.
To initiate the creation of a Missed Connections Report for a host airline, simply select the Missed Connections option and set the desired time window for analysis, expressed in minutes as needed. Kindly be aware that the Missed Connection option will appear only after you click the More Options button, as shown in Figure 1.
Once the analysis scenario is executed, the Missed Connections report will be updated and can be accessed by navigating to Planning > Analytical Reports > Missed Connects on the Fligence platform, as shown in Figure 2.
This report provides valuable insights into the potential increase in passenger numbers and revenue that could be achieved by adjusting the timing of existing flights, thus facilitating additional connection opportunities. The specified time window will define the limit for permissible adjustments to create these new connecting flights.
Please note that the analysis considers only single connections, encompassing online, codeshare, and interline partnerships. The estimated value of the missed connections is calculated using a Quality Service Index (QSI) forecast for itineraries that were not connected due to timing constraints.
Table 1 below outlines the data structure, with the data metrics aggregated by the combination of fields with a key icon (
).
| Field | Description |
| Org | IATA code of the trip origin airport |
| Cnx | IATA code of the connecting airport |
| Dst | IATA code of the trip destination airport |
| Opt_AL1 | IATA code of the operating airline of the first flight leg |
| Opt_Al2 | IATA code of the operating airline of the second flight leg |
| Type | Connection type: Online: a connection of two flights with the same marketing airline Interline: a connection of two flights with different marketing airlines Codeshare: a connection of two flights, one of which is codeshared |
| Missed_Minutes | Extra minutes required to meet the minimum connection time |
| Pax | Number of passengers on the connection during the target period |
| Revenue | Revenue generated by the connection |
| Dep_Time1 | Local departure time of the first flight in the HHMM format |
| Arr_Time1 | Local arrival time of the first flight |
| Dep_Time2 | Local departure time of the second flight |
| Arr_Time2 | Local arrival time of the second flight |
| Arr_Offset | Number of days when passengers arrive after the entire connected trip. -1: arrive on the previous day due to time zone differences 0: arrive on the same day 1: arrive on the next day 2: arrive two days later |
| Flight_No1 | Operating flight number of the first flight |
| Flight_No2 | Operating flight number of the second flight |
| Miles1 | Mileage of the first flight leg |
| Miles2 | Mileage of the second flight leg |
| DOW | Operating day of week based on the departure time of the first flight (1: Monday, 2: Tuesday, …, 7: Sunday) |
| QSI | QSI score of the connection record |
| Market_QSI | QSI score for the Origin-Destination (O&D) market |
| Market_Share | Traffic share of the connection over all services for the same O&D market |
| Market_Pax | Total number of passengers in the O&D market during the target period. The same number will be repeated across different lines if there are multiple online connection records in the same market. |