Three Myths About Airport Punctuality

While Ryanair is boasting to be the most punctual European airline, Oman Air celebrates one day of 100% on-time performance on April 26 this year. Unfortunately there is no public data that proves any of these claims.

What about airports? In April 2011 London Heathrow published a record 94% departure punctuality.  Now they are Britain's worst airport according to the Civil Aviation Authority (CAA).

I think it's time to wade through some of the myths and confusion surrounding airport punctuality.

1. Punctuality is an internationally standardized metric.

Punctuality targets are usually defined in terms of 15-minute punctuality, i.e. a flight is counted as departing on-time if the plane goes off-blocks within 15 minutes of the scheduled time of  departure. But what is "15 minutes"? Is it more than 14'59" or more than 15' or even more than 15'59"? Now some airports and airlines may disagree on this but even ACI, IATA and AEA don't. If they do, then it will probably be 15'59", stealing another minute from the passenger, airline and airport capacity just to look better.

And, have you compared off-blocks times of airport and airline? Some airports check and validate differences within +/- 1 minute, most don't. Result: airport and airline report different punctuality figures.

2. Punctuality is a great metric to benchmark.

In previous posts I was highlighting some flaws of punctuality as a metric.

• Cancellations of delayed flights improve punctuality
• Indicator ignores size of aircraft and number of passengers affected
• No assessment about the financial loss possible
• Mix of performance which can be influenced with exogenous factors
• Difficult to determine improvement measures

Why is it still used, even as internal target? Because it is easy to understand and when it is bad, it can be easily attributed to exogenous factors.

3. Eurocontrol A-CDM improves airport punctuality.

There is no evidence that ECTRL A-CDM improves punctuality. Yes, it might reduce taxi times but with a negative effect on departure punctuality. With the lack of evidence I did some research myself and present the findings in my next post.

I know it is easy to lament. What do I have to offer instead? An approach and metrics to actually address the issue together with other stakeholders. Because the airport can have that 360° view and not just the silo view by every other stakeholder.

The 7 habits of highly effective punctuality management

As soon as an airport or an airline has a punctuality record month, they publish press releases, they celebrate. But how sustainable is such a short-time success? If you check their performance from then on, you may find them falling back to the levels before.

Can on-time performance be actively managed? If you think it can't be managed or can only be resolved by others, the following 7 habits may present a different perspective. If you already manage punctuality, you can assess where you are in your quest.

Habit	Characteristics
Accountability	There is a sufficient number of delay codes to differentiate delay causer Each delay code (with sub-code) has an owner or responsible organization The delay code assignment process is clear and in place (assign, accept, reject, handling of disputes, final call). Secondary delays are allocated to the original causer Delay cost is calculated and assigned to the causer
Transparency	Delay code assignment and on-time performance of every organization is transparent to everybody. Data quality is high Share performance with other airports
Standardization	Only one definition of delay codes and delays across the airport based on IATA standard, incorporated in the Airport Handling Manual (AHM) Any non-conformance e.g. different reporting from an airline to its head office will be brought forward to the Governance Forum
Governance and Benchmarking	Multi-stakeholder Airport Operations Control Center to manage the daily operational on-time performance and escalations Has a Punctuality Manager Punctuality Board, chaired by the Airport's Punctuality Manager, with delegates from handling agents and airlines proposes and tracks actions Punctuality targets are defined and broken down to each stakeholder Maybe an award/penalty pool for on-time performance Benchmark against other airports
System Integration	Delay codes and delays are captured or integrated into one 'global' system. That system should also allow to automatically track issues of a flight which could have caused the delay in case of disputes.
Communication/PR	Constant, effective communication among all stakeholders Maybe an award for the best punctuality improvement program
Empowerment	Agree on challenging yet achievable goals but leave it up to the partners to implement sustainable improvement Provide sufficient resources for punctuality management and improvement programs

Airlines, tell us your punctuality

The Association of European Airlines (AEA) used to publish the on-time performance (punctuality) of their associated airlines. It seems that their airline members would not allow this anymore. Certainly you can use Flightstats, however, the information may prove inaccurate and incomplete. Wolfram search has a nice feature to learn more about airlines (US only) delays. Just enter the search term 'causes of delay of delta airline' and you will find a nice summary of Delta's performance as an example.

In a bold new move, South African domestic carriers have agreed with Airports Company South Africa (ACSA) to publish their punctuality on the ACSA web site. Passengers can take this into consideration upon choosing their carrier and the Airport makes a clear statement about the strategic value of on-time performance.

I'd rather have this continuous level of transparency than campaigns of carriers or airports which coincidentially happened to be the most punctual recently - irrespective of their size, number of cancellations, and number of passengers affected.

Hidden Issues Behind 99.9% Service Level

Your IT Director is surely proud to constantly deliver 99.9 and more percentage of availability of systems and network. Though it is probably the most commonly used metrics, it is not necessarily the best metrics to use. It does not, for instance, tell you anything about the impact of a downtime or outage. What we usually would be presented are great uptime graphs like this one:

What does this tell us really?

Imagine this, due to a network or system issue, check-in is not possible for an hour. The check-in agents will have to fall back to manual check-in. In addition to cost of additional staff, this may result in flight delays. Again, what is your plan to address this? Buy more technology? What is the ROI?

What if you knew the delay cost of the affected flights and could relate this to the responsible IT department? You then could trade an investment off against the cost of downtimes.