Indian Airlines On Time Performance Explained

On-time performance, or OTP, is a monthly average, not a promise about your flight. The Directorate General of Civil Aviation (DGCA) counts a domestic departure as "on time" if it leaves within a set tolerance of its published schedule, commonly 15 minutes, then averages that across a basket of airports for the month. What most people read into the headline number is a forecast for their own flight tonight. What the number actually is, is a rear-view mirror pointed at last month.

What "on-time performance" actually measures

DGCA's OTP figure is built from one comparison, repeated across a month of departures: the scheduled time an airline files, against the time the aircraft actually leaves the gate. A departure inside the tolerance counts as on time; one outside it does not. According to a May 2026 explainer on how to read DGCA's data, the tolerance commonly applied is 15 minutes late, and the metric is computed as a monthly average across a basket of major Indian airports, historically the four metros of Delhi, Mumbai, Bengaluru and Hyderabad, later widened to roughly ten airports with the addition of Chennai, Kolkata, Ahmedabad, Cochin, Guwahati and Lucknow (flightgpt.in, 2026-05-12).

Two things follow from that design. First, the number is a departure-side measure. It says nothing, by itself, about whether the aircraft then made up time in the air or lost more of it, or about what happened at the arrival end. Second, it is an average across every departure DGCA counted at those airports that month, not a figure attached to the specific flight you are booking. A carrier's OTP tells you how that airline behaved as a fleet, over roughly thirty days, at the airports DGCA tracks. It is a useful trend line. It is not a receipt for tonight's departure.

DGCA publishes the figure monthly, folded into its wider air-transport report alongside traffic, cancellations and complaint counts for scheduled domestic carriers.

What the published percentage does not tell you

Three gaps sit underneath every OTP headline, and none of them show up in the number itself.

The first is individual-flight risk. An airline running an 88% monthly OTP is still, by definition, late on roughly 12% of its departures that month (flightgpt.in, 2026-05-12). A high average does not mean your specific flight is protected; it means the airline was mostly on time across many flights, which is a different statement.

The second is what happens to cancellations. OTP is a percentage of flights that operated on schedule, out of flights that operated. A flight that never left the ground at all is not the same event as a late departure, and depending on how it is folded into the base, a bad month for cancellations can sit outside the OTP figure entirely rather than dragging it down (flightgpt.in, 2026-05-12). A traveller reading the percentage alone has no way to see that.

The third is severity. The metric is binary: a departure is either inside the tolerance or it is not. A flight sixteen minutes late and a flight delayed four hours both register as one "not on time" event, with nothing in the headline figure to tell them apart. Two airlines could post the same OTP in a given month for very different traveller experiences, one running mostly-minor slippage and the other running a smaller number of severe delays (flightgpt.in, 2026-05-12).

None of this makes the metric useless. It makes it a monthly average that answers "how did this airline generally run last month," and not "what will happen on my flight," "did I lose my whole day," or "is this airline actually cancelling more than it reports."

Reading an airline's number without over-trusting it

A single dated example shows how differently this figure can read even within the same month, once you look past one national average. For May 2026, one outlet's read of DGCA's air-traffic report put Chennai International at 92.2%, the highest OTP among the ten major airports the report covers (tradebrains.in, 2026-07-12). The same national carrier can post very different OTP at different airports in its own network, since congestion, weather and slot pressure vary by airport, not by airline brand. A carrier's month-level OTP is an average over exactly that kind of variation, which is one more reason not to read it as a per-airport, let alone a per-flight, guarantee.

A more useful reading habit than chasing the single headline number: treat OTP as one input alongside the route and the season you are actually flying, and hold every figure to a specific month and a specific, named source, the way the two figures in this post are dated and sourced above, rather than repeating a percentage that has drifted out of date.

FAQ

What counts as "on time" in DGCA's data? A departure inside a set tolerance of the airline's published schedule, most often cited as 15 minutes, per the DGCA-based reporting above.

Does OTP measure arrival delays too? The figure most commonly reported and cited is departure-based. It does not, by itself, tell you what happened between departure and arrival, or how a delay picked up in the air.

Why can two airlines report the same OTP but feel very different to travellers? Because OTP treats every delay outside the tolerance the same way, with no distinction between a short slip and a multi-hour delay, and because cancellations do not necessarily count the same way a late departure does. Two carriers can land on an identical percentage from very different underlying months.

How TrackMyWings helps

TrackMyWings™ carries directory pages for Air India, IndiGo and SpiceJet, for looking up a carrier before reading its punctuality in DGCA's own monthly figures. A private beta of the TrackMyWings app shipped on Android on 2026-08-24, on the Play internal testing track; there is no fixed public launch date. Planned features, including gate and status alerts, are on the roadmap and not yet shipped.

Sources

• flightgpt.in, "Airline On-Time Performance India 2026: How to Read DGCA Data", published 2026-05-12, captured 2026-09-23. Definition, tolerance, airports covered, publication cadence, and the three named limitations of the metric.
• tradebrains.in, "Chennai Airport Tops as India's Most Punctual Airport as Per DGCA Report", published 2026-07-12, citing DGCA's air-traffic report for May 2026, captured 2026-09-23. The Chennai 92.2% worked example.
• DGCA's and the Ministry of Civil Aviation's own on-time-performance pages were checked directly during research for this post; both returned an access error and could not be fetched. The two outlets above name and date the DGCA report each is citing; see facts.md for the fetch attempt and what is and is not claimed from it.