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

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

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 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": }, ... ]

This dataset contains Saudi Arabia Saudi Airlines Passengers Arriving from Abroad, by Airports for 2000-2016. Data from General Authority for Statistics . Export API data for more datasets to advance energy economics research.

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.

REQUIRED: A brief narrative summary of the data set.

This dataset contain information about: The number of flights executed, the number of buses and their capacity, and the number of passengers between cities for previous years, by year, month, and the city of departure

This service contains photo centers for the 2019 and 2020 high-resolution imagery acquisition.This is a MD iMAP hosted service. Find more information on https://imap.maryland.gov.Feature Service Link: https://geodata.md.gov/imap/rest/services/Imagery/MD_ImageryAcquisitionFlightInformation/FeatureServer/1

Eximpedia Export import trade data lets you search trade data and active Exporters, Importers, Buyers, Suppliers, manufacturers exporters from over 209 countries

This data contains the tile layout for imagery acquisition as part of the Digital High-Resolution Aerial Photography program. Note this tile layout reflects the overall grid and not the mapping limits. These tiles are the 3 inch imagery done as part of local buy-ups during the 2017 western shore imagery collection. Note this tile layout reflects the overall grid and not the mapping limits.This is a MD iMAP hosted service layer. Find more information at https://imap.maryland.gov.Feature Service Layer Link:https://mdgeodata.md.gov/imap/rest/services/Imagery/MD_ImageryAcquisitionFlightInformation/FeatureServer/3

This dataset contains the interpolated values of bird density and bird flight speed (N-S and E-W) resulting from the methodology presented in [reference].The methodology is explained in less detail at rafnuss-postdoc.github.io/BMM. The resulting interpolation is a probability distribution (define the probability of each value to occurs). Only the median, quantile 10 and 90 are given in this file.

The spatio-temporal grid has a resolution of 0.2° in latitude (43°-68°) and longitude (-5°-30°) and 15 minutes in time (19 September to 10 October 2016), resulting in 127x176x2017 nodes. Over this large data cube, the estimation are only computed at the nodes located (1) over land, (2) within 200km of the nearest radar and (3) during nighttime.

The same dataset can be visualised on a dedicated web interface: www.bmm.raphaelnussbaumer.com and data can be queried on a API (documentation).

The csv file is structured as a table with the following columns:

density_estimation: Median bird density bird/km^2

density_quantile10: Quantile 10 of bird density [bird/km^2]

density_quantile90: Quantile 90 of bird density [bird/km^2]

speedu_estimation: Mean bird speed east(+)/west(-) [m/s]

speedu_std: Standard deviation of bird speed east(+)/west(-) [m/s]

speedv_estimation: Mean bird speed north(+)/south(-) [m/s]

speedv_std: Standard deviation of bird speed north(+)/south(-) [m/s]

latitude

longitude

time

Southwest Airlines Co Company Export Import Records. Follow the Eximpedia platform for HS code, importer-exporter records, and customs shipment details.

On behalf of Australia, and in support of the Malaysian accident investigation, the Australian Transport Safety Bureau (ATSB) led search operations for missing Malaysian Airlines flight MH370 in the Southern Indian Ocean. Geoscience Australia provided advice, expertise and support to the ATSB to facilitate marine surveys, which were undertaken to provide a detailed map of the sea floor topography and to aid navigation during the underwater search.

This dataset comprises Side Scan Sonar (SSS), Synthetic Aperture Sonar (SAS) and multibeam sonar backscatter data at 5 m resolution. Data was collected during Phase 2 marine surveys conducted by the Governments of Australia, Malaysia and the People’s Republic of China between September 2014 to January 2017. The data was acquired by Echo Surveyor 7 (Kongsberg AUV Hugin 1000), Edgetech 2400 Deep Tow and SLH PS-60 Synthetic Aperture Sonar Deep Tow deployed from the following vessels: Fugro Supporter, Fugro Equator, Fugro Discovery, Havila Harmony, Dong Hai Jiu 101 and Go Phoenix.

All material and data from this access point is subject to copyright. Please note the creative commons copyright notice and relating to the re-use of this material. Geoscience Australia's preference is that you attribute the datasets (and any material sourced from it) using the following wording: Source: Governments of Australia, Malaysia and the People's Republic of China, 2018. MH370 Phase 2 data. For additional assistance, please contact marine@ga.gov.au. We honour the memory of those who have lost their lives and acknowledge the enormous loss felt by their loved ones.

22-1/E51-14/3

22-2/E52-06/3-3