This Feature Service provides a database of worldwide airport locations and aviation information. It includes information about codenames, elevation, frequency, runways and wikipedia links.Additional Information All the data are crowdsourced by the community of OurAirports.com. SourceOurAirports.com/data/ | Last accessed on: 23.05.2025Processing procedureBy using the CSV table 'Airports' dated Feb 09, 2024, we have joined the tables 'Runways' and 'Airport-Frequencies' for additional information using the key:"ident". The points were projected and released as an ArcGIS Online feature service.Data2024

This map layer, utilizing data from the Federal Aviation Administration (FAA), displays all U.S. Airports and Heliports with pilot-specific information about each airfield.Airports designated as "5010 Airports" are public-use airports which have been included in an electronically generated document titled "Form 5010" by the FAA. The office of primary responsibility for this form is the Office of Airport Safety and Standards - Airport Engineering Division (AAS-100), which is responsible for airport engineering standards for configuration, design, equipment, and operations criteria at civil airports. Heliports typically are used by general aviation operators and serve very few air carrier operations. Furthermore, there are very few helicopters that can seat more than nine passengers, and fewer still are used for scheduled passenger operations. Since Congress has not given FAA the authority to certify facilities serving general aviation operations and the clear majority of operations served by heliports are by general aviation operators, certificating the few heliports that serve air carrier operations would not significantly enhance safety.5010 AirportsData Currency: October, 2017For more information: Airport Data & Contact Information.For feedback please contact: ArcGIScomNationalMaps@esri.comThumbnail image courtesy of Simon ClancyOther Federal User Community federally focused content that may interest youDepartment of TransportationFederal Aviation AdministrationOpen Data: USDOTOpen Data: FAA

This noise map shows the noise pollution of air traffic around the international airports Brussels Airport, Ostend-Bruges, Kortrijk-Wevelgem and Antwerp, located in Flanders. The reference year of these dates is 2016. On the noise map, the annual average noise emission of the flight movements to and from the airport is expressed in the parameter Lden. The Lden level is a weighted annual average sound pressure level over the course of the day at which evening and night levels are relatively heavier, which corresponds to the finding that noise pollution is generally perceived as more annoying in the evening and at night. European research therefore shows that a Lden is a relatively good predictor of the extent to which local residents may experience nuisance. 55 decibels (dB(A)) are used as the lower limit for air traffic to determine the number of potentially hindered persons. Since the sound cards are not suitable for high-resolution analysis, zooming in on the card is limited. For Brussels Airport, the data comes from the strategic noise map (important airports). This strategic noise map, in implementation of the European Directive 2002/49/EC, is updated every five years. For the other airports, the noise emission was added as calculated by the KU Leuven (Acoustics Laboratory) on behalf of the airports themselves (annual update). More information about the noise contours around Antwerp airport can be found in this report: https://www.antwerp-airport.com/wp-content/uploads/2017/12/Report-EBAW2016_V5.pdf More information about the noise contours around Ostend-Bruges airport can be found in this report: https://www.ostendebruges-aeroport.com/wp-content/uploads/2021/05/Sound contours-Ostend-Year-2020_v3-compressed_compressed-1.pdf

DescriptionOpenFlights Airports Database contains over 70,000 airports. The data as generated by from DAFIF (October 2006 cycle) and OurAirports, plus timezone information from EarthTools. All DST information added manually. Significant revisions and additions made by the users of OpenFlights. LimitationsBlank.AttributesOBJECTID: Assigned by WWF. Unique identifier id: Unique OpenFlights identifier for this airport ident: ICAO airport code or location indicator type: Type of the airport. Value "airport" for air terminals, "station" for train stations, "port" for ferry terminals and "unknown" if not known. In airports.csv, only type=airport is included name: Name of airport. May or may not contain the city name latitude_d: Latitude in decimal degrees longitude_: Longitude in decimal degrees elevation_: Altitude in feet continent: Continent code where the airport is located. Cross-reference to ISO 3166-1 codes here iso_countr: Country code where airport is located. Cross-reference to ISO 3166-1 codes here iso_region: Region code where airport is located. Cross-reference to ISO 3166-1 municipali: Name of the municipality where the airport is located scheduled_: Availability of airline schedule data service gps_code: GPS airport code iata_code: IATA airport code, also know as an IATA location identifier, IATA station code or simply a location identifier local_code: Local airport code. Can be the same IATA code. home_link: Website of the airport in question wikipedia_: Source of Airport Data keywords x: X location in the original coordinate system of the database (WGS 1984) y: Y location in the original coordinate system of the database (WGS 1984)

The Airports database is a geographic point database of aircraft landing facilities in the United States and U.S. Territories. Attribute data is provided on the physical and operational characteristics of the landing facility, current usage including enplanements and aircraft operations, congestion levels and usage categories. This geospatial data is derived from the FAA's National Airspace System Resource Aeronautical Data Product.

Contained within the 4th Edition (1974) of the Atlas of Canada is a plate map that shows 2 maps. The first map shows the locations of airports and aerodromes as of 1967, and also time zone boundaries. Airports and aerodromes are denoted as being an international airport, a Department of National Defense aerodrome or other airport / aerodrome and as having precision approach capability, non precision approach capability or no approach instrumentation. The length of each airport or aerodrome's runway is also indicated. The second map, at a scale of 1:35 000 000, shows the locations of water aerodromes and heliports for all of Canada.

This noise map shows the noise pollution of air traffic around the international airports Brussels Airport, Ostend-Bruges, Kortrijk-Wevelgem and Antwerp, located in Flanders. The reference year of these dates is 2016. On the noise map, the annual average noise emission of the flight movements to and from the airport is expressed in the parameter Lden. The Lden level is a weighted annual average sound pressure level over the course of the day at which evening and night levels are relatively heavier, which corresponds to the finding that noise pollution is generally perceived as more annoying in the evening and at night. European research therefore shows that a Lden is a relatively good predictor of the extent to which local residents may experience nuisance. 55 decibels (dB(A)) are used as the lower limit for air traffic to determine the number of potentially hindered persons. Since the sound cards are not suitable for high-resolution analysis, zooming in on the card is limited. For Brussels Airport, the data comes from the strategic noise map (important airports). This strategic noise map, in implementation of the European Directive 2002/49/EC, is updated every five years. For the other airports, the noise emission was added as calculated by the KU Leuven (Acoustics Laboratory) on behalf of the airports themselves (annual update). More information about the noise contours around Antwerp airport can be found in this report: https://www.antwerp-airport.com/wp-content/uploads/2017/12/Report-EBAW2016_V5.pdf More information about the noise contours around Ostend-Bruges airport can be found in this report: https://www.ostendebruges-aeroport.com/wp-content/uploads/2021/05/Sound contours-Ostend-Year-2020_v3-compressed_compressed-1.pdf

In order to handle the planning and testing of the Taichung International Airport Park, the scope is the non-urban planning area of the airport, and the testing will be carried out around 110

This map presents transportation data, including highways, roads, railroads, and airports for the world.

The map was developed by Esri using Esri highway data; Garmin basemap layers; HERE street data for North America, Europe, Australia, New Zealand, South America and Central America, India, most of the Middle East and Asia, and select countries in Africa. Data for Pacific Island nations and the remaining countries of Africa was sourced from OpenStreetMap contributors. Specific country list and documentation of Esri's process for including OSM data is available to view.

The Geographic Names Information System (GNIS) actively seeks data from and partnerships with Government agencies at all levels and other interested organizations. The GNIS is the Federal standard for geographic nomenclature. The U.S. Geological Survey developed the GNIS for the U.S. Board on Geographic Names, a Federal inter-agency body chartered by public law to maintain uniform feature name usage throughout the Government and to promulgate standard names to the public. The GNIS is the official repository of domestic geographic names data; the official vehicle for geographic names use by all departments of the Federal Government; and the source for applying geographic names to Federal electronic and printed products of all types. See http://geonames.usgs.gov for additional information.

Contained within the 3rd Edition (1957) of the Atlas of Canada is a map that shows the locations of civil airports and aerodromes up to September 1957, together with the operational type of airport or aerodrome. The airports were classified according to class of Air Carrier each is technically and administratively equipped to serve. Major Airports are those equipped to service all classes of Air Carrier; Other Scheduled Airports are those equipped to service all classes of Air Carrier, except International Scheduled Air Carriers; Non-scheduled Airports can service one or more of the all classes, except Scheduled Air Carriers and International Scheduled Air Carriers; Water Airports shown are all Non-scheduled Airports. The map showing these airports also includes Canadian time zones circa 1957.

This map illustrates satellite-detected damage and destruction at Sana'a International Airport, Sana'a Governorate, Yemen. Using satellite imagery acquired 15 May 2015 and 12 December 2014, UNITAR-UNOSAT identified a total of 70 affected structures and transportation vehicles. Approximately 18 of these were destroyed, 32 severely damaged, and 20 moderately damaged. Additionally, 32 impact craters were found. One medical facility was identified within 500 meters of impact craters. This is a preliminary analysis and has not yet been validated in the field. Please send ground feedback to UNITAR-UNOSAT.

The data include the coastal ports and airport distribution in the Belt and Road region. The data are from the Natural Earth global port and airport data. The data are cut according to the standard map of the 65 countries along the Belt and road, and further corrected, then the distribution of the ports and airports in the area along the B&R is obtained. This data is mainly one to analyze the B&R area's important spatial layout and main characteristics of the transportation facilities, and to get other attributes data of port and airport in the following research, including the throughput of different port cargo types, the incoming and outgoing throughput, the number of docks and berths, the number of passengers on the airport, the data of the flights and routes of ports and airports, we can get further understanding of the spatial differentiation of the distribution of ports and airports in the B&R region.

This is a custom Story Map design not based on a Story Map app template.

This point shapefile represents airports in Pakistan. This layer is part of Global Map version 2. The drainage and Transportation layers version 2 are prepared by using the digital 1:1000k data of nepal. The Global Map Nepal version 1.0 Boundaries layer was developed using The Digital Map 200000. Updating the data of version 1.0 using 1:500,000 District Map series and 1:1,000,000 International Map series developed the Global Map Nepal version 1.1 Boundary layer. Updating the Global Map Nepal version 1.1 using 1:1,000,000 Topographic Maps and other information developed the Global Map Nepal version 2.0 Boundary layer, which is corresponding to the merger of municipalities as of April 1, 2010. The Global Map Nepal version 1.0 Population center layer was developed using The 1:1,000,000 Chart International series. Updating the data of version 1.0 using The 1:500,000 District Map series and 1:1,000,000 International Map series developed the Global Map Nepal version 1.1 Population center layer. Updating the Global Map Nepal version 1.1 developed the Global Map Nepal version 2.0 Population center layer, which is corresponding to the merger of municipalities as of April 1, 2010. (Because the built-up area data of the Global Map Nepal is corresponding to the location of each municipality.)

This point shapefile represents airports in Mozambique. The Global Map Mozambique version 2 was developed to update Global Map Mozambique version 1 based on Global Map Specifications version 2.1. The Global Map Mozambique version 1.0 was developed from the shapefiles Map 1:250.000 and 1:50.000 developed 1996-1999.

Arctic 1:100,000 airport distribution data set includes vector space data and related attribute data of airports (Arctic_Airport) and airport runway (Arctic_Airport_runways) in the arctic range: airport Name, airport country Name, airport country abbreviation (CNTRY_CODE), LATITUDE and LONGITUDE. The data comes from the 1:100,000 ADC_WorldMap global data set, which is a comprehensive, up-to-date and seamless geographic digital data after the data quality inspection of topology, warehousing and other data. The world map coordinate system is latitude and longitude, WGS84 datum surface, and the arctic data set is the special projection parameter for the arctic (North_Pole_Stereographic).

This vector tile layer provides a customized world basemap that is uniquely symbolized. It is optimized to display special areas of interest (AOIs) that have been created and edited by Community Maps contributors. These special areas of interest include landscaping features such as grass, trees, and rock and sports amenities like tennis courts, football and baseball field lines, and more. This vector tile layer is built using the same data sources used for the World Topographic Map and other Esri basemaps.

Lee Plan POLICY 1.6.1: The Airport Noise Zones (Map 1-E) cover areas subject to varying levels of airport-related noise. In conformance with Airport Noise Compatibility Planning outlined in Title 14 of the Code of Federal Regulations (CFR) Part 150, the Port Authority will update the aviation forecasts and associated noise contours for the Southwest Florida International Airport when warranted by operational changes and will initiate an amendment to the Airport Noise Zone Overlay to reflect the updates as applicable. In addition to meeting the requirements of the underlying Future Land Use Map categories, properties within the Airport Noise Zone Overlay must meet the following: Zone A/Airport Property is limited to uses that are compatible with airports and air commerce, including but not limited to those necessary to provide services and convenience goods to airline passengers, those generally associated with airport operation, and related development. Upon disposition of any Port Authority property, the land is then subject to the Noise Zone as applicable based on the most recent Composite Day-Night Average Noise Level (DNL) Noise Contours map for Southwest Florida International Airport approved by the Federal Aviation Administration (FAA). Zone B does not permit any residential units, places of worship, libraries, schools, hospitals, correctional institutions or nursing homes. However, residential units, including mobile or manufactured homes, that were lawfully existing as of June 27, 2000 will be treated as legally permitted uses and may be replaced with a new mobile or manufactured home or conventional single family construction as long as such replacement would be otherwise allowed by the LDC. However, an existing conventional home may not be replaced with a new mobile or manufactured home. One conventional single family home is permitted on each lot in a plat properly recorded before June 27, 2000 if such use would have been permitted on the lot prior to June 27, 2000. Zone B requires formal notification as provided for in the LDC. Zone C and D allow existing and new construction and land uses as would otherwise be permitted by the LDC. These zones require formal notification as provided for in the LDC. (Ord. No. 00-22, 02-02, 03-02. 16-16)Land Development Code (LDC) Section 34-1104 establishes regulations for properties located within the Airport Noise Zones.

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