TRAFFIC ANALYSER RESOURCE CENTRE

We recommend customers use Google Chrome. OAG Traffic Analyser can be slow or not show correctly on some browsers.

The ‘Adjusted Preliminary’ data is loaded on the second weekend of each month and covers travel data for two months prior to the current month.

The ‘Adjusted Final’ data is loaded on the third weekend of each month and covers travel data for four months prior to the current month.

‘Unadjusted’ data is loaded on the second weekend of each month and covers travel data for two months prior to the current month. It also contains data for 12 months in the future.

OAG Traffic Analyser data is sourced from our partnership with Travelport and is comprised of many different data inputs including MIDT. Unadjusted bookings data is MIDT-based, while the average fare data is derived from Travelport issued tickets. Adjusted data for bookings is a modelled dataset that estimates the true total market figure. The model takes capacity, load-factor, MIDT, and various other external datasets as input and runs them
through a series of sophisticated proprietary algorithms to arrive at its estimates. Average fare data is still derived from Travelport issued tickets. The ‘Adjusted preliminary’ data is a draft version of the adjusted data as some of the external sources used in the model are not available yet. The ‘Adjusted final’ is the final version using all sources.

No, the selections you make are simply ways to narrow down the data to meet your requirements. For instance, if you select no carrier, the query pulls data for all airlines. Similarly, if you select no time period you will be extracting data from the entire OAG Traffic Analyser database. Obviously, to make analysis quick and meaningful it helps to carefully select only the data you need.

If you have selected a large amount of data, the query will take longer than if you select a small volume of data. Make sure you have defined the data required as precisely as you can.

OAG Traffic Analyser requires a lot of computer processing, even for relatively small queries and reports. If your query includes a long time period, or double connections, this significantly increases the amount of processing required. Any report which takes over an hour to process is timed out by OAG Traffic Analyser.

Selecting ‘one-way’ returns data from a specified origin to a specified destination only. ‘Twoway’ returns data for the same route, or origin-destination pair, but shows the data from the origin to the destination, as well as the destination to the origin as two separate records.

The O&D is the airports at the start and end of the route booked by the passenger, i.e. the origin and destination airport. Each non-stop flight taken is a flight segment. A passenger who connects at one or more intermediate airports will have several segments associated with their O&D.

The data sources for adjusted bookings and fares are different, but related. While Adjusted Bookings come from a modelled dataset that estimates the true total market figure, the fare data is supplied by Travelport only. Occasionally the adjusted bookings data gives a figure close to zero which OAG Traffic Analyser rounds down to zero, while the Travelport data may have a nonzero fare. Where Travelport has no fare data OAG Traffic Analyser reports the fare as zero.

The average fare excludes taxes, fees and fuel surcharges, but does include commission payments. Non-revenue tickets are excluded from the calculation. Data is supplied by Travelport in USD.

While schedule data has consistent patterns by day of week, airline traffic data does not. In order to make analysis meaningful, data is aggregated to a minimum period of one month.

It doesn’t matter. You only need to select one of the names as Analyser pulls all the data by code as long as the code is the same.

The ‘Mix’ is the combination of the four types of passenger journeys represented on a single flight segment. These are ‘local’, beyond’, ‘behind’ and ‘bridge’ traffic.
− ‘Local’ traffic means those passengers flying non-stop on the flight segment.
− ‘Beyond’ traffic means those passengers flying onwards from the non-stop flight segment to another destination i.e. they take a connecting flight.
− ‘Behind’ traffic means those passengers who connected from another flight before travelling on this non-stop flight segment.
− ‘Bridge’ traffic means those passengers who connected onto this non-stop flight segment and will connect again onto another flight.
The diagram below illustrates each type of traffic.

The Point of Origin for a booking is the place where the passenger started their journey. This means that it might be different to the ‘Origin’ for the flight segment(s) as the passenger might be travelling on the return leg of a booking.

Each tab is calculated separately and sometimes numbers are rounded at different points in the calculation which means the numbers may not match exactly.

When you specify a carrier in a query in Traffic Analyser the default search presumes that the carrier is the dominant carrier on the routing, i.e. that the carrier is used for the longest leg of the routing. The Advanced Carrier function allows you to over-ride this and identify a specific carrier for any leg of the routing. This is especially useful when analysing traffic feed on short domestic sectors which feed long haul routes.

Traffic Analyser now includes a feature which allows the user to identify unserved routes.These are routes where there are passengers travelling between two points via connecting airports but there are no direct air services.

No. You are just logged out of the individual product but still logged on to the OAG Analyser dashboard (portal). If you are inactive on Traffic Analyser for 1 hour your session will timeout. Within the dashboard the inactive timeout is 12 hours. One user can have only one active session in the dashboard or Traffic Analyser at a time.