Improved flight delay statistics, flight delay brackets and flight locations for FIDS

  1. We have updated our “Flight delay statistics by flight number” endpoint. Earlier delay records of the same flight number were grouped by origins and destinations. This way you could separately see how much the flight is delayed in each airport it departs from or arrives at. From now on, groups are as well segregated by scheduled hours. This way you can see separate statistics for the flights commencing at different hours. This prevents mixing the statistics when, for instance, the airline changes the schedule or when there are multiple flights with the same number commencing at the same airport on the same day. The hour is reflected in the additional property “scheduledHourUtc” in each item within the “origins” or “destinations” collection of the endpoint response.
  2. Moreover, each item of these collections now contains several additional properties, including the number of flights considered for calculation, period of calculation, and, brackets containing more detailed information about how many flights were delayed/early per specific delay range brackets (e.g. late from 15 to 30 minutes, from 30 to 60, etc.), so you can precisely say how many flights on this route were delayed within, for instance, not more than 30 minutes and compare it with the total number of flights commenced. This will allow you to draw conclusions regarding the recent punctuality of the flight with better precision. Brackets are currently experimental and likely to be adjusted in the nearest future.

    Statistics are available only for flights commencing at airports that have live updates data coverage.

    Please take a moment to review the updated documentation for this endpoint as well as try it in RapidAPI playground

One more change is for FIDS / Schedules endpoint. Now it contains the experimental “withLocation” parameter. If set to “true”, the system will attempt to retrieve the current location, track, speed, and pressure altitude for the flights returned in the response. It is applicable for flights currently en route and having either ATC call-sign, registration, or Mode-S ICAO 24-bit address known.

This feature is reliant on previously introduced ADS-B-based flight data augmentation as well as on the current ADS-B territorial range. The latter is generally wider than the per-airport ADS-B coverage mentioned on the “Data coverage” page, that’s why you may receive locations for flights in airports not necessarily having ADS-B feed active. However, location won’t be present if the airplane is currently out of range. The feature is purely experimental, can be slow, and may move to a separate endpoint in the future.

Please take a moment to review the updated documentation for this endpoint as well as try it in a RapidAPI playground.