The Leg Connect Traffic report, illustrated in Figure 1, highlights variations in passenger numbers and revenue generated from connecting traffic through specific flight legs. It will specifically display the top 5000 records with the most significant revenue change, categorized by operating airline, origin airport and destination airport. Remaining records will be collectively aggregated and represented as ‘~ ~’ to ‘~ ~’.
You need to run the Segment Comparison before assessing the updated results in this report.
This image is password protected.
Table 1 below outlines the data structure, with the data metrics aggregated by the field with a key icon (
).
| Field | Description |
| Alliance | Alliance name. “~ ~” for the aggregation of all independent airlines. |
| AL_Group | Airline group defined in the Group_Airline table. If an airline is not part of any group, its airline code will be used. |
| AL | IATA code of the operating airline on the segment |
| Org | Segment origin airport code. “~ ~” for the aggregation outside the top 5000 records. |
| Dst | Segment destination airport code. “~ ~” for the aggregation outside the top 5000 records. |
| Pax_Change | Variation in passenger count between the ‘before’ case and the ‘after’ case during the target month |
| Rev_Change | Change in revenue, measured in USD, from the ‘before’ case to the ‘after’ case within the target month |
| Annual_Pax_Chg | Annualized variation in passenger count (equals to Pax_Change * 12) |
| Annual_Rev_Chg | Annualized revenue change (equals to Rev_Change * 12) |