You can get all global flight information in 1 API call or track flights based on flight number, airline, departure/arrival airport, and more. The data updates frequently, around every 5 minutes. The details of the data include:

Geography: Location information such as latitude, longitude, altitude, and direction. Speed: Vertical and horizontal speed of aircraft. Departure and arrival: IATA codes and ICAO codes of the departure and arrival airport. Aircraft and flight: IATA and ICAO number of flight and registration number, ICAO code, and ICAO24 code of aircraft. Airline: IATA code, and ICAO code of airline. System information: Squawk, status, and last updated in Epoch.

Here's an example response from the API: [ { "geography": { "latitude": 43.5033, "longitude": -79.1297, "altitude": 7833.36, "direction": 70 }, "speed": { "horizontal": 833.4, "isGround": 0, "vertical": 0 }, "departure": { "iataCode": "YHM", "icaoCode": "CYHM" }, "arrival": { "iataCode": "YQM", "icaoCode": "CYQM" }, "aircraft": { "icaoCode": "B763", "regNumber": "CGYAJ", "icao24": "C08412" }, "airline": { "iataCode": "W8", "icaoCode": "CJT" }, "flight": { "iataNumber": "W8620", "icaoNumber": "CJT620", "number": "620" }, "system": { "updated": 1513148168, "squawk": "0000" }, "status": "en-route" } ]

Developer Information:

1) Available Endpoints &depIata= &depIcao= &arrIata= &arrIcao= &aircraftIcao= &regNum= &aircraftIcao24= &airlineIata= &airlineIcao= &flightIata= &flightIcao= &flightNum= &status= &limit= &lat=&lng=&distance=

2) Flights Tracker API Output

Specific flight based on: Flight IATA Number: GET http://aviation-edge.com/v2/public/flights?key=[API_KEY]&flightIata=W8519

All flights of a specific Airlines: GET http://aviation-edge.com/v2/public/flights?key=[API_KEY]&airlineIata=W8

Flights from departure location: GET http://aviation-edge.com/v2/public/flights?key=[API_KEY]&depIata=MAD

Flights from arrival location: GET http://aviation-edge.com/v2/public/flights?key=[API_KEY]&arrIata=GIG

Flights within a circle area based on lat and lng values and radius as the distance: GET https://aviation-edge.com/v2/public/flights?key=[API_KEY]&lat=51.5074&lng=0.1278&distance=100&arrIata=LHR

Combinations: two airports and a specific airline flying between them: GET http://aviation-edge.com/v2/public/flights?key=[API_KEY]&depIata=ATL&arrIata=ORD&airlineIata=UA

The Schedules API service provides real-time data for the flight schedules and timetables of airports and airlines around the world and maintains this for you in our central database, always accessible with your personal API key. This is one of Aviation Edge’s core features. You can build real-time airport departure and arrival tables, keep track of delays and cancellations, track the status of flights by using our API. The data comes in JSON format, making it useful to implement to websites and build applications, tools, software, and more.

The data includes the following: - Flight Status: active, scheduled, landed, cancelled, incident, diverted, redirected. - Airport details: IATA code, ICAO code, Terminal, Gate for both departure and arrival airport - Take-off information: Scheduled, estimated and actual times on runway and that of departure/arrival. - Total delay (updated for departures) - Airline: Name, IATA code and ICAO code. - Flight: Number of Flight, IATA prefix with flight number and ICAO prefix with flight number.

Example response from the API:

[ {"airline": {"iataCode":"DL", "icaoCode":"DAL", "name":"Delta Air Lines"}, "arrival": {"actualRunway":"2021-03-03T04:15:00.000", "actualTime":"2021-03-03T04:15:00.000", "baggage":"T4", "delay":null, "estimatedRunway":"2021-03-03T04:15:00.000", "estimatedTime":"2021-03-03T04:15:00.000", "gate":"B41", "iataCode":"JFK", "icaoCode":"KJFK", "scheduledTime":"2021-03-03T05:05:00.000", "terminal":"4"}, "codeshared":null, "departure": {"actualRunway":"2021-03-03T00:10:00.000", "actualTime":"2021-03-03T00:10:00.000", "baggage":5, "delay":"16", "estimatedRunway":"2021-03-03T00:10:00.000", "estimatedTime":”2021-03-03T00:10:00.000”, "gate":"B06", "iataCode":"TLV", "icaoCode":"LLBG", "scheduledTime":"2021-03-02T23:55:00.000", "terminal":"3"}, "flight": {"iataNumber":"DL235", "icaoNumber":"DAL235", "number":"235"}, "status":"landed", "type":"arrival"} ]

Output:

For the departure schedule of a certain airport. GET http://aviation-edge.com/v2/public/timetable?key=[API_KEY]&iataCode=JFK&type=departure

For the arrival schedule of a certain airport. GET http://aviation-edge.com/v2/public/timetable?key=[API_KEY]&iataCode=JFK&type=arrival

Market Analysis of Flight Data API The global Flight Data API market is expanding rapidly, with an estimated market size of USD XXX million in 2025 and a projected CAGR of XX% during the forecast period of 2025-2033. The increasing demand for real-time flight information by airlines, travel agencies, and businesses is driving the market growth. Additionally, the rising adoption of cloud-based solutions, advancements in data analytics, and the proliferation of mobile devices are contributing to the market's expansion. Key market trends include the integration of Flight Data APIs with travel booking platforms, the development of predictive analytics to optimize flight operations, and the emergence of low-cost carriers and budget airlines driving the demand for affordable flight data. However, data privacy concerns, limitations in data coverage, and the availability of alternative flight data sources may restrain market growth. The market is segmented based on application (SMEs and large enterprises), type (cloud-based and on-premises), and region (North America, Europe, Asia Pacific, South America, and Middle East & Africa). Prominent market players include Aviationstack, FlightAware, OpenSky, Cirium, and Trawex. This report provides comprehensive insights into the Flight Data API market, covering key trends, drivers, challenges, and opportunities. It analyzes the market landscape, including market size, segmentation, and competitive analysis, to provide a clear understanding of the market dynamics. The report also includes detailed profiles of key players in the industry, providing valuable insights into their strategies, product offerings, and financial performance.

You can connect to the actual flight routes around the world with your API key at any time with very fast response times. It is possible to view all routes at the same time via a single API key. For your convenience, we have also developed many different filters so that you can pull the exact data you are looking for. This way, you may get data of the routes of a specific airline, routes from or to a specific airport (both IATA and ICAO codes work), or may get an individual flight based on its flight number.

A common use of the air routes API is to develop software in the aviation industry. While Aviation Edge’s focus is to collect and maintaining aviation data, you are free to develop countless applications, tools, and platforms by using our data.

The details included in the routes data are: Departure data: IATA code, ICAO code, terminal, and time. Arrival data: IATA code, ICAO code, terminal, and time. Airline: IATA code of airline. Flight: Flight number. Aircraft: Registration number of the aircraft.

Here's an example response from the API: [ { "departureIata": "OTP", "departureIcao": "LROP", "departureTerminal": 2, "departureTime": "09:15:00", "arrivalIata": "TRN", "arrivalIcao": "LIMF", "arrivalTerminal": 1, "arrivalTime": "10:45:00", "airlineIata": "0B", "airlineIcao": "BMS", "flightNumber": "101", "codeshares": null, "regNumber": "YR-BAP" } ]

Developer information: 1) Available Endpoints &departureIata= &departureIcao= &airlineIata= &airlineIcao= &flightNumber=

2) Output Airports, Airlines or Flights routes output: GET http://aviation-edge.com/v2/public/routes?key=[API_KEY]&departureIata=OTP GET http://aviation-edge.com/v2/public/routes?key=[API_KEY]&departureIcao=LROP GET http://aviation-edge.com/v2/public/routes?key=[API_KEY]&airlineIata=0B GET http://aviation-edge.com/v2/public/routes?key=[API_KEY]&airlineIcao=BMS GET http://aviation-edge.com/v2/public/routes?key=[API_KEY]&flightNumber=101 For information about a specific route (example). GET http://aviation-edge.com/v2/public/routes?key=[API_KEY]&departureIata=OTP&airlineIata=0B&flightNumber=101

The historical flight schedule data is perfect to create applications, plugins for websites, running analysis and creating statistics, keeping track of past delays and cancellations for insurance or flight compensation claims, and much more.

We have developed many parameters you can use to pull the exact data you need without having to spend too much time filtering it on your end. We've asked many developers around the world to find out which pieces of data they would need the most, and created the parameters based on this feedback.

The data includes: - Airline: Name, IATA and ICAO codes of the airline. - Departure and arrival: IATA codes and ICAO codes of the departure and arrival location. - Departure and arrival times: Scheduled, estimated and actual arrival and departure times, as well as runway times in local time. - Status: The latest status information of the flight which may be active (for departure schedules), landed (for arrival schedules), cancelled or unknown - Delay: Total delay amount in minutes for delayed flights

Example response from the API: { "type": "departure", "status": "active", "departure": { "iataCode": "jfk", "icaoCode": "kjfk", "terminal": "7", "delay": 10, "scheduledTime": "2020-09-25t20:15:00.000", "estimatedTime": "2020-09-25t20:09:00.000", "actualTime": "2020-09-25t20:25:00.000", "estimatedRunway": "2020-09-25t20:25:00.000", "actualRunway": "2020-09-25t20:25:00.000"}, "arrival": { "iataCode": "lhr", "icaoCode": "egll", "terminal": "5", "scheduledTime": "2020-09-26t08:20:00.000", "estimatedTime": "2020-09-26t07:32:00.000" }, "airline": { "name": "aer lingus", "iataCode": "ei", "icaoCode": "ein" }, "flight": { "number": "8814", "iataNumber": "ei8814", "icaoNumber": "ein8814" }, "codeshared": { "airline": { "name": "british airways", "iataCode": "ba", "icaoCode": "baw" }, "flight": { "number": "114", "iataNumber": "ba114", "icaoNumber": "baw114"} } },

2) Historical Schedules API Output - Developer Information For the departure schedule of a certain airport on a certain date. GET http://aviation-edge.com/v2/public/flightsHistory?key=[API_KEY]&code=JFK&type=departure&date_from=YYYY-MM-DD

For the arrival schedule of a certain airport on a certain date. GET http://aviation-edge.com/v2/public/flightsHistory?key=[API_KEY]&code=JFK&type=arrival&date_from=YYYY-MM-DD

For the schedule of a certain airport of a certain date range (also available for arrival). GET http://aviation-edge.com/v2/public/flightsHistory?key=[API_KEY]&code=JFK&type=departure&date_from=YYYY-MM-DD&date_to=YYYY-MM-DD

For the schedule of a certain airport on a certain date (or range) but only flights with a certain status. GET http://aviation-edge.com/v2/public/flightsHistory?key=[API_KEY]&code=JFK&type=arrival&date_from=YYYY-MM-DD&date_to=YYYY-MM-DD&status=cancelled

For tracking individual historical flights. GET http://aviation-edge.com/v2/public/flightsHistory?key=[API_KEY]&code=JFK&type=departure&date_from=YYYY-MM-DD&date_to=YYYY-MM-DD&flight_number=[1234]

For filtering the flights of a certain airline from the arrival schedule of a certain airport on a certain date (also available for departure schedules and as a date range). GET http://aviation-edge.com/v2/public/flightsHistory?key=[API_KEY]&code=JFK&type=arrival&date_from=YYYY-MM-DD&&airline_iata=TK

Important Tips: - Currently possible to get dates that are up to 1 year earlier than the current date (this will expand soon). - The date range can go up to 28 days for a single API call but may be shorter around 3-5 days for airports with heavy traffic.

The flight search software market is experiencing robust growth, driven by the increasing adoption of online travel booking platforms and a surge in air travel globally. The market's expansion is fueled by several key factors. Firstly, the increasing penetration of smartphones and internet access, particularly in emerging economies, is leading to a substantial rise in online flight bookings. Secondly, the constant innovation in flight search technologies, including AI-powered personalized recommendations and advanced fare prediction algorithms, is enhancing user experience and driving market adoption. Thirdly, the growing preference for seamless and convenient booking experiences is pushing both airlines and online travel agencies (OTAs) to invest heavily in sophisticated flight search software. Competition amongst OTAs is also a significant factor, leading to continuous improvement and feature enhancements in their software offerings. The market is segmented by deployment type (cloud-based and on-premise) and user type (private and commercial). Cloud-based solutions are witnessing rapid growth due to their scalability and cost-effectiveness. Commercial users, encompassing airlines and OTAs, dominate the market share, driven by their need for comprehensive flight data and booking management capabilities. While the on-premise segment still holds a significant share, it's projected to witness slower growth compared to cloud-based solutions in the coming years. Geographic distribution shows robust growth across North America and Europe, attributed to high internet penetration and established online travel markets. However, growth in Asia-Pacific is expected to be particularly significant in the forecast period due to increasing disposable incomes and rising air travel demand in countries like India and China. Challenges include maintaining data accuracy, ensuring data security, and adapting to constantly evolving airline pricing and scheduling practices. The forecast period (2025-2033) anticipates continued market expansion, with a projected CAGR (Compound Annual Growth Rate) of approximately 12%, a figure derived from considering the historical growth trends and current market dynamics. This growth is expected to be fueled by ongoing technological advancements, increasing competition, and a sustained rise in global air travel. While regulatory hurdles and data privacy concerns pose potential restraints, the overall trajectory points towards a consistently expanding market for flight search software. The major players listed (Google, Momondo, Fareportal, TripAdvisor, etc.) are expected to continue their dominance, but smaller, innovative companies could disrupt the market with specialized niche solutions or disruptive technology. Growth will likely be most pronounced in areas with rising internet and mobile penetration and expanding middle classes.

Explore comprehensive insights in Leads Rank TLD profiles, featuring detailed information for .flights. Utilize our API for efficient data access.

The airports the API returns include airports that have the submitted letters anywhere in them. For example, when the letters "ist" are requested, the API returns both "Istanbul Airport" and "Bristol Airport" (among other items).

The API is particularly useful for travel agency and flight booking websites, tools or apps to display the relevant airport and cities as a list for the user to choose from.

The city and airport data the Autocomplete API returns include: - IATA code and name, - Country code and name, - Airport location (latitude and longitude) - Time zone

1) Example Fields of Use - Travel agency and flight booking/schedule tracking websites, tools, apps where users are expected to submit a departure or arrival city or airport - Any autocomplete feature related to cities or airports

2) Example Input Airports and cities with the letters containing "xyz" in them:

GET http://aviation-edge.com/v2/public/autocomplete?key=[API_KEY]&city=xyz

3) Example Output [ { "code": "AMS", "name": "Amsterdam", "cityCode": "AMS", "cityName": "Amsterdam", "countryCode": "NL", "countryName": "Netherlands", "lat": 52.3730556, "lng": 4.8922222, "timezone": "Europe/Amsterdam", "type": "city" } ], "airports": [ { "code": "ZYA", "name": "Amsterdam Centraal Railway Station", "cityCode": "AMS", "cityName": "Amsterdam", "countryCode": "NL", "countryName": "Netherlands", "lat": 52.3730556, "lng": 4.8922222, "timezone": "Europe/Amsterdam", "type": "rail_station", "isRailRoad": 1, "isBusStation": 0 }, { "code": "AMS", "name": "Schiphol", "cityCode": "AMS", "cityName": "Amsterdam", "countryCode": "NL", "countryName": "Netherlands", "lat": 52.30907, "lng": 4.763385, "timezone": "Europe/Amsterdam", "type": "airport", "isRailRoad": 0, "isBusStation": 0 } ], "airportsByCities": }, ... ]

REQUIRED: A brief narrative summary of the data set.

Information such as airline name, airport name, airport code, regular flight schedule start date, end date, flight number, day information, season code value, code number classification, master flight number, etc. Passenger flight schedule information service in multiple languages (Korean, English, Japanese, Chinese) This data is data for one season (summer end of March to end of October/winter end of October to end of March of the following year), and the update cycle is different from the above 3 APIs. * Passenger flight operation status detailed inquiry service API, passenger flight weekly operation status API, passenger flight operation status (multilingual) API

Flight Express S A Company Export Import Records. Follow the Eximpedia platform for HS code, importer-exporter records, and customs shipment details.

International Round-Trip Flight Prices Dataset (SQLite)

This project collects international round-trip flight pricing data over a defined date range and duration from Atlanta (ATL) to 9 international destinations. It saves this structured flight information to a SQLite database and enables flexible downstream querying and visualization. Each entry represents a real flight quote retrieved from a travel search API under fixed conditions. The data is structured, time-stamped, and ready… See the full description on the dataset page: https://huggingface.co/datasets/egupta/atl-intl-flight-data-sql-db.

The Future Schedules API is perfect for: • Travel agency and flight booking websites where users are expected to submit a date and view available flights • Websites, tools or apps to display scheduled flights on a given date • Flight schedule and airway traffic analysis based on region or dates

We have developed many filters you can use in the input to request the exact data you need without having to filter the data on your end.

The data includes: - Departure and arrival airport information: IATA codes - Weekday: The day of the week of the flight, "1" being Monday - Terminal and gate: The most common terminal and the gate number of the departing/arriving flight - Take-off information: Scheduled departure or arrival time of the flight - Aircraft details: Model code and text - Airline details: Name, IATA and ICAO codes - Flight information: Flight number with flight IATA and ICAO codes

1) Request For the departure schedule of a certain airport on a certain future date.

GET http://aviation-edge.com/v2/public/flightsFuture?key=[API_KEY]&type=departure&iataCode=BER&date=YYYY-MM-DD

For the arrival schedule of a certain airport on a certain future date.

GET http://aviation-edge.com/v2/public/flightsFuture?key=[API_KEY]&type=arrival&iataCode=BER&date=YYYY-MM-DD

For the flights that are scheduled to arrive at a certain airport on a certain date (out of a departure schedule).

GET http://aviation-edge.com/v2/public/flightsFuture?key=[API_KEY]&type=departure&iataCode=BER&arr_iataCode=ORY&date=YYYY-MM-DD

For the flights that are scheduled to depart from a certain airport on a certain date (out of an arrival schedule).

GET https://aviation-edge.com/v2/public/flightsFuture?key=[API_KEY]&type=arrival&iataCode=BER&dep_iataCode=ory&date=YYYY-MM-DD

2) Filters &iata_code= (obligatory) Departure or arrival airport IATA code depending on the "&type=" value &type= (obligatory) Either "departure" or "arrival" as both within the same query is not possible &date= (obligatory) Future date in YYYY-MM-DD format

&dep_iataCode= filter of departure airport if "arrival" for "&type=" was chosen, based on the airport IATA code &dep_icaoCode= filter of departure airport if "arrival" for "&type=" was chosen, based on the airport ICAO code &arr_iataCode= filter of arrival airport if "departure" for "&type=" was chosen, based on the airport IATA code &arr_icaoCode= filter of arrival airport if "departure" for "&type=" was chosen, based on the airport ICAO code &airline_iata= option to filter airline based on airline IATA code &airline=icao= option to filter airline based on airline ICAO code &flight_num= option to filter a specific flight based on its flight number

3) Example Output: [ {"weekday": "1", "departure": { "iataCode": "mty", "icaoCode": "mmmy", "terminal": "c", "gate": "f2", "scheduledTime": "20:35" }, "arrival": {"iataCode": "iah", "icaoCode": "kiah", "terminal": "d", "gate": "d12", "scheduledTime": "22:00" }, "aircraft": {"modelCode": "a320", "modelText": "airbus a320-232" }, "airline": {"name": "vivaaerobus", "iataCode": "vb", "icaoCode": "viv"}, "flight": {"number": "616", "iataNumber": "vb616", "icaoNumber": "viv616"} } ]

Note: Schedules that are up to 1 year ahead of the current date are available.

Domestic One-Way Flight Prices Dataset (SQLite)

This project collects domestic one-way flight pricing data over a defined date range and duration from Atlanta (ATL) to 10 US cities. It saves this structured flight information to a SQLite database and enables flexible downstream querying and visualization. Each entry represents a real flight quote retrieved from a travel search API under fixed conditions. The data is structured, time-stamped, and ready for time-series, pricing trend… See the full description on the dataset page: https://huggingface.co/datasets/egupta/atl-dom-flight-data-sql-db.

Flight Light Inc Company Export Import Records. Follow the Eximpedia platform for HS code, importer-exporter records, and customs shipment details.

Flight Unmanned Systems Llc Company Export Import Records. Follow the Eximpedia platform for HS code, importer-exporter records, and customs shipment details.

Motivation

The data in this dataset is derived and cleaned from the full OpenSky dataset to illustrate the development of air traffic during the COVID-19 pandemic. It spans all flights seen by the network's more than 2500 members since 1 January 2020. More data will be periodically included in the dataset until the end of the COVID-19 pandemic.

License

Creative Commons CC-BY

The only difference with the original dataset comes from anonymised aircraft information.

Disclaimer

The data provided in the files is provided as is. Despite our best efforts at filtering out potential issues, some information could be erroneous.

Origin and destination airports are computed online based on the ADS-B trajectories on approach/takeoff: no crosschecking with external sources of data has been conducted. Fields origin or destination are empty when no airport could be found.

Aircraft information come from the OpenSky aircraft database. Fields typecode and registration are empty when the aircraft is not present in the database.

Description of the dataset

One file per month is provided as a csv file with the following features:

callsign: the identifier of the flight displayed on ATC screens (usually the first three letters are reserved for an airline: AFR for Air France, DLH for Lufthansa, etc.)

number: the commercial number of the flight, when available (the matching with the callsign comes from public open API)

aircraft_uid: a unique anonymised identifier for aircraft;

typecode: the aircraft model type (when available);

origin: a four letter code for the origin airport of the flight (when available);

destination: a four letter code for the destination airport of the flight (when available);

firstseen: the UTC timestamp of the first message received by the OpenSky Network;

lastseen: the UTC timestamp of the last message received by the OpenSky Network;

day: the UTC day of the last message received by the OpenSky Network;

latitude_1, longitude_1, altitude_1: the first detected position of the aircraft;

latitude_2, longitude_2, altitude_2: the last detected position of the aircraft.

Examples

Possible visualisations and a more detailed description of the data are available at the following page:

Credit

If you use this dataset, please cite the original OpenSky paper:

Matthias Schäfer, Martin Strohmeier, Vincent Lenders, Ivan Martinovic and Matthias Wilhelm. "Bringing Up OpenSky: A Large-scale ADS-B Sensor Network for Research". In Proceedings of the 13th IEEE/ACM International Symposium on Information Processing in Sensor Networks (IPSN), pages 83-94, April 2014.

and the traffic library used to derive the data:

Xavier Olive. "traffic, a toolbox for processing and analysing air traffic data." Journal of Open Source Software 4(39), July 2019.

The dataset contains locations and attributes of P56A and P56B flight restrictions in the District of Columbia. A dataset provided by the National Geospatial-Intelligence Agency (NGA) identified P56A and P56B flight restrictions in DC. The data specifically comes from NGA's Digital Aeronautical Flight Information File (DAFIF).

This datasets contains information about number of flight, passengers, and cargo in Saudi Arabia's Domestic airports, for 2016- 2019. Data from General Authority for Statistics . Export API data for more datasets to advance energy economics research.Source : Saudi Arabian Airlines Organization.

✈️ Flight Booking Chatbot

A conversational Python chatbot that helps users search and book flights. It integrates OpenAI's GPT model for intelligent query parsing and uses SQLite to store flight and booking data.

  🧠 Features

Natural language understanding powered by GPT (via OpenAI API) Flight search with flexible date ranges and route parsing SQLite database for storing flights and user bookings Interactive CLI chatbot interface View existing bookings by name and… See the full description on the dataset page: https://huggingface.co/datasets/alisid03/NLPProj.