Our new endpoint allows geolocating nearby airports by IP address. We already have an endpoint returning nearest airports by making use of the coordinates (latitude and longitude) as an input. The new endpoint complements this set. It geolocates the coordinates internally by using the IP address as an input, and returns airports, closest to that …
We now return ICAO and IATA airline codes as part of API responses from any flight endpoints, whether it is FIDS or flight status. Earlier, we only returned the name of the airline. The change will only apply to the flights, where the airline / operator could be correctly mapped. This is valid for the …
We have significantly expanded the capabilities of our airport delays endpoint. This endpoint is designed to get a statistical insight of the “smoothness” of flight operations in this or that airport. Until recently, it only allowed you to trace this information in real-time only. We have now changed several things: [UPDATED] Airport delays endpoint now …
Introducing Historical Airport and Global Delays Read More »
We support keeping aircraft registration history separately from a specific airframe. This includes the tail numbers and periods of registration. With AeroDataBox API it’s now possible to get an insight into historical aircraft registrations.
We’re introducing a new big feature: Flight Alert PUSH API. It facilitates the delivery of flight data in a fundamentally different manner. Instead of polling flight status or FIDS endpoint again and again in order to get data updates, you can now subscribe to a certain flight or airport and get notified automatically whenever an …
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 …
Improved flight delay statistics, flight delay brackets and flight locations for FIDS Read More »
We are continuing to expand capabilities related to analyzing actual flight tracks with reliance on community-maintained ADS-B data provided by third-party. Attentive users could have already noticed that for some airports AeroDataBox API has started providing: Flight runway data, which we introduced as a response to requests of a few users to have some capabilities …
We are introducing more capabilities to search for flight status. From now on, you can look for individual flight information not only by flight number but also by ATC call-sign, registration or 24-bit ICAO Mode-S hexadecimal transponder address of the aircraft operating the flight. New search capabilities are delivered by introducing new endpoints: Flight by …
Here are some updates regarding the API made in recent weeks: USA LIVE FLIGHTS COVERAGE We have integrated live flight updates for the airports in the USA, which is a huge live flight data coverage expansion (almost 400%). Updates are based on flight plan data and include aircraft registration and model, flight status, scheduled, estimated …
There weren’t many updates recently. Due to independent personal circumstances, we can’t devote much time to developing AeroDataBox at the moment, unfortunately. Nevertheless, there is some new stuff in the API: FIDS endpoint now has additional query string boolean parameter “withLeg”. When set to true, the response will contain times of arrival at destination for …
FIDS with Extended Information, Flight Time and Distance Read More »